Human approval on agent actions: what fraction of your approvals are rubber stamps?
Summary
The author asks practitioners how effective human approval gates on agent actions really are — what fraction of approvals are genuine catches versus rubber stamps, how trust and fatigue evolve over time, and whether approval queues expose supporting evidence. The post highlights that an unread approval gate may just add latency rather than safety.
Similar Articles
How are you actually building approval gates for agents? I'm convinced most are meaningless rubber stamps
The author argues that many human approval gates for AI agents are ineffective rubber stamps, and proposes a framework for designing meaningful review mechanisms that actually catch errors.
The approval queue isn't the tax on your agents. It's the only part that makes them smarter.
The author argues that human approval queues for AI agents aren't overhead but the key training signal: teams that capture rejection reasons and let actions auto-graduate shrink their queues, while teams that disable them see their agents fail. Cites Gravitee's 2026 report that only 14% of teams ship agents with full security/IT approval.
Human approval is too vague for production agents
The article argues that human-in-the-loop in agent systems should move from vague approvals to explicit, auditable step-level signed decision records with detailed evidence, payloads, idempotency keys, rollback paths, and ownership. It highlights the danger of approving a black-box story rather than a specific operation.
Human approval is not a weakness in AI agents
The article argues that human approval is a critical mechanism for building trust and defining policy in AI agents, rather than a weakness to be eliminated. It suggests using approval patterns to iteratively expand agent autonomy safely.
Approval fatigue is the hard part of agents that work while you're away. What Claude Duet's published stop rules show
Anthropic's research preview of Claude Duet highlights its stop rules addressing approval fatigue: some actions like payments and deletions always require approval, with an out-of-model automated check guarding against prompt injection. The piece argues agents should be judged by their stop rules rather than feature lists.