Human-in-the-Loop
Also called: HITL
Human-in-the-loop is a design pattern where an agent pauses to get a person's review or approval before or during a consequential action, rather than acting entirely on its own.
Human-in-the-loop (often abbreviated HITL) is how teams keep an agent's autonomy bounded without giving up the benefit of it acting on its own for most of a task. Instead of either doing everything unsupervised or requiring a human to approve every single step, an agent is designed to identify which actions matter enough to pause for — sending an email, merging code, spending money, deleting data — and check in only at those points.
Where the checkpoints go is a design decision, and it varies a lot by how costly a mistake would be and how reversible the action is. A coding agent might freely read files and run tests unsupervised but require approval before it pushes a commit; a support agent might freely look up account information but require approval before issuing a refund above some threshold.
Human-in-the-loop is closely tied to autonomy-level — it's essentially one specific mechanism (a review checkpoint) for implementing a chosen point on that autonomy spectrum, rather than a separate concept from it.
How it works
The pipeline in the diagram shows a common shape: the agent drafts an action — a proposed commit, an email, a refund — without yet executing it; that draft goes to a human review checkpoint, shown as the standout node in the diagram since it's where control actually passes to a person; and only after approval does the action get executed. If the human rejects or edits the draft, the agent typically revises based on that feedback rather than executing the original.
Example
An agent managing a project's dependencies might draft a pull request that upgrades a library version, but pause there and notify a maintainer rather than merging it automatically — the maintainer reviews the diff and the changelog, then either approves the merge, asks for changes, or rejects it.
How it differs
Human-in-the-loop is related to but narrower than autonomy-level: autonomy level describes a general spectrum from manual to fully autonomous, while human-in-the-loop specifically names the pattern of inserting a human review checkpoint at some point in that spectrum — a system can be 'mostly autonomous' and still be human-in-the-loop for its highest-stakes actions.
Common misconceptions
FAQ
What does human-in-the-loop mean in AI agents?
Does human-in-the-loop slow an agent down for every action?
What's the difference between human-in-the-loop and autonomy level?
Last checked: 2026-08-28