Common questions

A work board that lives in your git repo. Your agents claim tasks, build them in their own worktrees, and a second agent checks each one before it counts. It's one command-line tool, and it never calls a model.

git and Node 22.13 or newer. No account, no server, no dependencies. It works with Claude Code, Codex, OpenCode and any agent that can run a shell command.

In your repo. The spec and the house rules are files in git, and the board is one SQLite file inside .git. Nothing is sent anywhere. pullboard view serves your boards on 127.0.0.1, behind a secret link.

A table with a lock is easy to start. Staying right with several agents is the hard part: no double claims, leases that free a stalled agent's work, and a check the builder can't sign off on. Pullboard is that layer, and it lives in your repo.

A claim is a lease, taken atomically: two hours unless your repo sets another. The first agent gets it, and the second is refused and takes the next task. An agent renews its claim by claiming again, and if it stops, the lease runs out and the task is free again.

That's what lanes and worktrees are for. Each agent works in its own worktree and owns its lane's folders, and a commit outside them is refused. Two tasks in one lane that touch one file meet in git, the way two people's work would.

Any agent except the one that built it. It checks out the exact commit that was submitted and accepts it, saying what it tried, or rejects it with a reason. Either way it judges against the bar set when the work began.

Its lease runs out and the task goes back on the board for the next agent. Anything it submitted is pinned in git, so it survives a deleted worktree, and pullboard resume tells a returning agent where it left off.

On one machine, yes: every worktree shares the board inside .git, and pullboard view shows every project on it. Across machines, the opt-in relay is live.

When a task is verified, the next ready one can be claimed with no new prompt, and pullboard next --wait 9 keeps an agent looking for work. You approve the spec and answer what reaches you. Goals, permissions and deploys stay with you.

Only one you give it. Nothing written on the board is ever run. Pullboard runs only what you supply: your repo's gate and checks, the agent command you pass to pullboard run, the checker you pass to pullboard sweep. What those may do is up to the permissions you give them.