Evidence record / omnigent
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-09-21-omnigent-carry-forward-spend-caps-are-gated-before-the-next-call-on-already-reconciled-spend-the
Carry-forward: spend caps are gated before the next call on already-reconciled spend; the orchestrator-attached sub-agent cap became approvable. Answer to the contract question: the check runs before a call, but it compares against spend already incurred and reconciled at turn boundaries. It can refuse the next turn or tool call; it cannot stop the turn that crosses the cap. The top-level cost_budget is unchanged since July. The sub-agent budget (usually attached by the orchestrating model at spawn, per #6505 a budget the user never set blocked at 12.6x its cap with no warning) no longer hard-stops: a human approval lifts it. Approvals in a shared session are resolvable by any editor (item 4).
Channel: tagged-release. Half: both. Date: cost.py changed in v0.13.0 (2026-09-09); unchanged into v0.14.0.
Operator consequence: Size max_cost_usd with one turn of headroom; it is a gate on the next call, not a meter. If you relied on a model-attached sub-agent cap as a hard stop, it is now an approval prompt on v0.13.0+; put a top-level cost_budget with empty expensive_models on the root if you need a stop that does not ask.
Receipt
Finding metadata
Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0
Finding ID: 2026-09-21-omnigent-carry-forward-spend-caps-are-gated-before-the-next-call-on-already-reconciled-spend-the
Profile citations
- omnigent / claim / spend-gate-before-next-call
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact