THE AI AGENT FIELD GUIDESOURCES FIRST. CLEARER CHOICES.
CONCEPT GUIDE

Human-in-the-loop AI workflows

Place review before consequential actions. Compare approval patterns and LobeHub batch review, with a checklist for authority, evidence and limits.

What the term means here

A human-in-the-loop workflow pauses, escalates or requests approval at a defined step. Review is useful only if the person sees the relevant context and can change or reject the proposed action.

Two documented patterns

n8n advertises human approval checkpoints and execution inspection. Tidio Lyro describes configurable escalation and real-time intervention. These are different forms of oversight; a handoff does not automatically approve an account action.

Supervised is not professionally reviewed

A software approval feature does not establish that a doctor, lawyer or other qualified professional assessed an output. This site records professional review separately from product functionality.

Design a review checkpoint

Show the proposed action, source evidence, target account and cost implications. Decide who may approve, when to time out and how to route a failure. Test those conditions before expanding access.

LobeHub v2.2.20: review before scaling a batch

The October 18, 2026 release provides a concrete example in its probe-based Goal batch path. A Goal created from a conversation starts as a draft and needs an explicit start before dispatch; this does not describe every creation path. After small probe tasks, the first move into mass execution in each round waits for the owner to review the plan and probe deliveries. Later waves go to the main Agent, which can release them or escalate to the owner. If no main Agent can take that review, the owner is asked. It is therefore not a human approval requirement for every wave.

Approval routing in the released probe-based batch path
StageDecision routeReview focus
First mass wave of each roundOwner reviewProbe deliveries and the plan that will be repeated
Later waveMain Agent releases or escalates; owner if unavailableCompleted wave, gate checks and next-wave scope
Owner sends plan backMain Agent rewrites; owner reviews againThe changed plan; completed probes are not rerun by this action
Batch breaks and is revisedA new probe round precedes scaling againCorrected recipe and reopened units

A checklist for the reviewer

Inspect the actual deliveries, not just a green completion label. The released review dossier captures the plan revision, unit artifacts and status, available acceptance checks, recorded runs and tokens, gate checks, and the next-wave roster. Before approving, verify that the sample covers meaningful input variants, that the proposed targets and batch size match your authority, and that escalation has an available owner. Check budget and rollback arrangements separately: recorded tokens are not a complete cost estimate, and this checklist is an editorial recommendation, not a claim that LobeHub enforces every item.

Revision, failure and the limits of a gate

Two return paths matter. Sending a plan back from the release review asks the main Agent to rewrite it and returns the revised plan to the owner on the review; that action does not rerun completed probes. A broken batch handled through the separate revise/restart path updates the recipe and opens a fresh probe round before scaling. The code also supports other rollout paths, so this example is not a universal approval guarantee. Gate checks concern recorded unit completion, open decisions, plan presence and declared variant coverage; the tagged evaluator does not validate external CI or a remote merge. A passed gate is a decision checkpoint, not proof of safe execution or a security certification.

Source and evaluation boundary

This example is a review of official release notes and source at LobeHub commit 49204982cab98bfa2f2fb6831a34d5018a2af6be, checked October 18, 2026. We did not install LobeHub, run a Goal or measure its performance. Validate your deployed version, permissions and failure handling with a small reversible workflow before relying on the pattern.

Continue your comparison

Compare workflows and agents →

Evaluate an AI agent with a small trial →

Explore agent workflow building →

Discuss a workflow evaluation →

Related products and tasks

n8n · Explore the related task →

Tidio Lyro · Explore the related task →

Sources supporting this guide

  1. Official product information

    n8n · n8n.io · Read · 2026-10-01

  2. Official pricing and deployment options

    n8n · n8n.io · Read · 2026-10-01

  3. Official product information

    Tidio · www.tidio.com · Read · 2026-10-01

  4. LobeHub v2.2.20 release

    LobeHub · github.com · Read · 2026-10-18

  5. LobeHub batch release review change (PR 20917)

    LobeHub · github.com · Read · 2026-10-18

  6. LobeHub draft/start change (PR 20840)

    LobeHub · github.com · Read · 2026-10-18

  7. Pinned release routing and plan revision implementation

    LobeHub · github.com · Read · 2026-10-18

  8. Pinned review dossier implementation

    LobeHub · github.com · Read · 2026-10-18

  9. Pinned batch gate checks and limits

    LobeHub · github.com · Read · 2026-10-18

  10. Pinned broken-batch restart implementation

    LobeHub · github.com · Read · 2026-10-18

  11. Pinned conversation-created Goal start implementation

    LobeHub · github.com · Read · 2026-10-18

Research method & original evidence · Who operates uAgentKit · Commercial disclosure

Suggest a correction →