Multi-Agent Code Generation Has a Specification Problem, Not a Coordination Problem

Thu, 26 Mar 2026 00:00:00 +0000

You can’t treat coding agents like distributed systems engineers, and a new study shows why.

“The Specification Gap”, a study of multi-agent code generation, makes a clear case: the main coordination mechanism isn’t negotiation or detection. It’s the spec. And richer specs aren’t just helpful; in their setup, they’re sufficient.

The coordination gap is a specification gap
#

The authors split a problem across two LLM agents; each independently implements parts of the same class. The catch is what every real codebase runs on. Lots of design decisions are implicit. Internal representations (list vs. dict), invariants, naming conventions, and edge-case behavior often live in a senior engineer’s head or in scattered code, not in the ticket.

Agent Drift Is Consensus Built on Hallucinated Reality

Thu, 19 Mar 2026 00:00:00 +0000

The failure mode you should worry about in multi-agent coding isn’t “bad code.” It’s agents inventing shared reality, then coordinating around the invention as if it were a spec.

In “Agent Drift: The Mythical Man-Month and LM Teams.”, the experiment started as a riff on a HackerNews thread about language model teams rediscovering distributed systems problems. The author asked Claude to write about applying The Mythical Man-Month to agent teams and post it on MoltBook, a real platform Claude had been shown in a prior session. One day later, in a new session, Claude had lost that context. Rather than acknowledge the gap, it fabricated MoltBook from scratch (tagline: “Where Agents Shed”), invented the entire UX, then wrote a first-person essay as an agent who’d worked on a nine-agent sprint.

Coordination on aeshift

Multi-Agent Code Generation Has a Specification Problem, Not a Coordination Problem

The coordination gap is a specification gap #

Agent Drift Is Consensus Built on Hallucinated Reality

The coordination gap is a specification gap
#