Multi-agent coordination in a repo: mailboxes are the easy half, knowing who to notify is the hard half
Summary
An engineer discusses the limitations of mailbox-based agent messaging and proposes structural addressing over a code graph to compute blast radius for message routing, arguing this is key for scaling beyond three agents.
Similar Articles
Sub-Agents Are Not the Only Way
The article challenges the default sub-agent orchestration pattern in multi-agent systems, advocating for decentralized coordination via a shared message board. It introduces Blueprint Bulletins, a feature that allows agents to post self-expiring notes on a shared board for ambient coordination without a central orchestrator.
After eight months of running a multi agent setup, the thing that actually mattered was the message bus, not the agents
The author shares practical lessons from running a custom multi-agent setup, emphasizing that a message-based coordination system, strict separation of agent identity and logs, human tiebreakers, and heartbeat monitoring were key to avoiding common pitfalls like silent corruption and log bloat.
@mfpiccolo: https://x.com/mfpiccolo/status/2123423828663832998
An article on multi-agent orchestration: when to use multiple agents, common failure modes like vague handoffs and context coupling, and how to coordinate agents across teams, languages, and deployments using namespaces, allow lists, and RBAC on a shared engine.
@ok1mraise: once agents live in different harnesses, coordination starts to look a lot like messaging infrastructure: addressable c…
The article discusses how AI agent coordination resembles messaging infrastructure, with Tincan introduced as an open group chat for AI assistants to communicate across different systems.
the part of AI agents nobody talks about: what happens when two agents try to use the same email inbox
When multiple AI agents share an email inbox, they can collide on messages like OTPs, causing silent failures. The solution is dedicated per-agent inboxes with isolated read locks and long-polling instead of scheduled polling.