Introducing /multitask in the new Cursor 3 interface. Cursor can now run async subagents to parallelize your requests instead of adding them to the queue. For already queued messages, you can ask Cursor to multitask on them instead of waiting for the current run to finish. https://t.co/gtvOlup2hX
Cursor 3.2 Parallelizes Agent Workflows With Async Subagents and Multi-Repo Support
· Updated
Cursor 3.2 introduces the multitask command to run asynchronous subagents in parallel rather than waiting for sequential queue execution. This update shifts the developer experience from serial task management to simultaneous orchestration across multiple repositories within a single agent session.
3.2 featuring a new /multitask command for its agentic coding (AI that autonomously writes, tests, and iterates on code) interface. The update allows the editor to spawn asynchronous subagents that execute multiple requests in parallel instead of using a sequential queue.This shift extends the orchestration of multiple autonomous agents for complex engineering. By enabling parallel execution, the system builds on parallel subagent workflows introduced in earlier versions to handle large-scale refactors and multi-file features without stalling the developer's flow.
You can now also target multi-root workspaces, allowing a single agent session to modify code across several repositories simultaneously. This capability follows the integration of frontier models optimized for multi-file tasks. These features are available in the Agents window of the 3.2 desktop application.
Still wondering? A few quick answers below.
Every HeadsUpAI update is written based on its original source and reviewed before it's published. Read our editorial standards →
