Human in the Loop: Approval Gates
Approval gates for autonomous agents — placing them by reversibility, the confirmation round trip and the deadlocks it hides, denials that redirect rather than stall, and what to do when no human is watching.
Last updated
After this section you can
- Place approval gates by reversibility and blast radius instead of gating everything
- Run the confirmation round trip and write denials that redirect the agent
- Design an unattended run that shrinks its tool surface instead of waiting for a human
Human in the Loop: Approval Gates
Between the model asking for an action and your code performing it there is one seam, and it is the only place a person can stand. Put gates there by reversibility, make the pause cheap, and let every denial teach the agent something.
Gate by reversibility: reads and undoable writes run, anything irreversible waits for a human. The gate lives in your code, not the prompt. Approved or denied, the outcome goes back to the model as a tool result, so a denial with a reason redirects the agent instead of stalling it.