Running multi-agent setups for 8 months: The message bus mattered more than the agents
__hymn · reddit · 2026-08-20
The author shares lessons from running a multi-agent setup for eight months. The key finding is that coordination, not the agents themselves, is the bottleneck. Successful strategies include:
- Message Bus over Shared Memory: Using a "post office" directory of JSON message files instead of shared state makes coordination bugs inspectable.
- Separate Identity from Log: Agents read a canonical identity file first, then dated logs, preventing role signals from being buried in history.
- Human as Tiebreaker: State conflicts escalate to a human overseer, preventing silent corruption from self-arbitration.
- Heartbeats and Recovery Protocols: Defining a protocol for missed heartbeats is essential to detect system failures.
- Preventing Looping Summaries: Enforcing that log entries must contain new facts avoids "busy but empty" looping behavior.
The remaining unsolved challenge is the gap between "saved" and "remembered correctly".
More from coding & agent
- YC's codebase hits 4M lines, adding 2M and 350+ internal AI tools since March — garrytan · 2026-08-20
- Turn Grok Bot Into CTO: Autonomous Agent Recruitment with 2 Prompts — elonmusk · 2026-08-20
- Latent On-Policy Self-Distillation Enables Self-Improving Agents — burkov · 2026-08-20
- Using Qwen 3.8 27B for agents/coding? Which harness works? — BackyardAnarchist · 2026-08-20
- X.ai launches Grok Build: A local coding agent with MCP and plan view — elonmusk · 2026-08-20
- Using Grok Agents to Audit and Negotiate Monthly Subscriptions Automatically — tetsuoai · 2026-08-20