Claude Code, Cursor, and Windsurf All Ship Parallel Subagent Execution. Same Week.

Three things happened almost simultaneously. Cursor 3.3 shipped "Build in Parallel," which identifies independent parts of your plan and runs them concurrently using async subagents. Windsurf integrated Devin Local with cloud handoff and multi-model support. And Claude Code's agent teams with worktrees have been quietly maturing into the same pattern.

When three competing products independently converge on the same capability, it's not a feature. It's table stakes.

The performance difference between sequential and parallel agent work on multi-file changes is too large to ignore. I've been using Claude Code's worktree-based parallelism for a few weeks now, and the difference isn't 2x. It's more like 4-5x for tasks that decompose cleanly into independent file groups. A refactor that used to take an hour of agent time takes fifteen minutes.

The emerging differentiator isn't whether you can run parallel agents. It's how much control you get over what those subagents use. Cursor 3.3 lets you configure the subagent model from settings. Want your subagents running Opus while the main agent uses Sonnet? Done. Windsurf's Adaptive mode auto-selects models per task to stretch quota. Claude Code gives you worktree isolation, which is more of an infrastructure play than a model selection play.

Here's where I see this going: the coding IDE that wins isn't the one with the best single-agent performance. It's the one that makes multi-agent orchestration feel natural. Right now, all three feel bolted on. Cursor's approach of identifying parallel-ready plan steps automatically feels the most natural, but it's limited to plan-mode workflows. The IDE that figures out how to make parallel execution the default, without requiring explicit orchestration from the developer, takes the category.

If you're still using one agent session at a time, try parallel execution this week. The learning curve is real, but so is the throughput gain.