Human-in-the-loop
π Short definition
Principle that an agent or automated system may analyze and propose, but must wait for human validation before a critical action: merge, publication, deletion, access to sensitive data.
π Detailed definition
In an agentic workflow, the LLM can read files, call tools, produce a patch, or open a PR. Human-in-the-loop places a human as the control point before the irreversible step.
This differs from human-on-the-loop, where a human supervises after the fact. For a document vault or Git repo, the recommended model is hybrid: the agent may work on a branch, but merge stays human.
π‘ Why it matters for on-prem AI
On-prem does not guarantee safety by itself: a local agent can still delete, publish, or over-edit. Human-in-the-loop limits operational risk while keeping automation gains.
β οΈ Common pitfalls
- Confusing notification with validation: receiving a report is not approving the action.
- Allowing automatic merge to
mainfor editorial tasks. - Letting an agent read archived plans and execute stale TODOs.
π Go deeper
π See also
System where an LLM drives tools and decisions itself to complete a multi-step task.Autonomous agent responsible for maintaining a vault, repository, or document corpus by proposing human-validated corrections.