roost
Every coding agent writes its own state onto its tab: working, blocked, done. One look along the row shows where to go next, and none of it is guessed from the screen. roost runs them all on a tmux server of its own.
curl -fsSL https://raw.githubusercontent.com/beatzball/roost/main/install.sh | sh
Needs tmux 3.2 or newer and git. There is no daemon and no binary, just a launcher, a tmux config and some shell scripts.
Claude drafts a plan and asks three other agents to review it at once: Claude on Sonnet, Codex and opencode. Every tab shows who is working, and the reviewed plan opens in a pane on the right.
Four things that change once your agents run in roost.
Each agent reports its own state through a hook or an adapter, so a badge is what the agent said, not what its screen happened to look like. One key takes you to the most urgent: an error first, then anything blocked.
Ctrl-s broost runs on a tmux server of its own, with its own config and its own prefix. Your everyday sessions never see it, and one command puts the whole thing away.
roostroost killread returns the reply the agent recorded as its turn ended, not the input box drawn underneath it. wait-done blocks until a pane is finished and exits 2 if the agent died, so a script can branch instead of guessing.
roost sendroost wait-doneroost read$ roost wait-done api $ echo $? 0 $ roost read api - Roost gives each agent its own window in one shared tmux space.
roost ssh starts roost on another host and attaches you to it. The agents run over there; the keys, the badges and every command stay the same.
roost ssh buildboxFour commands, in this order.
curl -fsSL https://raw.githubusercontent.com/beatzball/roost/main/install.sh | shClones roost and puts it on your PATH.
roost doctorChecks tmux, truecolor, fzf, hooks and adapter links.
roost initPicks a theme and prints the agent hooks.
roostStarts the default session, or attaches to it.
roost's commands are small enough to type, loop over, or hand to an agent.
Prompt an agent from whatever tab you happen to be on.
roost send api "run the tests"Send the same prompt along the fleet, then wait-done on each.
for w in api web; do roost send "$w" "run the tests"; doneAn agent prompts a helper it opened, then reads the reply it recorded.
roost send %12 "review the diff"Driving a fleet has every command, with its exit codes.
Five come ready to report their own state. Anything else can call one command.
roost hooksroost doctorroost doctorroost doctorroost hooks codexroost state working
5 adapters ship in the repo, and each one badges its
pane and records its reply on its own. Claude Code and opencode are
wired automatically in roost's own panes; the rest take one
roost install. What each can signal is not identical:
Codex has no error signal to pass on, and pi never asks permission,
so a pi pane never blocks.
Every harness's exact badge table.
The full recording the clip at the top is cut from, from the first prompt to the reviewed plan.
Claude on Opus leads. It writes a plan and asks three reviewers in
their own windows: Claude on Sonnet, Codex on gpt-5.6-terra, and
opencode on Nemotron. It folds their feedback into the plan and
opens it with roost view and preen. The waits are cut:
the real run took about eight minutes.
curl -fsSL https://raw.githubusercontent.com/beatzball/roost/main/install.sh | sh
New to it? Start with getting started.