Local edition · Arms and budgets
What an arm is, how tiers work, and how budgets stop spend.
This reference describes the standalone local edition started with pnpm start. For the hosted workspace, see Connect a runner.
Arms
An arm is one way to run a card: an executor, a model, an effort level and a tier.
{
"id": "claude-haiku",
"executor": "claude",
"model": "haiku",
"effort": null,
"tier": 1,
"unitCost": { "per": "run", "usd": 0.01 },
"enabled": true,
"notes": "good at small bug fixes and docs"
}
- Tier orders arms from cheapest (1) upward. The
cascadepolicy starts at the lowest tier and escalates one tier when verification fails. - Unit cost is used only when the CLI reports no cost. Costs computed from it are marked as estimates in Insights.
- Notes are shown to the planner, together with each arm’s measured pass rate and median cost from the ledger.
Edit arms on the Agents page with the form, or as raw JSON under “Advanced”. Disabled arms are skipped by every policy.
Budgets
A budget limits one executor over a period: day, week, month or total, in credits, usd or runs.
[{ "executor": "kiro", "period": "month", "limit": 50, "unit": "credits" }]
Spend comes from the ledger: the cost the CLI reported, otherwise the arm’s unit cost (an estimate), otherwise nothing. When a budget is used up, every policy skips that executor’s arms and says so in its reason. The status bar and Insights show budget meters.
What the CLIs report
- Kiro reports credits but no tokens.
- The harness reports tokens but no price.
- Claude Code reports a list-price USD figure (
total_cost_usd), even on a subscription. - Codex reports tokens when a
turn.completedevent carries usage.
Agent Kanban never invents a number: anything a CLI did not report stays blank.