July 20, 2026
Buzzword swarm, comment storm
Agent swarms and the new model economics
AI ‘swarms’ got way better fast, but the comments section is not buying the hype
TLDR: The company says its new AI team setup solved a hard coding task much better than its old one and did it far faster. Commenters immediately split between “this is the future” and “this feels like overhyped homework if the AI already saw the answers.”
The big claim here is deliciously dramatic: a new team of AI helpers did far better than the old one on a tough coding challenge, getting to 80% on a hidden test in four hours while the previous version apparently melted down before hour two. The company says the trick is simple in theory: let the smartest AI do the planning, then hand the smaller jobs to cheaper, faster AIs. They also bragged about building a brand-new system to manage the flood of changes, because their old setup topped out at about 1,000 code changes per hour, while the new one allegedly screams along at 1,000 per second.
But the real show is in the comments, where readers split into two camps: future-believers and hype police. One excited fan called it a glimpse of the future, the kind of wild experiment people would have laughed at a couple of years ago. Others were much less starry-eyed. The sharpest side-eye came from people asking the obvious question: if the AI was trained on lots of public code, is rebuilding SQLite really proof of genius, or just a fancy open-book exam? Another popular complaint was basically, “Cool demo, where’s the actual useful product?” One commenter joked that these posts keep flexing the power of the process while admitting the resulting software still kind of stinks.
And then there’s the classic tech-drama subplot: show us the goods. Some readers said the most interesting part isn’t the flashy benchmark, but the behind-the-scenes machinery—and they’re annoyed that the company teased it without releasing the code. In other words: the swarm may be cooperating, but the comment section definitely isn’t.
Key Points
- •The article compares an older and newer agent swarm on the task of building SQLite from scratch in Rust from documentation.
- •The newer swarm outperformed the older swarm in every tested model configuration under the same models and time budget.
- •In one reported run using Grok 4.5, the new swarm reached 80% of a held-out SQL test suite in four hours, while the old swarm had to be paused before two hours.
- •The swarm architecture uses planner agents to decompose goals and worker agents to execute subtasks, with different model mixes producing similar quality but very different costs.
- •To support much higher concurrent agent activity, the team says it built a new version control system, increasing peak activity from about 1,000 commits per hour on Git to about 1,000 commits per second.