One board for every Claude Code and Codex session on every machine you own.
See what each agent is doing, answer what it's waiting on, and hand it the next task — from your desk or your phone.
Install · How it works · 中文
- See every session at a glance. Sessions on all your machines, grouped by project — running, waiting on you, standing by or done, with what each one is doing right now.
- Answer from anywhere. When an agent needs a decision, you get a push notification. Pick an option on your phone, and the answer lands in that agent's next turn.
- Keep the work in one place. Agents record requirements as they go; you confirm them, hand them to a session, and accept the results with screenshots attached.
Step away from the desk and keep things moving from the couch, the train or bed.
- Installs like an app. Add it to your home screen and it runs full screen. Sign in with a passkey (Face ID / Touch ID).
- Tells you when it's your turn. Push notifications on iPhone, iPad and desktop browsers (also Bark and WeCom); tap one to land on that exact session or requirement.
- Built for touch. Long-press a card and drag it to another column, swipe through screenshots, swipe between requirements while reviewing — and nothing zooms or bounces when it shouldn't.
Circle, box, point and write right on the agent's screenshots. The pen follows pressure, your palm is ignored once you've used a pencil, and the marked-up image goes back to the agent with your feedback. Works with a finger, mouse or trackpad too.
 |
|
- Hand off the next task. Give a requirement to a session; to-dos queue up and arrive together when it goes idle. A session waiting in
ks waitpicks it up within seconds. - Plans with gates. Split a big goal into stages; each stage unlocks only after you accept the previous one.
- A live view of every session. Recent tool calls stream in, a ring shows how full the context is, and — if you connect your own model — a one-line summary says what it's doing.
- Swim-lane timeline. Every session gets a lane on the workbench, summarised per minute; below the midline it draws newly computed tokens (coloured by cache hit rate, with cold starts marked), and each background shell command gets its own row with start, end, type and result — failures stand out, runaways turn yellow. "Orphan" processes that outlived their ended session are listed so you can stop or ignore them.
- Context ring and compact hint. A ring next to each session title shows how full the context is; near the threshold it turns yellow, then red with "compact suggested", and one click copies the
/compactcommand for that role. - Session handoff. Click "Hand off" on a session and the old one writes down what it is doing, what it waits on, the ground rules and the next step; run
ks takeover <role>in the project directory to start the successor. Key state is also restored automatically after a compaction. Older MCP builds useks handoff. - Review before you. When a requirement is submitted for acceptance it is first sent to an online reviewer; it reaches your to-do list only after the review is in (or after 30 quiet minutes). Acceptance cards show the review status and verdict.
- FYI messages don't wake anyone. Team messages and subscribed events are either "act on this" or "FYI only"; FYI items don't wake a session and are attached the next time it is woken.
- Sub-task model policy. A per-project setting with three levels — economy, balanced, quality first — written into the PM, Aide and Dev prompts to steer which model sub-tasks use.
- Status comes from explicit records. What a session is waiting for, approve / reject and the recommended option are stored as fields; a question in the chat no longer counts as "waiting for you".
- Multiple Claude config directories. If you run Claude Code under several
CLAUDE_CONFIG_DIRs, hook each up withks install --claude-dir; session cards show where each one came from (see Install). - Briefing strip and "Away". A one-line strip on top of the workbench ("who wrote it · one-line conclusion · n to look at") rotates and opens a layered report. Switch on "Away" and the Aide answers within the scope you allow, pushes are limited to hard rules and uncertain calls, and you get a report when you return.
- One undo window, kept drafts. Every verdict shares the same undo window and takes effect immediately; every input box keeps its draft across closing a drawer, refreshing or switching items.
- One project across machines. Sessions are grouped by git remote, so the same repo on your laptop and your Mac mini is one project.
- Never in the way. Hooks time out in 1.5 s and fail open; offline machines buffer events and catch up later.
A small daemon on each machine listens to your agents through their official hooks and MCP, and reports to a Hub on one always-on machine. You use the Hub's web board from any browser. Details: How it works.
1. Install ks on every machine — the Hub and each machine you code on (macOS or Linux):
curl -fsSL https://raw.githubusercontent.com/NekroAI/kitestring/main/scripts/install.sh | sh2. Start the Hub on one always-on machine, then open http://<hub>:7310:
ks hub passwd && ks install --hub --claude=false --codex=false --daemon=false3. Connect each machine with a token from Settings → Devices:
ks login --hub http://<hub>:7310 --token kst_xxx && ks installOpen Claude Code or Codex and your session appears on the board. Updating, Codex setup and building from source: Install guide.
Kitestring only uses the extension points Claude Code and Codex document officially. It never touches your login credentials, never proxies model traffic, never consumes your subscription and never drives agents on its own. Read more.
Issues and pull requests are welcome — see CONTRIBUTING.md. Report security problems privately as described in SECURITY.md.