Running Triage

Triage runs in a coding agent — yours, launched for a few minutes with one job: organize the open backlog, then stop. There are three ways to start it.

From the Cockpit

Click Triage in the Backlog masthead. nitpin launches your configured agent headlessly, shows a “Triaging the backlog…” progress row (with a Cancel), tints the chrome slate-violet while it runs, and regroups the Backlog live as the clusters land.

Which agent and model run is set by the Triage row in Settings › AI Agents › Models.

From your coding agent

Type /nitpin triage in your agent, or ask it to “triage the nitpin backlog”. Same result, but interactive: you can watch it reason and answer questions. The agent reads the open issues, peeks at screenshots only where the text is ambiguous, splits anything incoherent, groups the rest, and stops without fixing.

From a terminal

nitpin triage --run                 # launch the configured agent headlessly
nitpin triage --run --harness codex # pin a specific agent
nitpin triage --run --only 3,5,8    # re-triage just these issues, merging in
nitpin clusters                     # print the current clusters

--only is a partial re-triage: the named issues are re-placed while every other cluster, override, and brief stays put.

When to re-run it

Triage isn’t one-shot — backlogs drift as you keep capturing. The auto-triage setting (per project, with a machine-wide default) watches the ratio of unclustered to clustered issues and recommends a re-triage when the pile outgrows the plan: Off / Suggest at 2× / 3× / 5×. Agents see the same recommendation and will re-triage before starting work when it’s warranted; your drag-corrections survive.

nitpin set autotriage=3     # the same knob, from a terminal