XIV · Anti-PatternsAnti-pattern✕

Infinite Debate

also known as Stuck Multi-Agent, Convergence Failure, Agents Stuck Talking, Multi-Agent Loop

Anti-pattern: launch multi-agent debate without a termination rule and watch the agents loop forever.

Context

A team sets up a multi-agent debate or consensus pattern — for example a proponent, a skeptic, and a synthesiser — so that several agents argue a question before producing a final answer. The orchestrator is written with the assumption that the agents will eventually agree on their own and the loop will naturally end. There is no explicit round cap, no judge that emits a terminal verdict, and no measurable convergence signal between rounds.

Problem

Without a termination rule, debate converges only by accident; far more often the agents keep finding new angles to disagree on, restate prior positions, or politely circle the same point indefinitely. Token cost and latency grow linearly with rounds while real progress on the answer stalls, and the loop ends only when an outer cost limiter or a timeout intervenes. The team is left with an expensive run, no decision, and no clean way to tell whether two more rounds would have helped.

Forces

  • Consensus heuristics are easy to game.
  • Round caps cut off legitimate convergence.
  • Judge agents become the new bottleneck.

Example

A research team sets up a three-agent debate to answer policy questions: a proponent, a skeptic, and a synthesiser. They forget to add a termination rule. The first run burns through 90 minutes and $34 of tokens with the proponent and skeptic still circling each other when an engineer kills the process. They name the failure infinite-debate and add a round cap of six exchanges plus a judge that emits 'agreement', 'irreducible-disagreement', or 'continue', with continue allowed at most once. Cost becomes predictable.

Diagram

Solution

Therefore:

Don't. Add a round cap and a termination predicate. Pair debate with a judge or aggregator. See debate, step-budget, the-stop-hook.

What this pattern forbids. By definition, this anti-pattern imposes no useful constraint; the missing constraint is the failure mode.

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

  • alternative-toDebate·— Have multiple agents argue different positions on a question and converge through structured exchange.
  • alternative-toStep Budget★★— Cap the number of tool calls or loop iterations the agent is allowed within a single request.
  • alternative-toStop Hook★★— Define an explicit programmatic predicate that decides when the agent's loop should terminate.
  • conflicts-withCommunicative Dehallucination★— When an instructed agent would have to invent missing context to comply, have it reverse roles and ask the instructor for the missing detail before answering.
  • complementsDecision Paralysis✕— Anti-pattern: when given equally-weighted conflicting goals, the agent either gets stuck trying to satisfy all simultaneously or oscillates between solutions without converging — the most common LLM response to genuine goal conflicts.

Neighbourhood

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

References

Provenance