Working the Backlog
The Backlog is the left column of the Cockpit: every issue in the project, grouped into clusters after triage, with the controls to sort, search, and dispatch.
Issue states
An issue’s state rolls up from its sub-issues:
| State | Meaning |
|---|---|
| Unresolved | nothing done yet |
| In progress | some sub-issues resolved, some not |
| Resolved | every sub-issue fixed |
| Won’t fix | deliberately declined |
| Split | triage broke it into focused issues — the original remains as a breadcrumb |
The masthead reads BACKLOG · N OPEN (green at all-clear) with a sort toggle (by priority ⇄ by recent) and a search field (⌘F). Below the open issues, Resolved collects finished work, and an Archived disclosure folds away older resolved issues (how many stay visible is a project setting).
The Stage and Inspector
Select an issue and its screenshot takes the Stage: the annotated frame with every badge drawn on. Select a sub-issue to focus its exact spot, read its note, and act on it. The Inspector’s Details show provenance (app, window, URL and viewport for Live captures), and its Actions rail always offers one keyboard-first primary action (⌘⏎) plus the rest:
- Mark Fixed / Won’t Fix / Reopen — resolve or reopen a sub-issue by hand (or the whole issue at once).
- Fix — dispatch an agent at this issue or sub-issue; Fix with ▸ picks a specific agent, model, and effort. See Dispatching Fixes.
- Copy selector — on Live captures, the CSS selector under the mark.
- Revert fix — undo a landed fix with a fresh commit. See Reverting a Fix.
- Below a Careful rule: Stop agent (stops the agent working this issue and releases its claim) and Delete issue (moves it to the Trash — nitpin asks first, and warns if an agent currently holds it).
Priorities and ordering
Drag issues to reorder them. Order is priority, and agents work the backlog in the order you set. Within a triaged backlog you can also drag an issue onto another cluster, or use Move to ▸ / Ungroup from its context menu; nitpin remembers those placements as your corrections and preserves them across re-triages.
Who’s working what
A breathing teal dot marks any issue or cluster an agent currently holds, with the agent’s name and a live progress line. The rail’s presence cluster aggregates everything running; click it for the roster — who’s on what, with per-run Stop buttons. Claims expire on their own if an agent dies, so nothing stays stuck. But Stop agent is always there when you want something back now.
Captured content is immutable
One thing the Cockpit won’t do, on purpose: edit a capture. The screenshot, your notes, and the body are frozen at capture time. Status, priority, comments, and deletion are yours; the words and pixels stay as captured.