Glossary · term

Automation bias in agentic AI

Automation bias in agentic AI is the tendency of a person responsible for reviewing, approving, or supervising an AI agent to over-rely on the agent's recommendations, plans, or actions and to miss or insufficiently challenge errors. The agentic context matters because agents can execute long, fast, multi-step workflows through tools, making sustained attention and step-by-step verification difficult. The term describes a human-automation interaction risk, not bias encoded in the model's training data.

Culture2025-09-11Wave 3 · 2025–26Maturity: 3/5

Origin and context

The EU AI Act codified awareness of automation bias as one element of human oversight for high-risk AI systems, while a 2025 systematic review synthesized experimental evidence across human-AI decision settings. Partnership on AI then documented the agentic extension: longer workflows, speed, scale, and direct action can erode attention and make nominal human review a bottleneck. IMDA's 2026 agentic-AI framework independently described automation bias as a larger concern with increasingly capable agents and recommended locating significant approval checkpoints and auditing whether oversight remains effective.

Sources: s1, s2, s3, s4

Why it matters

Giving a human an approve button does not guarantee meaningful control. Reviewers can habituate to mostly correct proposals, rush repeated alerts, or lack the time and context to reconstruct a long chain of agent decisions. If approval gates become ceremonial, an agent may modify files, send messages, change records, or initiate transactions despite an error that a nominal human-in-the-loop design was meant to catch. This risk links interface design, permissions, workload, monitoring, training, and accountability. It also explains why blanket approval of every step can be counterproductive: too many low-value interruptions may weaken attention at the steps that matter most.

Sources: s1, s2, s3

Example

A procurement agent prepares dozens of routine purchase actions and occasionally proposes a high-value irreversible transaction. Requiring the same hurried click for every action can produce alert fatigue and automatic acceptance. A risk-calibrated workflow can reserve explicit approval for high-stakes or hard-to-reverse steps, show the evidence and intended effect, let the reviewer override or halt execution, and monitor override rates and response times. These controls may improve engagement, but they do not prove that automation bias has been eliminated.

Sources: s1, s2, s3, s4

How it differs

Algorithmic Monoculture

Algorithmic monoculture concerns correlated dependence on similar models or decision systems across many actors. Automation bias concerns how human overseers rely on automated outputs in a particular interaction or workflow. The two can compound but are not synonyms.

LLM sycophancy

Sycophancy is a model behavior that agrees with or flatters a user. Automation bias is the human tendency to over-rely on automation, including agents that are not sycophantic. Agreeable output may worsen overreliance, but neither condition requires the other.

Maturity and evidence

Maturity is rated 3. Automation bias has a substantial research base, explicit legal recognition in EU high-risk-system oversight, and two independent sources now applying it directly to AI agents: Partnership on AI in 2025 and IMDA in 2026. The agentic application is still recent, and the reviewed sources do not establish a universal incidence rate or a proven single control pattern across agent architectures and deployment contexts.

Sources: s1, s2, s3, s4

Limits and open questions

Overreliance should be measured rather than inferred from any acceptance of agent output; correct reliance can improve performance. Explanations, transparency, or extra approval prompts can sometimes add cognitive load instead of reducing bias. Evidence from traditional decision-support settings does not transfer automatically to every autonomous workflow, and the agent-specific guidance remains developing. Legal duties under the EU AI Act apply only within the Act's scope, while IMDA's framework is governance guidance rather than a universal legal standard. Controls must be matched to stakes, reversibility, user expertise, workload, and system affordances.

Sources: s1, s2, s3, s4

Related terms

References

Last updated: 2026-09-05

In the Skills Atlas

This term is also covered in the Skills Atlas as human in the loop ai skill.

In the Skills Atlas

This term is also covered in the Skills Atlas as ai risk management skill.

In the Skills Atlas

This term is also covered in the Skills Atlas as model evaluation skill.