Human in the loop means keeping a person inside the agent's decision path, so the agent proposes and a human approves, steers, or verifies before anything becomes final. It is the deliberate counterweight to full autonomy.
Where the human sits
The loop can be threaded at different points:
- Before an action: a permission request that waits for your yes.
- After the work: a human review of the diff before it merges.
- Mid-task: stepping in to redirect when the agent drifts off course.
Why keep the human in
Models are fast and confident but not reliable. They hallucinate, they agree too easily, and they miss context you never gave them. A human in the loop catches the class of mistake automated checks cannot: the change that technically passes but is not what you wanted. That is a judgment call, and judgment is the thing models are worst at.
The cost is your time and attention, which is exactly what agents are meant to save. So the real question is not whether to keep a human in the loop but where. Put the person at the decisions that are expensive to get wrong, and let the agent run free everywhere else. Taking the human out entirely is AFK working, and it only becomes safe once strong guardrails have replaced the judgment you removed.
Related terms
Permission request
A permission request is the moment an agent stops and asks you to approve a consequential action, such as running a command or writing a file, before it happens. It is the seam where a human can catch a mistake before it lands.
Read definition →AFK
AFK means running an agent unattended for long stretches while you are away from the keyboard. It is only safe with strong guardrails and automated checks, since no human is watching each step.
Read definition →Human review
Human review is a person actually reading what an agent produced, understanding it, and taking responsibility for shipping it. It is the final quality gate that tests and automated review can support but never replace.
Read definition →