Approval Gates
Human Checkpoints Inside Autonomous Workflows
Unlike upfront plan review, Approval Gates are embedded inside long-running workflows. The agent pauses at predefined checkpoints, shows what it plans to do next, and waits for human sign-off before proceeding. The safety net for high-stakes agentic execution.
Framing
The problem
Long-running automation needs human checkpoints inside the flow, not just at the start.
The pattern
Pause execution at predefined gates for approval, edit, or abort.
Why chat breaks here
Conversation cannot reliably interrupt hidden downstream steps at the right moment.
Risks
Too many gates destroy automation gains and train users to rubber-stamp.
Avoid when
The sequence is fully reversible and low-risk end to end.
Use when
Long-running automation has discrete decision points that require human judgement mid-flow.
DOPE evaluation
- Directability
- Approve, edit the plan, or abort at each checkpoint
- Observability
- Upcoming actions visible at each gate before execution
- Predictability
- Gate positions are predefined — users know exactly when they'll be asked
- Explainability
- Each gate shows what the agent plans to do next and why before proceeding
In the wild
- LangGraph Human-in-the-Loop (LangChain) — interrupt() pattern + HITL middleware: on tool call, pauses for approve / edit / reject / respond. The canonical developer-API expression of the pattern.
- n8n Wait Node (n8n) — Jan 2026 shipped HITL for AI tool calls — gated tools cannot execute without explicit human approval. Wait node is the building block routed to Slack/email.
- Cursor Agent Ask-Before-Act (Cursor) — Composer asks before each tool call by default; users can cap steps (e.g. 50) before the agent must re-ask. Mid-flow gates without a separate orchestration framework.
- Magentic-UI: Human-in-the-Loop Agentic Systems (Academic source · Mozannar, Bansal, Tan et al. (Microsoft Research, Jul 2025)) — Argues for per-action-class guardrails (web access, file write, shell command) rather than uniform approval. Same gate primitive, but configured per tool category — a sharper application of the pattern.
FAQ
When should I use the Approval Gates pattern?
Long-running automation has discrete decision points that require human judgement mid-flow.
When should I avoid the Approval Gates pattern?
The sequence is fully reversible and low-risk end to end.
What problem does Approval Gates solve?
Long-running automation needs human checkpoints inside the flow, not just at the start.
Why is chat the wrong fit for this?
Conversation cannot reliably interrupt hidden downstream steps at the right moment.
Related patterns
- Often paired with: Intent Preview — Preview at the start; gates inside the run — together they cover the whole arc.
- Often paired with: Action Audit & Undo — Gates catch high-risk steps live; the audit log keeps everything reviewable.
- Often paired with: Autonomy Dial — Lower autonomy categories trigger more gates; the two settings reinforce each other.