Qodo Engineers Explain Dark Factory: Why Multi-Agent Collaboration Needs a Communication Space Separate from Execution

When building autonomous software engineering agent teams, a common misconception is that enabling agents to call each other constitutes collaboration. In an article published on October 6, 2026, Dr. Ofir Friedman, Senior AI Engineer at Qodo, and Amir Zaushnizer argue through their internal system, Dark Factory, that this point-to-point delegation model has fundamental flaws. They found that while protocols like A2A allow agents to be discovered and delegated to, they do not describe what happens when multiple participants need to hold a single evolving understanding of the same problem.

Friedman and Zaushnizer explain that true collaboration requires shared conversation, membership, and a common history readable by late-arriving participants. Without a shared collaboration layer, connecting agents across different environments necessitated custom request endpoints, polling mechanisms, and state management. This not only increased integration complexity but, more importantly, failed to create meaningful collaboration—agents were executing tasks rather than sharing an evolving understanding or challenging assumptions.

To address this, Qodo developed BAND, an interaction layer described by the authors as 'Slack for agents.' BAND does not orchestrate agents or replace underlying frameworks but provides persistent identities, chat rooms, and deterministic message routing. In the Dark Factory architecture, the SWE agent responsible for planning and implementation, the independent Reviewer agent, and the SRE agent with access to production logs all operate as distinct participants within the same BAND room. This design allows the SRE agent to contribute production evidence without moving privileged credentials into the SWE environment, while keeping the Reviewer independent from the author.