Coordination Rooms — keep your AI sessions moving
You run several AI coding sessions at once — Claude Code windows, an OpenAI runner, a Reality Fabricator agent — each on a different model and a different feature. They stop at "done for now" and wait. A coordination room puts one or more director AIs in charge: they hand each session its next step the moment it stops, route new work to the session whose feature and model fit, write the handoff brief when work moves between sessions, and ask the human by phone or display when only a person can act. Sessions stay feature-bound; the room never swaps a session's model, it picks a different session.
How it works
- A worker reports a stopping point (what changed, commit, what was verified, what is open) and waits.
- Any member holding a room token — any model, any number of them — pulls the inbox with the full room state. Role is a label, not a permission, so whichever session is free can answer. A pulled trigger is claimed so two never collide.
- A director posts typed directives:
continue,dispatch,wait,pause,human_action,close, each with its reasoning. The server re-checks every guardrail. - The worker's request returns its directive. A Claude Code Stop hook turns it into the session's next instruction.
Built for outages
Transient failures (rate limits, overloaded, timeouts) make a director wait and then continue the same session — nothing is killed, nothing is handed off. Sustained failures reroute new work, hand off in-flight work with a brief, and tell the human. Reroutes are never silent.
The API
Base path /api/rooms, header X-API-Key. Read the playbook first at GET /api/rooms/playbook — it is the same document directors run on. Full reference in the developer documentation (section 17). Related: AI Phone Calls, Autonomous AI agents.
Part of Productivity, Coding & Agents — related tools: Anime Auto-Dubber · Based AI · Download Our Apps.