Anysphere · 2026-04-24 · notable
Cursor 3.2 — Async Subagents, Multi-root Workspaces, Improved Worktrees
Cursor 3.2 ships three agentic workflow changes: /multitask runs async subagents in parallel instead of queuing; worktrees get one-click branch isolation; multi-root workspaces let a single agent session span multiple repos for cross-repository changes.
Cursor 3.2 adds /multitask for true parallel agent dispatch and multi-root workspaces for cross-repository agent sessions.
Key specs
| Version | 3.2 |
|---|---|
| Release date | 2026-04-24 |
What is it?
Cursor 3.2 is a point release for Anysphere's agentic code editor, following 3.1 (April 13) and 3.0 (April 2). The three headline features address a bottleneck that has been manual until now: running multiple independent agent tasks simultaneously, each in its own isolated branch, across multiple repositories.
How does it work?
The /multitask command spawns async subagents in parallel instead of adding requests to a sequential queue — useful when you have several independent changes and don't want to wait for each to finish before starting the next. The improved Agents Window lets you move any branch into your local workspace with one click, removing the manual promote-from-worktree step. Multi-root workspace support brings multiple folders into a single agent session, so a single model context can edit frontend, backend, and shared libraries in one pass.
Why does it matter?
Sequential agent queuing was a primary workflow bottleneck in Cursor 3.0 and 3.1. Async dispatch brings the tool closer to how experienced engineers actually work — several tasks in flight at once. Cross-repo sessions are especially valuable for teams whose changes must span independent repositories that share interfaces.
Who is it for?
Developers using Cursor for agentic coding workflows, especially teams with multi-repo setups
Try it
Update Cursor and use /multitask in the Agents Window