Run several coding agents on one board without collisions.
Claude Code in one terminal, Codex in another, Cursor on your laptop. Klio hands each one different work and keeps the board honest about what's really in progress.
- Waiting for the first agent…
How Klio helps
Klio gives each agent connection a claim on the story it's working on, so two agents never build the same thing, and the board shows who is doing what.
Atomic claims
start_issue claims a story for that connection. Other agents' get_next_work skips it, and a second start_issue is refused with the holder's name.
Status discipline
Agents move stories in order, one at a time: In Progress, criteria ticked as they pass, then In Review. Done stays your call.
Stale work comes back
If an agent goes quiet, the story shows “no activity” on the board with a Release button, so another agent can take it.
Scoped tokens
Limit a token to the projects one repo works on. It can't see, change or create anything else.
Questions
Which agents can share a board?
Any MCP client: Claude Code, Codex, Cursor, Windsurf, VS Code with Copilot, Zed, Kiro, Cline, Gemini CLI, opencode and more.
How does Klio tell agents apart?
Each MCP connection gets its own session. Klio also shows the model ID an agent reports on the stories it works on.
Which coding agents work with Klio?
Any agent that speaks MCP. There are setup guides for Claude Code, Codex, Cursor, Windsurf, VS Code with Copilot, Zed, Kiro, Cline, Gemini CLI and opencode in the docs.
More from Klio
Start with one sentence.
Sign in with GitHub. Your workspace starts with a five-minute tour project.