Cursor 3.2 (April 2026): /multitask Async Subagents, Better Worktrees, Multi-Root Workspaces

Cursor’s April 2026 3.2 release is focused on making the Agents Window feel more like a parallel workbench than a single-file line. The headline is /multitask, which spins up async subagents to take on multiple queued items at once — plus background worktrees and a new multi-root workspace concept for cross-repo edits.

It’s also a strong terminal week: Cursor’s CLI gets Debug Mode (/debug), a “side-question” escape hatch (/btw), an interactive configuration panel (/config), and customizable status bars via /statusline.

What Shipped in Cursor 3.2

All of the above is described in Cursor’s official changelog for 3.2. Cursor changelog

/multitask: Async Subagents in the Agents Window

Cursor 3.2 introduces /multitask in the Agents Window as a first-class way to parallelize agent work. Instead of queueing each request behind the current run, Cursor can run async subagents and fan out a larger task into smaller chunks.

This is useful when your “agent backlog” includes multiple small changes (docs + refactor + tests) that don’t need to block each other.

Source: Cursor changelog

Better Worktrees for Background Branch Work

Cursor is leaning into worktrees as the unit of background execution: you can run isolated tasks across different branches, and then bring the branch you want into your local foreground when you’re ready to test.

Source: Cursor changelog

Multi-Root Workspaces: Cross-Repo Agent Sessions

The Agents Window now supports a reusable “workspace” made of multiple folders. That means a single agent session can work across frontend + backend + shared libraries without you constantly retargeting the agent.

Source: Cursor changelog

Interactive Canvases (Durable Side-Panel Artifacts)

Cursor can now respond by creating interactive canvases — dashboards and custom interfaces built with components like tables, boxes, diagrams, and charts. In the Agents Window, these canvases are durable artifacts that live in the side panel alongside the terminal, browser, and source control.

Source: Cursor changelog

Cursor CLI: Debug Mode, /btw, /config, /statusline

Cursor’s CLI received a cluster of quality-of-life upgrades:

• Debug Mode (/debug): a workflow for root-cause analysis where Cursor generates hypotheses, adds logging, and uses runtime signals before making targeted fixes.
• /btw: ask quick side questions without derailing the main task.
• /config: open an interactive settings panel inside the CLI.
• /statusline: customizable status bars so you can surface the session signals you care about.

Source: Cursor changelog

Practical Takeaway

If you use Cursor as an agentic IDE, 3.2 is primarily a throughput update:

1. Use /multitask when you have a backlog of small independent changes.
2. Use worktrees to run risky or noisy experiments (dependency upgrades, refactors) without locking up your main branch.
3. Use multi-root workspaces when your codebase is split across folders or repos.

Official Links

• Cursor changelog (3.2, canvases, CLI updates): Cursor changelog