$ cockpit watch
Claude Code made it cheap to run several coding agents at once — one git worktree per task, each with its own cmux terminal running claude, each ending in a PR. That scales the work, not the tracking. Cockpit is the missing glue: it re-derives the whole fleet every cycle and renders one live table you drive by keystroke.

$ cat WHY.md
After a few parallel tasks you're tabbing through terminals and refreshing browser tabs to answer three questions: which agent is idle and waiting on you, which PR just went red on CI, which one has a review comment nobody answered. Cockpit computes every row from the real state of git, cmux, and GitHub each cycle — no stored inventory to drift out of sync. From that one table you focus a session, open its PR or ticket, nudge an idle agent, or close a finished worktree, without leaving the terminal.
what it does
git worktree list + cmux tree + your open PRs + linked tickets, re-derived every cycle. Each row is computed, never cached — so it can't lie to you.
/cockpit:new builds a worktree + cmux session + PR-tracking row from a PR number, Slack thread, ticket, or bare branch — and reaps the whole thing when the PR merges.
Links each PR to Linear, GitHub Issues, Jira, or Trello via a footer in the PR body, and can transition the ticket on merge. One keystroke opens it.
Most keys act on the highlighted row and the footer hints adapt to its state. Focus, nudge, close, or open a PR — no mouse, no leaving the terminal.
the verbs
$ install
requirements
uv, git ≥ 2.30, Python ≥ 3.12, an authenticated gh, and Claude Code — plus a workspace backend on PATH: cmux on macOS or limux on Linux. Without a backend, cockpit still runs the statusline in cache-only mode.
it also writes your Claude Code statusline
I wrote Cockpit to run my own multi-agent workflow — it's the platform behind the AI work on the rest of this site. Issues and PRs welcome.