Today we're releasing approval gates — a way to pause an agent before a specific action and require a human to confirm before it proceeds.

The request behind this one was consistent. Teams wanted agents running independently on most of a workflow, but not on the two or three steps where a mistake would actually matter. Until now that meant choosing between full autonomy and full supervision. Approval gates remove the choice.

How it works.

Add a gate to any step in an agent's workflow. Everything before it runs automatically. When the agent reaches the gate, it pauses and notifies the assigned reviewer with full context — what it's about to do, why, and what data it's using. Approve and it continues. Reject and it stops, with the reason logged.

Where teams are putting them.

Early users have gravitated toward a clear pattern: no gates on reading, drafting, categorizing, or routing; gates on writes to systems of record, outbound customer messages, and anything touching billing.

Rejected actions don't count toward your task limit.

We didn't want pricing to discourage the safety mechanism.

Approval gates are live now for all Pro and Enterprise customers. You'll find them in the workflow editor under each step's settings.