Agent Ops

Agent Ops

Approval gates that don’t slow everyone down

Approval gates that don’t slow everyone down

Approvals are the safety net for autonomous agents. Designed badly they become a queue. Here’s how to design them well.

Approvals are the safety net for autonomous agents. Designed badly they become a queue. Here’s how to design them well.

Portrait of Rhea Natarajan

Rhea Natarajan

6 min read

Abstract data illustration for “Approval gates that don’t slow everyone down”

An approval gate pauses a run until a person says yes. Used well, it’s how you let agents near money and access. Used badly, it’s a new queue nobody owns.

Gate decisions, not agents

Put gates on specific actions with clear thresholds: refunds over $150, production access, emails to more than 50 recipients. Everything below the threshold runs on its own.

Bring the context to the approver

An approval request should contain the agent’s recommendation, the evidence and the policy it applied — in Slack or Teams, where approvers already are. If people have to open another tool, approvals stall.

  • Set an owner and a timeout for every gate

  • Default to the safe outcome when a gate times out

  • Review gates monthly: raise thresholds where approvals are always yes

Portrait of Rhea Natarajan

WRITTEN BY

Rhea Natarajan

Head of Agent Operations

Rhea leads the team that helps customers move agents from shadow mode to full autonomy. Before Cairn she managed a 200-person support org.

Field notes

One email a month. Only the useful parts.

Lessons from running agents in production, new templates and the releases worth knowing about. Unsubscribe in one click.

Create a free website with Framer, the website builder loved by startups, designers and agencies.