Guardrails
Limits that stop an agent and wait for a person.
Guardrails apply to every agent in a project. When an agent hits one, it stops, tells you why, and waits.
| Guardrail | What happens |
|---|---|
| Paths agents can't touch | A run that needs to change these paths stops and asks. |
| Largest handoff | A change over this many lines stops, and should be split into a stack. |
| Needs a person's approval | The agent prepares the action and waits. |
| Daily spending limit | No agent can start once the limit is used up. |
| Limit per agent | Caps one agent's share of the daily limit. |
| When agents can run | Outside these hours, agents can't start. |
| Pause automatically | Pauses an agent if too many of its runs fail in an hour, and tells its owner. |
When an agent is stopped
You'll see it on the handoff, in your Inbox and under Waiting on you. Choose Allow once to let that run carry on, or Keep blocked to end it. Either way, it's in the audit log.
Your organization can set rules that apply on top of these, such as agents only opening drafts. See Organization rules.