Agent Coordination Overhead (Supervisor vs. Workflow)

The runtime/token cost of having an LLM dynamically decide agent invocations and arguments step-by-step (supervisor/ReAct-style) versus following a deterministic, pre-declared execution path (workflow/plan-and-execute-style) — the same correct outcome reached at multiples of extra latency when coordination decisions are left to the LLM at runtime. Distinct from coordination-cost (human-side organizational coordination).

Also known as: LLM-induced coordination overhead, supervisor overhead, ReAct vs. plan-and-execute, dynamic vs. declared agent coordination

Documents (1)

• A harness for every task: dynamic workflows in Claude Code Thariq Shihipar and Sid Bidasaria (Anthropic, Claude Code team) · 2026-06-02 source ↗ Reader 🖥️
  Because a single, continuously-running context window degrades on long, parallel, structured, or adversarial tasks through three specific failure modes — agentic laziness, self-preferential bias, and goal drift — Claude Code should let the model write and orchestrate a custom, task-specific multi-agent harness (a dynamic workflow) on the fly, rather than relying on one generic static harness for every task.

Propositions touching this concept (1)

By publication month, oldest first (extraction month when no publication date is known).

2026-07

• explicitIn a head-to-head comparison on the identical bug-fix task, the workflow (fixed-sequence) architecture completed the task about three times faster than the supervisor (autonomous) architecture — roughly two minutes versus more than six minutes — because the workflow eliminates the LLM-induced coordination overhead of a supervisor that must autonomously decide, at runtime, which sub-agent to invoke next and with what arguments.
  The Self-Building Agent: A LangChain4j Experiment · p3

Open gaps (1)

• incompleteThe headline feature — running independent agent tasks in parallel across tabs on the same codebase — is presented purely as removing a waiting bottleneck, with no discussion of how (or whether) the tabs coordinate on shared files, detect conflicts, or share context, and no acknowledgment that the developer must still review and integrate three concurrent outputs rather than one.
  Android Studio Quail 2 Redesigns Agent Mode, Streamlines AI-Assisted Coding — read next: Compare with extract-fowler-orchestrators-tax (parallel agent wall-clock speedup is 'a visible byproduct, not the interesting part' of a session's cost/benefit) and the orchestration-tax concept generally: parallelizing generation does not remove the human as the serial bottleneck for review and integration.