Cursor 3 introduced a separate agent-first workspace that can run agents locally, in worktrees, over SSH, and in the cloud while keeping the editor available. The release gives teams a path to multi-agent orchestration without giving up the traditional IDE surface.
/worktree and /best-of-n commands, with separate checkouts per model and a parent agent that compares outputs.You can read the full launch post, skim the worktrees and Best-of-N breakdown, and the product already exposes a dead-simple entrypoint because Eric Zakariasson says the whole thing opens from Cmd+Shift+P → Agents Window. The most interesting product choice is that Cursor did not throw away the old editor surface: AILeaksAndNews’ summary and the official post both frame the new workspace as a companion window that still lets you drop back into the IDE.
Cursor 3’s centerpiece is Agents Window, a new interface that Cursor says it built from scratch around agent workflows rather than around the editor itself. In the launch post, the company describes it as a unified workspace for building software with agents, with a multi-repo layout and a higher-level view of ongoing work.
The official forum announcement adds the concrete operational model:
That is a bigger product move than the marketing line suggests. Ryo Lu’s reaction picked up the same design goal, that the interface starts simple and exposes more tooling only when needed.
The release thread makes the scope explicit: agents can run locally, in a worktree, over remote SSH, and in the cloud. The blog post fills in the missing detail, which is handoff in both directions.
From cloud to local, a session can move down to the desktop when a developer wants to edit or test directly. From local to cloud, the same session can keep running after the user goes offline, which Cursor pitches for long tasks that would otherwise die when a laptop closes.
Cursor also says cloud agents now generate demos and screenshots for verification, reusing the same experience from cursor.com/agents inside the desktop app. Kevin Kern’s launch-day note focused on that seamless local and cloud switch, which is probably the part engineers will remember first.
The cleanest technical change lives in the official worktrees post. Cursor replaced older implicit worktree behavior with two explicit commands:
/worktree starts an isolated Git checkout for the rest of a chat./apply-worktree brings the result back to the main branch./best-of-n runs the same task across multiple models at once, each in its own worktree..cursor/worktrees.json can define project-specific setup, including dependency installs, env-file copying, and migrations.That same thread includes a useful follow-up from Cursor engineer David Gomes: /worktree and /best-of-n now support multi-repo setups, which had been a practical blocker for teams splitting frontend and backend repos.
Shipper’s Every review lands roughly where the product evidence does. He argues the rebuild makes sense because agent orchestration is replacing plain AI pair programming, but he also says the current release still feels early and not yet strong enough to force a switch.
Cursor’s other notable choice is restraint. The launch post says the company is still carrying over the IDE features people actually use inside an agent-first shell, instead of pretending the editor no longer matters.
The list is concrete:
That is also why the rollout path is unusually lightweight for a product this different. Upgrade Cursor, open Cmd+Shift+P, launch Agents Window, and the old IDE is still there when you want it. Cursor is betting that agent orchestration gets adopted faster if it ships as an adjacent workspace instead of demanding that developers abandon the editor muscle memory they already have.