Autonomy Budgets
Autonomy budgets grant an agent unattended runtime with hard bounds on time or action count, then pause for review. They prevent runaway loops by forcing a checkpoint instead of a blank check on time, tokens, or side effects.
When to use
Essential for long-running AI coding agents, research agents, and autonomous workflows where bounded unattended execution prevents runaway loops and keeps humans in the loop at natural checkpoints.
When not to use
- Single-step assistants that never run unattended.
- Fully supervised flows where every step already requires approval.
- When you only need a soft warning; use hard budget ceilings for spend, not just a timer toast.
Anti-patterns
- Unbounded agent loops with only a cancel buried in a menu.
- Budgets that expire silently and keep going.
- No visible remaining time or step count during the run.
- Extending the budget automatically without an explicit user gesture.
How products use it
| Product | Implementation |
|---|---|
| Cursor Agent | Max iterations / run bounds before the agent stops for review. |
| Claude Code | Session and tool-use caps that surface when limits approach. |
| Devin | Work units and scoped runs instead of open-ended autonomy. |
| GitHub Actions | Job timeouts as a hard ceiling on unattended execution. |
Use this pattern in your project
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Autonomy Budgets" AI interface design pattern.
Pattern Definition:Run · Acme renewal
Unattended progress
Run pauses when either limit is reached.
The run stops when time or steps run out.
Frequently asked questions
What are autonomy budgets in agent UX?
Autonomy budgets are visible limits on how long or how many actions an agent may run without human review. When the budget is exhausted, the agent pauses for approval instead of continuing indefinitely.
How are autonomy budgets different from hard spend ceilings?
Autonomy budgets bound time or steps of unattended work. Hard budget ceilings bound money or tokens and stop execution at a spend cap. Strong agent products often use both.
What should users see during a budgeted run?
Show remaining time or actions, current goal, and an obvious Stop. When the budget hits zero, pause with a summary of what changed and a clear Extend or Review choice.
When should I use autonomy budgets vs human-in-the-loop?
Use budgets to allow a burst of unattended progress. Use human-in-the-loop to gate individual high-impact actions inside or after that burst. They solve different failure modes.