Budgets
Set a per-session cap and trailing daily, weekly, and monthly limits in the agent's YAML, next to the prompt. Organization and per-developer limits sit above them. A session that would breach a limit never starts, and one that hits its cap stops and records why.
A budget block in the agent's YAML sets the cap for one session and trailing limits over one, seven, and 28 days. It is reviewed in the same pull request as the prompt it governs, and a one-off run can lower it from the CLI or API without touching the deployed agent.
session: budget: session: 1.50 day: 5.00 week: 20.00 month: 60.00budget: declared in the agent's YAML
A session that would breach a limit is cancelled before a sandbox is created, with the reason recorded. A running session that reaches its budget stops and records budget_hit, a blocked mention gets a reply naming the limit, and alerts fire before a limit is reached.
Placeholder: session timeline ending in a budget_hit status, next to the reply a blocked mention receives
Pre-flight blocks and in-flight stops, both recorded
Trailing organization caps are always on, per-developer limits are opt-in, and the tightest applicable cap wins. Every session is attributed to a person, an API key, or a parent session, so who spent what is a filter on the sessions list.
Placeholder: the four cap levels as nested rings (account > agent > session > developer), each labeled with its scope
Account, agent, session, and developer caps compose