Building Multi-Agent Fleets That Actually Talk to Each Other

The consensus architecture for multi-agent systems in 2026 is: orchestrator + isolated subagents. A single coordinator holds context, spawns specialists, merges results. You've probably built something like this. A coordinator agent fans out to a research subagent, a code-generation subagent, maybe a QA subagent. The orchestrator waits, collects, synthesizes. It works. But there's a hidden assumption baked into most implementations: agents communicate through you. The coordinator is the hub. Every message routes through your application code. Subagents don't know about each other.