What Kairos does by itself

Baton

Handing a task to another coding tool when every account of its own tool is out, and back again — the baton file, what goes along, what the session says, and why it happens only for sessions you mark.

When the account a session runs on reaches its limit and no other account of its tool has room, Kairos first moves the session to another account of the same tool when it can. When it cannot, Baton hands the task to another coding tool, which continues in the same folder, and hands it back once the first tool has room again.

Only when you mark the session

A handoff sends your repository to another vendor, so it happens only for a session you marked, never on its own: Hand off to Codex when out in the session's detail, on the Mac, the iPhone or the web dashboard. See Sessions.

The baton

The handoff is a file in the session's folder, .kairos/baton.md: the goal, what is done, the changes, the failing tests, the decisions and the next step.

1. Before it stops, the session is asked to write the baton. If it already stopped mid-step, Kairos writes it from what it knows: the session's last request and reply, git status and git diff.
2. The other tool starts in the folder, reads the baton first, and rewrites it before it finishes.
3. When the first tool has room again and the other has finished, the first session is asked to continue from the rewritten baton.

.kairos/ ignores itself in git, so the baton is never committed.

Pages go along

Another tool cannot open a claude.ai page, so what Kairos keeps of each page the session published goes into the folder too, with an index naming each page, its link and the account that has it. See Pages.

On screen

Nothing else leaves the Mac: each tool talks only to its own vendor, as it always does.