Forty agent lanes. Two need you.
Every project you have work running in, on one screen
Pitwall reads a project's tracker, its repositories and the work running in them, and reports them together: what is blocked, what needs a person, and whether that is still true.
npx @404sl/pitwall@latest snapshotSource on GitHubHow it works
Open lanes
Point Pitwall at a repo and describe the work. Each task gets its own lane: a branch, an isolated worktree, and whatever executor you already use.
Watch the board
Every lane reports the same five numbers: state, progress, elapsed, diff size, step. Open one to read its log and its plan. Kill it, restart it, or leave it alone.
Review, merge, deploy
Green lanes run review, merge into base and deploy without asking. Anything ambiguous stops and flags you. That is the only time the board turns red.
What the control center gives you
Isolated lanes
Separate worktree per lane. Nothing collides, nothing waits on a shared checkout.
Automatic review gate
Tests, typecheck and your own review rules run per lane. Only clean lanes reach merge.
Merge and deploy
Queued merges into base, then a preview or production deploy. Rollback is one row away.
Full timing history
Every lane keeps its log, diff and timing. Compare two runs of the same task side by side.
Executor-agnostic
Bring your own agents, scripts or CI jobs. Pitwall schedules and watches; it never executes.
One red flag at a time
Failures are ranked, not broadcast. The board tells you which lane to look at first.