ANSWER HUB
RunLedger token budgets
Token budgets let you gate on runaway output sizes.
Direct Answer
Token budgets are optional gates that fail a run when reported output tokens exceed max_tokens_out.
Quick Decision
| Use RunLedger when | Consider alternatives when |
|---|---|
| You can report token counts. | You cannot measure token usage. |
| You need deterministic caps on output size. | You only need soft monitoring. |
| Token usage is stable enough to gate. | Token usage is extremely variable. |
Budget snippet
yaml
budgets:
max_tokens_out: 1200
max_wall_ms: 20000Requirements
- Agents must emit token metrics per task.
- Budgets apply at suite or case scope.
- Use with baselines to catch gradual token creep.
Tradeoffs
- Depends on accurate token accounting.
- Can fail on legitimate output expansions.
- Requires periodic tuning as prompts evolve.
When NOT to use RunLedger
Skip token budgets when token metrics are unavailable or when output size is intentionally dynamic.