Handling failure

Human in the loop and escalation

For high-stakes or low-confidence actions, put a human in the loop and design clean escalation paths, so the agent knows when to stop and ask.

Not everything should be autonomous

Full autonomy is not always the goal. For irreversible, expensive, or sensitive actions, a confirmation step from a human is a feature, not a failure. The reliable design is one that knows which actions require a person and pauses for them.

Escalate on low confidence

When the agent is uncertain, or a guardrail or verifier flags a result, route it to a human instead of guessing. Confidence thresholds turn "the agent tried its best" into "the agent knew its limits and asked," which is what users actually trust.

Make escalation clean

An escalation path is only useful if it is clear: who gets the handoff, with what context, and how the agent resumes afterward. Design the handoff as carefully as the automation.

Key takeaways

  • Require human confirmation for irreversible or high-stakes actions.
  • Escalate on low confidence or flagged results instead of guessing.
  • Design the handoff: clear owner, full context, and a clean resume.