Human in Loop
Human in the loop is an AI UX pattern that requires human review or approval before the model executes a consequential action. The AI drafts, proposes, or stages work; a person confirms, edits, or rejects before send, purchase, deploy, or other irreversible effects. Use it when errors are costly and trust depends on visible control.
When to use
Essential for email clients, code generation tools, and applications where human oversight of AI actions prevents errors and builds trust.
When not to use
- Low-stakes, easily reversible suggestions where approval friction slows the user more than it protects them.
- Fully autonomous monitoring or batch jobs where the product already has hard budgets, rollback, and clear failure alerts.
- Every micro-edit in a creative canvas; prefer selective gates on publish, send, or spend instead.
Anti-patterns
- Silent auto-send or auto-apply with only a buried undo.
- Approval UI that does not show the exact payload (email body, diff, amount) being approved.
- One global “always allow” that never re-prompts for higher-risk actions.
- Approval after the side effect already happened.
How products use it
| Product | Implementation |
|---|---|
| GitHub Copilot | Suggests code in-editor; human accepts, rejects, or edits before commit. |
| Gmail Smart Compose | Inline completions stay draft until the user sends the message. |
| ChatGPT | Agent and connector flows ask before sending email or taking external actions. |
| Gemini | Approval cards and send gates for actions that leave the chat surface. |
Use this pattern in your project
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Human in Loop" AI interface design pattern.
Pattern Definition:Reply to
Team standup invite
Real-world examples
How shipped products implement human in loop, from our teardown guides.
Frequently asked questions
What is human-in-the-loop AI UX?
Human-in-the-loop UX means the AI proposes or stages an action and a person must review and approve before it executes. It is the primary control pattern for email send, purchases, code apply, and other irreversible or high-cost outcomes.
When should I require human approval for AI actions?
Require approval when the action is hard to reverse, spends money, contacts other people, changes production systems, or carries compliance risk. Skip or lighten approval for low-stakes, local, easily undone edits.
How is human-in-the-loop different from autonomy budgets?
Human-in-the-loop gates a specific action with an explicit review. Autonomy budgets bound how long or how many steps an agent may run unattended before pausing. Many agent products need both: budgets for the run, approval for high-impact steps.
What should an approval card show?
Show the exact action, target, and content (recipient, diff, amount, tool), plus clear Confirm and Cancel. Hide nothing the user is authorizing. Optional edit-in-place beats approve-then-fix.