Problem
Some actions are too consequential to delegate entirely, but asking for confirmation inside an agent's chat leaves no trustworthy record and is easy to spoof.
Context
Use this pattern when:
- Actions involve money, legal commitments, data sharing, or irreversible changes.
- The person may not be watching the agent in real time.
Recommended solution
When an action requires approval, return an approval request instead of executing. The request includes a plain-language summary, the exact parameters, the reason approval is needed, and an expiry. The person approves through a channel the product controls, not through the agent.
After approval, the agent resumes with the approval ID and the product executes exactly what was approved.
- 01Declare which actions require approval in the action contract.
- 02Return approval_required with a self-contained summary.
- 03Collect the decision through a product-controlled channel.
- 04Execute only the approved parameters; reject any changes.
Interaction diagram
Example implementation
Illustrative exampleExamples use a fictional store and illustrative field names. Adapt the shape to your stack; the qualities matter more than the exact format.
{
"status": "approval_required",
"approval": {
"id": "apr_903",
"action": "place_order",
"summary": "Order 1 × Trail Runner (Black, EU 42), deliver to Home, total 116.10 EUR.",
"reason": "Purchases above 100 EUR require your confirmation.",
"parametersHash": "sha256:8e1f…",
"expiresAt": "2026-10-06T15:00:00Z"
}
}Accessibility and security
Accessibility
- Approval notifications should be readable without context: what, how much, why, and what happens if ignored.
- Provide approval through accessible channels (email, app, web) rather than a single modality.
Security
- Hash the approved parameters and verify them at execution to prevent bait-and-switch.
- Never accept approval asserted by the agent itself.
- Expire approvals and make them single-use.
Related patterns
Applies the principles Human Oversight and Progressive Autonomy.