Cursor 3 ships a thing called "Build in Parallel." The pitch is straightforward: instead of executing a plan step by step, Composer identifies which steps are independent and runs them as concurrent subagents.
It's a real shift. And it changes what a useful production template has to look like — because parallel agents punish vague conventions in a way single-threaded ones never did.
What changed
Cursor's May 2026 release notes describe it like this: Composer breaks a plan into a dependency graph, identifies branches with no shared writes, and dispatches them to async subagents. You watch a tree of tasks finish in roughly the time the longest single branch would have taken — not the sum.
It works. We tested it on a typical kit task ("add a new entity end-to-end: schema, API route, list page, detail page, types, prompts.md row"). Linear plan: 6 minutes 40 seconds. Parallel plan: 2 minutes 10 seconds. Three subagents writing three files at once, then a fourth subagent that wires the index export once they're done.
