XIV · Anti-PatternsEmerging★

Supervisor Cognitive Overload

also known as Human-Supervisor Bottleneck, Parallel-Agent Attention Saturation, 認知負荷オーバーロード

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.

Context

A team adopts a multi-agent setup to parallelise work — several sub-agents each handling a slice of a larger task. To keep them on track, the design routes every sub-agent's questions, clarifications, and approvals back to one human. As the number of concurrent agents grows, that human is expected to hold context on all of them at once and reply to each.

Problem

Parallel agents multiply the supervision surface faster than a human can absorb it. Each agent needs context-setting, mid-task clarification, and review; when all of that lands on one person simultaneously, the supervisor thrashes between agents, loses track of which said what, and either rubber-stamps to keep up or becomes the slowest part of the system. The parallelism that was supposed to speed things up is throttled by a single human's working memory.

Forces

  • More concurrent agents mean more parallel demands on one supervisor's attention.
  • Human working memory and context-switching capacity are fixed and small.
  • Sub-agents still need steering, so oversight cannot simply be removed.
  • Rubber-stamping to keep pace defeats the purpose of having a human in the loop.
  • Aggregating agent state for the human costs design effort that is easy to skip.

Example

A developer runs a spec-driven setup that spawns five sub-agents, each pinging them for clarification on its slice of the build. Within an hour they are switching between five chat threads, losing track of which agent was told what, and approving diffs they have not really read just to keep all five moving. The five-way parallelism that promised speed has collapsed into one exhausted human serialising everything through their own attention.

Diagram

Solution

Therefore:

Recognise the anti-pattern and redesign the oversight surface. Insert an aggregation layer between the agents and the human: batch and summarise sub-agent status, surface only the decisions that genuinely need a human, and let a lead agent or orchestrator absorb routine clarifications. Cap the number of agents one person supervises, or move from per-agent conversation to a single dashboard with prioritised exceptions. The corrective patterns are selective escalation and a coordinating layer, not more human bandwidth. Japanese practitioner reports flag this directly: when the human must talk to every agent, cognitive load becomes the limiting factor.

What this pattern forbids. The system must not require a human to hold live context on, and individually converse with, every concurrent sub-agent; supervision has to be aggregated and selectively escalated so the human's attention surface stays bounded as the agent count grows.

And the patterns that stand alongside it, or against it —

  • complementsOrchestrator as Bottleneck✕— Anti-pattern: route all agent runs through a single-process orchestrator that becomes the system-wide concurrency ceiling.
  • complementsUnbounded Subagent Spawn✕— Anti-pattern: a supervisor or orchestrator spawns sub-agents that can themselves spawn sub-agents without a global cap.
  • complementsRole-Typed Subagents✕— Anti-pattern: pre-allocate roles (manager, coder, designer, researcher) across a fixed set of typed sub-agents and route tasks to them by role label.

Neighbourhood

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

References

Provenance