Fetching from the wire…
Public story · 2026-07-31 · high
Four Opus 4.6 agents coordinating through the system beat a solo agent on the newer Opus 4.8 model, 62.1% to 57.2%, per the July 30 paper.
Why now: The paper posted to arXiv on July 30.
AgentRadio lets coding agents message each other mid-task, and four coordinated agents resolved 62.1% of codebase questions versus 32.3% for one agent working alone, per a July 30 arXiv paper. That's a nearly 30-point jump in benchmark accuracy. It comes from a coordination layer teams could add to agents they already run, not a newer model.
The system adds three primitives: threads, messages, and waiting for a mention. The wait runs as a background task, so an agent keeps working in the foreground instead of stopping to check in.
The benchmark is SWE-Atlas QnA, a set of long-horizon questions about production codebases. The four-agent group split the work using a five-phase division-of-labor protocol, and the code is released under Coral-Protocol.
That 62.1% score also beats a single Claude Code agent running the newer Opus 4.8 model, which answers 57.2% of the same questions.
The accuracy gap between solo and coordinated agents widens as tasks get harder, per the paper. The authors read that as mid-course correction, agents catching and fixing each other's wrong turns, not four agents splitting a workload.
A related paper, SkillRise, takes a different route to the same goal. It has a single agent alternate between solving tasks and rewriting its own skill document. No teammates required, one policy improving itself instead of four agents talking to each other.
Each link below shares sources, entities, or timing with this story.
The errors trace back to how the benchmark pairs pull requests with GitHub issues, not just to model quality.
Cross-vendor AI review still shows up in just 1.6% of agent-authored pull requests, but reviewers grade outside code more harshly than their own.
The attack hides malicious intent across separate skills that only turn dangerous when they pass work to each other, and a fix cuts success to 22.5%.
arXiv 2607.28430 adds asynchronous message-passing to coding-agent harnesses with three primitives: threads, messages, and waiting for mentions, where the wait runs as a background task so an agent stays passively aware of teammates without blocking foreground work. Single Cla...
Sandbox memory in the test suite peaks at 28 GB a session, and latency across components swings up to 32x within the same app.
Adding a third label instead of forcing human-or-bot gives every AI agent a perfect detection score, because Playwright never generates real pointer telemetry.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.