XIV · Anti-PatternsAnti-pattern✕

Agent Output Alert Fatigue

also known as Boy-Who-Cried-Wolf Agent, AI Review Fatigue

Anti-pattern: an agent emits high-volume, low-precision findings that progressively desensitise its human reviewers until they mute it, so even its correct findings stop landing and the human-oversight control silently disappears.

Context

An agent is deployed as an assistive reviewer — posting code-review comments, raising alerts, suggesting fixes — behind a human who is meant to read and act on its output. To look thorough, the agent errs toward recall: it surfaces everything that might be an issue. Most of what it raises is noise.

Problem

When an agent floods reviewers with findings that are mostly low-value, the humans adapt by disengaging: first they skim, then they approve on autopilot, then they mute the agent entirely. The human-in-the-loop control that justified deploying the agent quietly evaporates, and the agent's genuinely correct findings are now discarded along with the noise. The damage is asymmetric — trust erodes faster from noise than from the occasional missed issue — and near-irreversible, because re-earning a reviewer's attention after they have learned to ignore the agent is far harder than losing it. A volume metric like comments-per-review actively rewards the behaviour that breaks the control.

Forces

  • Precision and recall trade off: erring toward recall to look thorough is what generates the desensitising noise.
  • Trust erodes faster from noise than from missed issues, so the asymmetry punishes over-flagging.
  • Higher precision usually costs more per finding, which a volume-oriented metric discourages.
  • Once reviewers disengage, re-earning attention is far harder than it was to lose it.

Example

A team adds an LLM code-review bot that posts every possible concern on each pull request — over eight comments per PR, barely a third of them useful. Within weeks developers stop reading them and approve on sight; a real bug the bot flagged ships because no one looked. The team raises the bot's confidence threshold so it posts about four comments per PR at roughly seventy percent usefulness, at higher cost per review. Developers start reading the comments again, and the bot's correct findings land once more because it stopped crying wolf.

Diagram

Solution

Therefore:

Gate the agent's output on confidence so it raises fewer, higher-precision findings; measure usefulness-per-finding, not findings-per-review. A documented post-mortem cut a review agent from 8.3 comments per pull request at 35 percent usefulness to 4.1 at 72 percent and restored reviewer engagement, accepting higher cost per review. Monitor reviewer engagement (resolve rate, mute rate, time-to-skim) as a first-class signal that the oversight control is decaying. Mitigation patterns: cross-encoder reranking or a verifier stage to filter low-value findings before they reach a human; confidence thresholds tuned to the asymmetry. Treat a rising comment count at flat usefulness as an alarm, not progress.

What this pattern forbids. No useful constraint; the missing constraint is a precision floor on agent findings and an engagement signal that treats reviewer disengagement as the oversight control failing.

The patterns that counter or replace it —

  • complementsHidden Validation-Work Amplification✕— Anti-pattern: an agent rollout shifts effort from doing the work to validating, monitoring, and recalibrating the agent — net productivity is negative because the hidden human evaluation burden exceeds the visible automation gain.
  • complementsSupervisor Cognitive Overload✕— Name the failure where a human must converse with and steer every parallel sub-agent individually, so oversight saturates the supervisor and the human becomes the bottleneck the multi-agent design meant to remove.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance