Cursor 3 removes the one-agent-at-a-time limit and adds Design Mode
Cursor 3 lifted the restriction to a single running agent, and shipped Design Mode — annotate UI elements directly in the browser to give the agent precise visual targets for frontend work. It arrives in a market where every major coding tool has shifted pricing model within the last year.
Concurrent agents is a bigger change than it sounds, because it alters what a developer is doing. One agent at a time means supervising a task. Several at once means dispatching work and reviewing results, which is a different job with different skills — and a different failure mode, since parallel agents editing a shared codebase can conflict in ways a single agent never does.
Design Mode addresses the most persistent friction in agentic frontend work: describing which element you mean. Pointing at a rendered component removes an entire class of ambiguity that no amount of prompt engineering reliably fixes, and it is a good example of a fix that is interface design rather than model capability.
The hybrid pattern most experienced developers report — one tool for daily editing, another for hard problems — only survives while running two subscriptions stays affordable. That is a pricing condition, not a product one, and pricing in this category has moved every few months.
Cursor Changelog — Cursor 3.0 — new interface, parallel agents, Design Mode → · byteiota — Cursor 3 Agents Window: parallel execution and worktrees → · New Claw Times — Cursor 3 redesigns the IDE around agents with parallel execution and Design Mode →