Your coding agents just got an office.
Roster turns every coding session — Claude Code, Gemini CLI, Cursor or Codex — into a little colleague in a pixel office on your Mac. They work at their desks, stand up when they need you, and walk over to yours the moment the job is done.
macOS 14+ · Signed & notarized · No account, no telemetry
Stop babysitting terminals.
You kick off an agent, alt-tab to real work, and lose track — done ten minutes ago? Stuck on a question? Lists, diffs and kanban boards can tell you, if you remember to go read them. Roster is the ambient version: a quiet little office in the corner of your screen. You don't read it, you glance at it. The state of the room is the state of your agents.
Features
A room that speaks for itself
The walk
Real work earns a crossing: when an agent finishes a long task, it stands up, walks across the office and waits at your desk until you've had a look — with a native notification (and a ding) in case you're elsewhere. Never find out twenty minutes late again.
One glance, every state
Seated and working. Standing when it needs your input. Walking when it's done. At your desk for review. A red pill when a turn fails. And each desk wears its tool's logo, so a mixed office reads at a glance.
Click a colleague
Click an agent — in the room or in the sidebar — and its profile card slides in: the last thing it said, the repo path, one button for VS Code, one for the Terminal, one to mark the work reviewed.
A real little office
The colleagues are real 3D — voxel bodies under a real light, turning toward wherever they walk. Stroll around with the arrow keys (the camera stays glued to you, Gather-style), double-click to hurry somewhere, zoom when the room gets crowded.
How it works
Three small pieces, all local
- 1
A hook
With your consent, Roster wires every agent it finds: hooks in each Claude Code and Gemini CLI settings, Cursor's hooks.json, Codex's notify — every config backed up first. From then on, each session event lands in a local spool file.
- 2
A spool file
Events pile up even while Roster is closed. On launch the room replays them and catches up — no server, no socket, no polling.
- 3
A room
Events map one-to-one to the choreography: needs-input stands the agent up, a finished long turn triggers the walk, a failure pulls it back to its station, and a closed session takes its desk along.
Everything stays on your Mac. Roster never reads your code — only session events. No network, no account, no telemetry.
Open source
MIT, from day one
Roster is free and open source. The state machine is unit-tested, the fragile parts are isolated behind a thin layer, and every design decision is written down in the repo — including the verified research behind the multi-agent support (docs/providers.md). Good first issues are waiting for you.
Questions
Claude Code, Gemini CLI, Cursor and Codex, out of the box. Roster detects the tools installed on your Mac and wires them all with one click — each config backed up first. opencode is next on the list; the research is public in docs/providers.md.
Give your agents a desk.
One DMG, one click — and your coding sessions become colleagues, whichever agent runs them.