Skip to content
Level up your prompts with SurePrompts — curated prompts for every workflow.
agentscamp

Human-in-the-Loop (HITL)

Human-in-the-loop design inserts human judgment at decisive points in an AI workflow — approving actions, resolving ambiguity, owning the irreversible steps.

Updated

Human-in-the-loop design places human judgment at chosen points inside an automated workflow: the agent executes, but designated decisions wait for a person. The question is not whether to trust an agent but which steps need a signature, namely the irreversible, the ambiguous, and the consequential. Blanket approval prompts are the anti-pattern.

Human-in-the-loop (HITL) is the design principle of placing human judgment at chosen points inside an automated AI workflow — the agent executes, but designated decisions wait for a person.

It's the practical answer to the autonomy question: not whether to trust an agent, but which steps require a human's signature. Good HITL design is surgical — gates at the irreversible (deploy, pay, delete, send), the ambiguous (low confidence, conflicting inputs), and the consequential (plan approval before a large change), with everything routine left to run. The anti-pattern is blanket approval prompts, which produce click-through fatigue and less real oversight than a few sharp gates.

Mechanically, gates range from interactive prompts (Claude Code's permission system is HITL built into the harness) to asynchronous approval steps in pipelines — pause, notify, resume on sign-off. Adding one to an agent is packaged work: the human-in-the-loop-gate skill designs the checkpoint, and the add-human-approval command scaffolds it.

Frequently asked questions

Where should the human be in the loop?
At the points where errors are expensive or irreversible: before deploys, payments, deletions, and external sends; when the agent's confidence is low or inputs are ambiguous; and at plan-approval time for large changes. Everywhere else, approval friction just trains people to click yes — gate the decisive moments, automate the rest.
Does human-in-the-loop defeat the point of agents?
No — it's what makes real autonomy shippable. A well-placed gate converts 'we can't let an agent do this' into 'the agent does 95% and a human owns the 5% that matters.' The failure mode to avoid is rubber-stamping: too many low-stakes approvals and the human stops reading them, which is worse than fewer, sharper gates.

Filed under

hitl · agents · safety · workflow

Related