Compare
Every cell below comes from that project's own docs. Where something could not be confirmed it says so instead of guessing, and the rows the others win are in the table rather than left out of it.
| agent-manager | herdr | Vibe Kanban | claude-squad | plain tmux | |
|---|---|---|---|---|---|
| Where it lives | terminal | terminal | browser | terminal | terminal |
| Live agent status | yes | yes | yes | yes | no |
| Status from hook events | yes | yes | unverified | pane matching | no |
| New agent in one keypress | yes, space or n |
command or API | create an issue first | yes, n |
new-session, by hand |
| Sessions name themselves | yes, the agent renames it | no | issue title | you name it | you name it |
| Quick prompt, one keypress from the list | yes, space |
CLI and socket API | in the web UI | at creation only | send-keys, by hand |
| Spawn a new agent with the prompt embedded | yes, on a group row | via the API | yes, per issue | at creation | no |
| Retarget mid-sentence, bar stays open | yes | no | no | no | no |
| Paste a clipboard image into the prompt | yes, ctrl+v |
unverified | unverified | no | no |
| Whole-file diff review | yes | no | yes, in the browser | diff tab | no |
| Line comments back to the agent | yes, in the terminal | no | yes, in the browser | no | no |
| Resume a dead session | same conversation | unverified | unverified | pause, resume | no |
| Folded group keeps per-status counts | yes, any depth | workspaces | board columns | flat list | no |
| Agent drives the manager over MCP | yes, 4 tools | socket API instead | no | no | no |
| Worktree creation | no | yes | yes | yes | no |
| Opens pull requests | no | unverified | yes | yes | no |
| Mouse and Windows | no | both | both | no | mouse only |
Read from their docs, not from a demo half-remembered.
It is the honest baseline, and this tool is built on it. tmux keeps sessions alive and lets you switch between them, which is most of the job at small scale. What it cannot do is tell you which agent needs you, because it has no idea what is running inside a pane. Everything here is that one missing answer.
Its own Rust runtime instead of sitting on tmux, so panes, tabs and workspaces are native. Mouse is first-class, Windows runs through a beta installer, a socket API lets agents prompt each other, and there is a plugin marketplace.
A kanban board where each issue gets a workspace with a branch, a terminal and a dev server, plus 10+ agents, a built-in app preview, and PRs with generated descriptions. It also reviews diffs with inline comments sent back to the agent, which is the one thing we thought was ours; the difference is that theirs is a web UI and this is a terminal. Worth knowing before you adopt it: the project is sunsetting.
Every session gets its own worktree and branch automatically, so parallel agents
cannot collide. s commits and pushes the branch and c checks
out by committing and pausing, so review-to-PR is built in.
The deepest of any of them on worktrees: sparse-checkout
inheritance for monorepos, setup scripts, and a worktree finish that
merges and cleans up. Also a cost dashboard with budgets, session forking, and
Docker-sandboxed sessions.
One key starts an agent, one key answers a blocked one, one key opens its diff, and
the session names itself so you never stop to invent one. Then ctrl+r
shows the whole changed file rather than a hunk, and C sends your line
comments straight into that agent's pane. Nobody else closes that loop without
putting you in a browser.