Human-in-the-loop vs human-on-the-loop

Key takeaways

• HITL blocks execution until a human approves. HOTL lets the agent run but keeps humans watching.
• Choose HITL when the action is hard to reverse or directly affects a customer.
• Choose HOTL when the action is routine, monitored, and cheap to undo.
• Most production systems mix both - HITL at checkpoints, HOTL on everything else.

Human-in-the-loop

Human-in-the-loop (HITL) means the agent pauses and waits for an explicit human decision before the risky action executes. This is the right model when the action is high-impact, hard to reverse, or touches a customer or financial system directly.

Human-on-the-loop

Human-on-the-loop (HOTL) means the agent runs autonomously, but humans have visibility into what it is doing and a fast path to stop or override. This fits lower-risk automation with strong monitoring and an easy rollback path.

Choosing between them

• Pick HITL for money movement, HR actions, destructive operations, and policy exceptions.
• Pick HOTL for lower-risk automation with strong monitoring and rollback.
• Use both in the same workflow - HOTL by default, HITL at specific checkpoints.

Frequently asked questions

Can the same workflow use both models?

Yes. Most production systems do. Agents run autonomously for low-risk steps and pause for explicit approval at specific checkpoints.

How do I decide which steps get HITL?

Use the four-question test: does money move, does a human feel it, is it reversible, is there a policy owner. A yes on any one means HITL.

Does HOTL work without good observability?

No. HOTL depends entirely on humans being able to see what the agent is doing in time to intervene. Ship the monitoring first.

Related resources