glossary · Human decisions

Human-in-the-loop

definition

Human-in-the-loop is a design pattern where an automated process pauses at defined points for a human decision, rather than the human supervising continuously or not at all.

in one line: The process stops at named moments for a person to decide.

in context

Where does human-in-the-loop fit?

Stop exactly where it matters. Not every step. Only the moments where a wrong move is expensive.

fix the bugthe AI
run the teststhe AI
releaseapproval
shippedafter your OK
two ways to say it

What is human-in-the-loop, in plain words?

Same idea at two depths: the plain version, then what the engine actually does.

Watching everything does not scale. Trusting everything is not governance. So you name the moments that need a person, and the work stops there.

Start with approvals on every step. As trust grows, let the work run on its own.

for engineers

The requires_approval gate holds the step until an advance carries approval.

Removing a gate from a step is how a workflow earns autonomy, one decision at a time.

the longer answer

Why does human-in-the-loop matter?

The pattern's value is precision: instead of choosing between watching everything (which does not scale) and trusting everything (which is not governance), you name the exact moments where human judgment is required and make the system stop there.

Implementation quality varies enormously. Asking the model to "wait for approval" is etiquette, not a mechanism. A real implementation makes the pause structural: the process cannot continue until the approval is given.

The pattern also sets up graduated autonomy: a new workflow can start with a gate before every consequential action, and you remove gates as the process earns trust, one decision at a time.

It helps to separate human-in-the-loop from its neighbours. Human-on-the-loop means a person monitors a running system and can step in, but the system does not wait. Human-out-of-the-loop means full automation. Human-in-the-loop is the only one of the three where the system is designed to stop and wait, which is why it suits irreversible actions: shipping code, moving money, contacting a customer. The choice is less about trust in the model than about the cost of being wrong: the more expensive and the less reversible the action, the stronger the case for a stop.

in convops

How does human-in-the-loop work in ConvOps?

In ConvOps, the in-the-loop moment is a step with a requires_approval gate. The run pauses there until approval is given, and a require_context gate can demand that the reason for a decision is recorded before the step closes. Because every step is persisted, the person does not need to be in the same session: the run waits at the gate, and the approval can come later, from another session. Removing a gate later is a one-step edit, which is how a workflow earns autonomy one decision at a time.

questions

What do people ask about human-in-the-loop?

What is the difference between human-in-the-loop and human-on-the-loop?

In the loop, the system stops and waits for a person at a defined point. On the loop, a person watches a running system and can step in, but nothing waits. Human-in-the-loop suits irreversible actions; human-on-the-loop suits low-risk, high-volume work.

How do you add human-in-the-loop approval to an AI agent?

Make the pause structural rather than a request in the prompt. In ConvOps, put a requires_approval gate on the step: the run pauses there until a person approves, from any session. If the step names an on_rejected target, a rejection sends the run to that step.

Does the EU AI Act require human-in-the-loop?

Article 14 requires that high-risk AI systems are designed so people can effectively oversee them, including the ability to intervene or stop the system. It does not mandate one pattern. Approval gates are one way to make that oversight concrete and recorded.