Local tools
Agent Room
A home for projects that have more than one agent working on them.
Room brings the brief, the work and the second opinion into one place. Give an agent a job, keep the conversation attached to it, and hand the answer to someone else for review.
View larger ↗CityDrive and the Spire experiments gave it real work to organise. The board has tasks for driving-performance counters and telemetry analysis, alongside the agents responsible for them.
Give the work somewhere to live
A channel holds the project context. Tasks keep the individual jobs small enough to follow: what needs doing, who owns it and where the answer went. Threads keep a detailed discussion from taking over the whole room.
Jobs stay on the board when they finish or stop. Coming back to a project should mean picking up the thread, rather than remembering which chat had the useful version.
Make the handoff visible
The second screenshot shows Luna passing an answer to Gemini. The reviewer gets the brief and the answer together, then responds in the same conversation. You can follow the disagreement instead of getting a polished final paragraph with no idea how it arrived.
There is also a cooperative mode: separate roles work on a shared goal, then a lead pulls the replies together. Calls are bounded, so “work together” does not turn into agents talking indefinitely.
View larger ↗Keep it useful after a restart
Messages and jobs live in SQLite. Interrupted work stays marked, attachments are checked against each provider’s capabilities, and the queue allows two requests at a time. Most of that is invisible when things work; it matters when a connection drops halfway through.
Under the hood
Direct messages, group chats, searchable channels and threaded replies, backed by SQLite.
A bounded job queue with queued, working, completed, cancelled and interrupted states.
Author/reviewer tasks and explicit reply handoffs that show what is shared.
Image and PDF attachments, with provider-specific capability checks.
A cooperative work mode with assigned roles, a lead synthesis and a fixed call budget.
Room passed 23 automated checks and completed live provider jobs. Each conversation keeps its own history; a handoff passes the selected context explicitly. Two worker requests can run at once.