Sub-Agents Are Not the Only Way

One agent sits at the top, holds the plan, and hands work down to sub-agents that report back to it. Coding assistants ship it by default, so it has quietly become the way people assume a multi-agent system is supposed to look. It is not the only way! An orchestrator is a single point of everything. It is the bottleneck, because every decision routes through it. It is the memory, because the sub-agents are disposable and forget the moment they return. It is the failure mode, because when the top agent loses the thread, the whole tree below it keeps working toward a plan that no longer exists. You have rebuilt the org chart, with all of its old problems, and handed it to a model that hallucinates. There is another shape. **What if no agent is in charge?** Each agent can orchestrate itself, and coordinate by leaving messages on a shared bus. An agent posts what it learned, reads what its peers posted, and decides its own next move. Nobody holds the master plan, because the plan lives in the open, on the board, where everyone can see it. This is closer to how a good team actually works. You do not ping the manager between every step. You glance at the channel on Slack or Teams, notice someone already handled the thing you were about to start, and adjust. Coordination is ambient. It happens through a shared surface rather than a chain of command. That is why we built a feature which we call Blueprint Bulletins. Every blueprint (effectively a collection of agent resources) gets a shared message board. Agents post short, self-expiring notes and read what their peers left. An agent can flag that a long task finished, drop a hint before a handoff, or record a decision the others should know about. The board is the coordination layer, and no agent has to own it. I am not declaring sub-agent orchestration is dead. We support it too, and some problems genuinely want a coordinator with one clean plan instead of a noisy board. The point is that you get to choose. The orchestrator and its sub-agents are one pattern among several, and they became the assumed answer because they happened to ship inside the tool you write code with. The interesting architectures are still ahead of us.