Your agents can ship faster than you can keep track.
bench turns your repo into mission control: every task is a card,
every agent works in its own worktree, every change waits as a PR
for your review.
bench's own board, on this repo. Three
agents at work, each on its own branch — and every one of them stops
at review.
Two minutes
Untar it, run it, open the board.
It goes into .task-manager/ inside the repo
it manages. One script wires the project and serves the board on port
26071 — pinned, so the url is always the one you bookmarked.
Two questions on the first run: solo or team, and which coding agent
runs the headless jobs. What runs your tests is read off the project.
Everything else is written into a settings file, commented, for when
you want it.
no account, no service, no database. it is
python 3 on your own machine.
~/your-repofirst run · abridged
$install_block
solo or team? [solo]:
which agent adapter? [claude]:
…
Task board for ~/your-repo/.task-manager/tasks
http://127.0.0.1:26071/
You've got agents. Now you've got a coordination problem.
“Which tab was that in?”Every agent's task, branch and status on one
board — not scattered across chat sessions that forget everything.
“They keep stepping on each other.”Each agent works in its own git worktree.
Parallel work, zero collisions.
“Did something just merge?”Never. bench opens PRs and puts CI on the
card — the merge button is yours alone.