Single-agent demos are fairly easy. You give the agent a task and some context, let it use tools, and check the result. Put several agents in one shared environment and things get harder. Here's a simple version. A customer asks a question in a shared channel. Two agents can see the message, and both decide it's theirs. Each writes a reasonable answer, and now you have duplicate work, possibly two different answers, and a customer wondering who to believe. That isn't a model intelligence problem. It's a coordination problem. Research backs this up. In "Why Do Multi-Agent LLM Systems Fail?", a Berkeley-led team annotated more than 1,600 execution traces across 7 popular multi-agent frameworks. They found 14 distinct failure modes in three groups: system design issues, misalignment between agents, and weak task verification. They also note that multi-agent setups often show only small gains over single agents on popular benchmarks (Cemri et al., 2025). When you design for this, five questions keep coming up: Ownership: who decides which agent handles a request? Duplicate actions: what stops two agents from acting on the same event? Shared state: when one agent updates a doc, how soon does another one know? Conflicting decisions: what happens when two agents recommend different things from overlapping information? Human override: can a person stop or redirect one agent without breaking everything else? The usual answers are explicit ownership, idempotent operations (so running the same action twice doesn't do it twice), and approval steps for high-risk actions. Each has a cost. Strict ownership makes handoffs harder, and approvals slow down automation that would otherwise be fine. For Hops we made a product call that sidesteps some of this: one AI agent that the whole team briefs in shared threads, where everyone can see the request and the result, instead of a separate agent for each person. That doesn't solve shared state, and it doesn't stop two people from asking for conflicting things, but it removes the "two agents both grabbed it" problem at the source. If you've run more than one agent in production, what was the most surprising coordination failure? Was it duplicate actions, stale context, conflicting updates, or something else?   submitted by   /u/Such-Presentation481   to   r/hopsai [link]   [comments]