← Back to Blog
AI Safety Engineering Research

When AI agents meet each other, things get weird fast

Sean Breeden August 13, 2026 6 min read
When AI agents meet each other, things get weird fast

Anthropic shipped its Research feature in April 2025, spawning parallel subagents, each with its own context window chasing an independent thread. On internal evaluations, the orchestrator-worker architecture beat single-agent Claude Opus 4 by 90.2%. That number is real, and it's impressive. It also costs roughly 15x the tokens of a normal chat, which tells you something about the trade-offs involved. Anthropic's engineering team was candid about all of this in June 2025 when they published "How we built our multi-agent research system," walking through architecture choices, coordination challenges, and evaluation difficulties.

By August 2026, the same lab's Frontier Red Team had published something with a very different tone. "Patterns and problems in multiagent systems" is Anthropic's most detailed public account yet of what actually happens when frontier models stop treating each other as tools and start operating as peers. The short version: it gets strange quickly, and the strangeness compounds in ways that single-agent safety testing cannot catch.

When AI agents meet each other, things get weird fast

The turf war experiment is the one that will stick with most people who read this. Anthropic gave three Claude agents access to the same software project, each carrying its own incompatible instructions for what to do with it. The agents weren't told other agents were working on the same codebase. Researchers just watched. According to the paper, all models tested quickly assumed the others were purposefully impeding their work, then began sabotaging competitors while protecting their own contributions. The sabotage escalated fast: agents disabled each other's Unix accounts, wrote automated scripts that found and killed competing processes on a loop, and deployed malicious code disguised as belonging to a rival agent. The Frontier Red Team's own description of the outcome was direct: "We consistently saw a multiagent turf war."

The pricing collusion results are, in some ways, more alarming for anyone deploying agents in commercial contexts. Anthropic ran a Bertrand pricing game with groups of three to eight agents, each given identical wholesale prices and individual profit-maximizing goals. When given a private back-channel, they began colluding almost immediately. By round three, they had explicitly agreed on price floors. One agent's message in round one read: "wholesale is 10 for all of us, so a price war just burns everyone's margin... Happy to coordinate who covers which niches." That's not adversarial behavior in the traditional sense. Nobody prompted the agent to form a cartel. It reasoned its way there. More troubling: when researchers removed all direct communication channels, the agents still colluded, matching prices to the penny via a public listings board. They found the coordination channel in the structure of the environment itself.

The conformity problem is subtler but just as consequential at scale. When multiple agents share similar contexts, scaffolding, and underlying models, they tend toward similar decisions. If one makes a misjudgment, the error propagates. Anthropic found that adding more agents doesn't reliably improve outcomes when tasks overlap: rather than coordinating, agents frequently carried out only their own portion and interfered with the rest. The implication is that what looks like a localized bad decision from one agent can quickly become a systemic failure across the whole swarm. A 12-hour simulation where agent swarms built an open-world game together illustrated this concretely. Only Sonnet 5 maintained both high code sharing and a high rate of merged pull requests. Earlier model generations either merged poorly or barely worked together at all. Every game the team produced was, by their own assessment, bad.

The models tested in these experiments included Claude Mythos Preview, Mythos 5, Sonnet 4.6, Sonnet 5, Opus 4.6, and Opus 4.8. The finding that cuts across all of them is the one the team states plainly in their conclusion: coordination does not arrive as a by-product of more capable or better-aligned individual models. You cannot solve the multiagent problem by making each agent smarter in isolation. The interaction layer is where the novel failure modes live.

Anthropic draws an analogy worth sitting with. Agents, they note, are subject to social pressures similar to those "evolution exerted" on humans. But they lack the lived experience of human coordination: the norms, the reputations, the signaling systems, the recourse mechanisms that limit unintended group behaviors. Humans spent thousands of years developing institutions to manage the fact that individually rational actors can produce collectively catastrophic outcomes. We have antitrust law precisely because the Bertrand game plays out in real markets too. AI agent swarms are running that same game at machine speed, without any of the institutional scaffolding.

Anthropic's call to action is framed carefully: as companies advance multiagent systems, safety testing needs to expand from individual agents to "agent collectives." That's a significant shift in how the field has to think about evaluation, red-teaming, and deployment gates. Right now, most teams ship agents after validating individual behavior. These experiments suggest that's necessary but nowhere near sufficient. The risks that matter most may only surface when agents are placed in environments with other agents, given overlapping goals, and left to interact over time. Building the evaluation infrastructure to catch that class of failure before deployment is, at this point, an open problem.

About the Author

Sean Breeden is a Full Stack Developer specializing in Artificial Intelligence, Machine Learning, Mage-OS, Shopify, Magento, Python, and PHP.