Skip to main content

The Human Gate

An approval step the platform enforces before an agent's action commits. A prompt can ask for approval; a permission policy guarantees it.

Hand-drawn ink-line illustration on terracotta: a loopy hand raised calmly palm-forward inside a simple cream archway, a one-line profile face observing beside it.

What it is​

A human gate is a checkpoint where an agent must stop and get sign-off before an action takes effect: before the filing submits, the email sends, the money moves. On Managed Agents this is a platform feature: per the docs (verify against platform.claude.com/docs; beta surfaces drift), permission policies mark each tool always_allow or always_ask, and an always_ask tool triggers a confirmation round-trip that the harness enforces. The Agent SDK has the same machinery in permission modes and hooks, per its docs.

Enforcement beats instruction​

The load-bearing distinction: telling the model "always ask before submitting" is an instruction, and instructions are probabilistic. The model follows them almost always, and almost always is not a compliance posture. A permission policy is enforcement; the tool call cannot execute without the approval, no matter what the model decides, and no matter what a prompt injection tells it to decide. That last clause is why the gate is also a security control and the standing complement to Vaults: the vault protects credentials, the gate governs actions.

The demand is explicit​

The builders this platform courts are asking for exactly this. In YC's Summer 2026 batch launch material, Zomma states it plainly: "Every action stops for human approval before anything submits." Alloovium, in the same batch, ships the same posture: "nothing AI-drafted moves without a human sign-off." Anthropic's own advice in Building AI agents for startups points the same direction: start "in areas where human oversight already exists and imperfect automation won't create major problems."

The gate in production​

  • Duvo's procurement agents operate SAP and supplier portals for multi-billion-euro retailers with human-in-the-loop approval, and persist each approval decision so the same question is not asked twice. (source)
  • Eve Legal's overnight agents end at a gate by design: "When you wake up, you're approving legal work that has been done overnight." (source)
  • Notion routes finished agent work to a named approver: "our platform routes them to the right person for approvals." (source)
  • Twilio's Feature Factory story shows the gate as a dial rather than a switch: "On day one, I had human approval gates after every pipeline phase. Six interruptions per feature. By day 45, the system ran headless: no human in the loop, real phone calls, real validation." (source)

The Twilio arc is the mature version of the pattern: gates everywhere at first, then removed one at a time as validation earns the removal, never assumed away up front.

Further Reading​