loading
loading
A checkpoint that requires a human, policy, or automated rule to approve an agent action before it runs.
Approval gates keep high-risk steps from becoming silent automation: sending email, spending money, deleting data, pushing to production, or calling a dangerous tool. The agent can prepare the action, but execution pauses until a human or policy engine approves it. Example: a coding agent may draft a migration, then wait for approval before running it against production.
Plainly
Think of Approval Gate as the lock and rules that keep people and data safe. A checkpoint that requires a human, policy, or automated rule to approve an agent action before it runs.
In practice
Use it when a workflow touches secrets, permissions, user data, payments, or untrusted input. In practice, define the owner, input, output, and failure mode before you rely on it.