Dispatching Fixes

You don’t have to open a terminal to put agents to work. The Cockpit dispatches and supervises them for you.

Fix one thing

Every issue and sub-issue has a Fix action in the Inspector; clusters have Fix all. Plain Fix routes through your task models — the right model for the work’s size. Fix with ▸ opens a picker (agent → model → effort) when you want to choose by hand — say, escalating a stubborn fix to a bigger model.

Autopilot: fix everything

Autopilot in the Backlog masthead sweeps the whole open backlog (or, with a search active, just the matches — FIX MATCHES). Before committing you choose:

Involvement — see below.
Agent — Automatic (routed per unit by task model) or a specific one.

Then Fix all open N issues. Autopilot triages first if the backlog needs it, fans out one agent per cluster and per ungrouped issue, and batches small loner fixes into shared sessions (sweeps) so a dozen one-liners don’t cost a dozen sessions. How many agents run at once is capped by Settings › AI Agents › Parallelism.

While it runs, the verb becomes Running ⌄ with a live count; a progress bar in the rail tracks done / running / queued, and Stop all is one click.

Involvement: ask or auto

What should an agent do when a note is truly ambiguous?

Async · ask (default) — park a question as a comment on that sub-issue, skip it, and keep working everything else. You answer in the thread; the next run picks it up.
Async · auto — decide and keep going, unattended. For when you’d rather review diffs than answer questions.

The default lives in the project’s settings (When agents get stuck).

The roster

Click the presence cluster in the rail (or the running Autopilot verb) for Who’s working on what: every live agent, the sub-issues it holds (click to jump), its model and effort, a per-run Stop, and Stop all.

Watching the meter

Fixes report what they cost. During a run the status bar shows live token counts (↑ input · ↓ output); after it, each fixed sub-issue carries a small receipt — model, tokens, and a cost figure — in the Inspector. The menu-bar popover shows a running spend strip during big sweeps, so a glance tells you what the session is costing even with the Cockpit closed.

The same, from a terminal

Everything above is also a CLI:

nitpin fix 3                    # one issue
nitpin fix --cluster 2          # one cluster
nitpin fix --all                # the whole backlog (Autopilot)
nitpin fix --sweep 3,7,12       # batch small unrelated issues in one session
nitpin fix 3 --agent claude --model opus --effort high   # pin the routing
nitpin fix --all --involvement auto --max 4              # unattended, 4 at once

See the CLI reference for every flag.

Keyboard shortcuts