Task Models
Not every nit deserves your biggest model. nitpin routes each unit of agent work to a model matched to the job; you configure the policy once in Settings › AI Agents › Models.
Five tasks, five preference chains
| Task | Used for |
|---|---|
| Triage | clustering related issues and splitting unrelated sub-issues |
| Small | quick, low-risk fixes |
| Medium | typical fixes |
| Large | substantial, multi-file fixes |
| XLarge | the biggest, riskiest fixes (also Tune’s analysis) |
Each task owns an ordered preference chain — Primary › fallback² › … — of
agent + model (+ effort) entries. Drag to reorder, Change model to edit an entry
through an agent → model → effort picker, Restore default to go back to the
shipped policy.
For each task nitpin tries the first entry whose agent is installed. Later entries are error fallbacks only: they run when the earlier one fails technically (API, billing, rate-limit, or auth errors), never because a fix was “hard”. Your primary is always the one doing the thinking.
Where sizes come from
Triage estimates each sub-issue’s size (S / M / L / XL); a dispatched unit routes by the largest size it contains. Work that was never triaged has no size, so the Unsized fixes setting (default L) picks which chain it uses.
Explicit choices always win: Fix with ▸ in the Cockpit, or
nitpin fix --agent/--model/--effort from a terminal, pin the exact routing for that
dispatch.
Parallelism
Agents at once (Settings › AI Agents › Parallelism) caps how many fix agents Autopilot runs in parallel, machine-wide. Projects set to One at a time serialize regardless of the cap.