How it works.
Six pictures, one at a time. The CLI makes every one itself, so none of them can go stale.
How work moves.
You decide the spec. Agents claim, build and submit. A second agent verifies that commit.
Starting with an agent.
Set up the repo, commit, and tell your coding agent what to build. It runs the team from there.
An item's life.
Every state, move and refusal, drawn from the one place the CLI declares them.
Where things live.
The coordinator's checkout, the worktrees beside it, and the board inside .git.
The board you watch.
pullboard view on a demo board: every project on your machine, live, on one page.
On your phone.
The same board, in dark mode, on a phone's width.
What you get
What changes once your agents work from a board in your repo.
Work is checked before it counts
Another agent checks out the exact commit, runs your tests and tries to break it.
The bar is set up front
A task's criterion is frozen when it's claimed, so it can't be lowered to get the work through.
Work carries over between sessions
Tomorrow's agent reads what's next, what was rejected and why, from the board in your repo.
You see only your decisions
Agents ask their coordinator first, and it passes on the decisions only you can make.
See it in thirty seconds
The tour runs a real reject and its fix on a throwaway repo. Then set up your own.
npm i -g pullboard
pullboard tour