What is human-in-the-loop?
Human-in-the-loop means an automated AI system pauses at critical steps and waits for a person to approve, correct or decide. In coding agents it usually takes the form of permission prompts before editing files, running commands or publishing anything.
What it looks like in coding agents
Most agents ask before risky actions such as editing a file, running a shell command or fetching from the network. In Claude Code, permission rules (allow, ask, deny) and permission modes control this; in plan mode, for example, the agent only plans and doesn’t change files. Codex has its own approval and sandbox settings.
Where approval is a must
Rather than asking everywhere, put approvals where mistakes are expensive.
- Irreversible actions: git push, publishing, deleting data, migrations.
- Actions that reach the outside world: email, payments, production servers.
- Access to secrets: .env files, keys, customer data.
- The plan: approving it before a big change saves hours heading the wrong way.
Approval fatigue
When every file read needs a click, people start saying yes without looking, and approval stops meaning anything. The fix is to auto-approve safe work like reads and tests and always ask about the truly risky actions. Options that skip all permissions, such as Claude Code’s --dangerously-skip-permissions flag, belong only in isolated environments.
Approving remotely
On long jobs, agents may ask for approval while you’re away. Notifications and approving from your phone keep an agent from sitting idle for hours, and seeing every waiting agent in one queue speeds things up when you run many at once.
Human approval in AgentVera
AgentVera gathers approvals in one place and makes sure only the ones that matter reach you.
- Approval queue: the status bar counts agents waiting for approval and ⇧⌘A jumps to the one that has waited longest; there are desktop notifications and a Dock badge too.
- Telegram: approve or reject flow steps from your phone.
- Auto approval answers Claude Code’s read, test, lint and read-only git requests without asking, while commands such as git push, rm and git reset --hard always come to you (Pro and Team).
- The Human approval node in flows and the plan approval in Research, plan, build hold the work until you approve.
FAQ
Should I let an agent do everything without approval?
Usually not. Auto-approving safe, reversible work makes sense; pushes, deletes and anything touching production should go through you.
What is approval fatigue?
It’s when prompts come so often that people approve without reading. Automating the safe ones means the remaining approvals get real attention.
What’s the difference between human-in-the-loop and human-on-the-loop?
In the first, the system stops at critical steps and waits for approval. In the second, the system runs on its own while a person monitors and steps in if needed.