The First Version Was Too Naive
The first wave of multi-agent systems was mostly theatre. People imagined a room full of autonomous agents debating, writing, reviewing, planning, and magically converging on the right answer.
In practice, it usually broke.
The problem was not that the models were stupid. The problem was that every agent made its own hidden decisions. One agent chose a style. Another chose a different edge case. A third invented a slightly different interpretation of the task. By the end, the system had many pieces of work, but no single mind holding the product together.
This is why most useful agent systems stayed simple for a long time. One agent did the work. Other tools helped with search, retrieval, or analysis. It was not very glamorous, but it was much easier to trust.
Parallel Work Creates Parallel Decisions
The hard part of software is rarely typing code. The hard part is making decisions.
When multiple agents write at the same time, they do not just produce more code. They also produce more decisions. Some of those decisions are explicit, but many are hidden inside the implementation.
This is where systems become fragile.
An agent deciding how to handle permissions is making a product decision. An agent choosing what error state to show is making a UX decision. An agent deciding which abstraction to reuse is making an architecture decision.
If five agents make those choices independently, you do not get five times the output. You get five competing versions of the product.
The Pattern That Works
The practical pattern is not a swarm. It is a manager.
One agent should own the main thread of work. It holds the user goal, the plan, the tradeoffs, and the final decision-making. Other agents can help, but they should contribute intelligence before the main agent takes action.
This gives you the benefit of multiple perspectives without fragmenting ownership.
A reviewer can inspect the diff with fresh eyes. A research agent can find missing context. A stronger model can be called in when the primary agent is uncertain. A planning agent can challenge the approach before implementation begins.
But the write path should stay narrow.
This is the difference between collaboration and chaos. The system can use many minds, but it still needs one place where judgment is synthesized.