Repository navigation
Add configurable session cost budget with guardrail events #32
Description
Phase 2 — Security-critical observability
Runaway agents have no circuit breaker. Add configurable session cost threshold.
- Emit
cost_warningwhen approaching limit - Emit
cost_exceededwhen hit - Optionally halt execution on exceed
- Configurable via settings or CLI flag
Activity
Keesan12 commentedon May 19, 2026
For session caps, the thing I’d avoid is exposing only “budget exceeded” as an event.
Operators usually need three layers:
That last one matters because otherwise you know the run stopped but not whether it stopped after a useful checkpoint, mid-retry, or after an avoidable failure. We’ve found the receipt is what turns a cap from a safety brake into something you can resume and audit cleanly.