Top AI Product

Cursor pointed a swarm of coding agents at a blank repo and told it to rebuild SQLite in Rust. Four hours later, Grok 4.5 had 80% of the test suite passing. The old swarm architecture couldn’t survive past hour two.

A planner that never writes code

Agent Swarms is orchestration inside Cursor, not a new model. Planner agents run on frontier models and split the goal; worker agents run on cheap fast models and execute. Planners never implement, workers never plan, so neither one’s context fills with the wrong altitude of detail. The old swarm peaked around 1,000 commits per hour on Git. This one hits roughly 1,000 per second on a version control system Cursor wrote from scratch. Merge conflicts fell from 70,000+ to under 1,000. A Fable 5 hybrid shipped SQLite in 9,908 lines where the old system sprawled to 64,305.

Model choice is now a budget decision

Same task, $1,339 to $10,565 depending on configuration. You mix models per role — Opus 4.8 or Fable 5 planning, Composer 2.5 doing the typing — and worker spend collapses from $9,373 to $411. Coordination, not raw capability, is the bill.

You Might Also Like

• From Claude Flow to Ruflo 22k Stars 5900 Commits and the Multi Agent Swarm Taking Over Claude Code
• Design Agent by Lokuma Topped Product Hunt With a Simple Pitch ai Agents Need Designers too
• Cursor for ios Turns Your Phone Into a Coding Agent Dispatch Console
• Agent Builder by Thesys When ai Agents Stop Talking and Start Showing
• Cloudrouter Gives Your ai Coding Agent its own Cloud Machine and Thats a big Deal