Multi Agent Coordination Bench · Shreyas Pimpalgaonkar, Kartik Sharma, Carlos Bonilla and colleagues, Bespoke Labs · Bespoke Labs, 2026
Eight agents with a message board did no better than eight working alone
MAC Bench is twelve four-hour tasks built so that each agent's work depends on its teammates'. In seven of them the team builds software in one shared repository. Opus 5.5, GPT-6.1 Sol and Gemini 4 Argon each ran in its developer's harness three ways: one agent, eight agents with a message board, and eight agents with no way to message. Averaged over the three models, a team of eight scored 0.42 and one agent 0.35. Eight agents without messaging added 0.087 over one agent. Allowing messages changed the score by -0.018, which the authors report as not statistically significant. Opus 5.5 was the exception: as a team of eight it reached 0.53, against 0.41 for GPT-6.1 Sol, though the two score about the same alone.
A team of eight cost 8.8 times as much as one agent at list prices and reached the single agent's final score a median 2.2 times sooner. In teams of two, 22% of tool calls already went to the message board. A teammate changed course within five minutes on 34% of 1,087 sampled findings. Duplicated work showed up in 64% of 139 team runs without damaging results; most damage came from messages nobody acted on and from parts that did not fit together. Claude models assigned the failure labels and checked them against the logs, and the harness has not been released, so outside readers cannot rerun the tasks yet.
Why it matters: Adding parallel agents to one task buys speed well below its cost, and on average the gain comes from extra workers, not from their messages. The failure tally points to interface ownership and acting on a teammate's findings as the places to add structure.