How Do You Run Several Cursor Agents at Once?
Use the Agents Window, Cursor's agent-first interface. Press Cmd+Shift+P and run Open Agents Window, then start each task as its own agent, running in a worktree or in the cloud. Every task gets separate files, so agents don't overwrite each other. Run Open IDE to go back to the editor at any time.
/multitask These tasks are independent. Run them in parallel, each in isolation: 1. [task and its done condition] 2. [task and its done condition] 3. [task and its done condition] For each, report the result, what you ran to verify it, and any file that more than one task needed to change.
- Worktree
- Cloud Agent
- Project
Try it now
- 1Press Cmd+Shift+P (Ctrl+Shift+P) and run **Open Agents Window**.
- 2Start two small, unrelated tasks, and choose a worktree for each so they stay isolated.
- 3Review each result in the diffs view and commit it. It worked if each change is separate and your main checkout wasn't disturbed. Pin any chat you'll come back to.
Use it when
When you have several independent tasks, or a task long enough that you'd otherwise sit and wait. From a plan, click Build in Parallel to run independent steps at once while dependent steps stay in order.
Skip it when
Tasks that touch the same files, since you'd only move the conflict to merge time. And be realistic about review. Parallel agents multiply diffs too, and if your tests take 10 minutes, ten agents is nearly two hours of waiting, as Cursor's course points out. Speed up the tests first.
Why it works
Agents collide when they edit the same checkout. Worktrees give each task its own Git checkout with its own dependencies, and Cloud Agents give each one a whole machine. The Agents Window brings these together with one sidebar, a diffs view for review and commit, and handoff between local and cloud. Cursor's docs recommend it for managing many agents, and the classic editor for VS Code extensions and viewing many files at once. Both stay supported.
Example
Say you have three chores: add tests to payments, update a dependency, and fix a typo across docs. You run them as three worktree agents and pin the dependency one, since it might need follow-up. Meanwhile, a longer migration runs in the cloud, and you check its demo video from your phone. Each returns its own diff, so you can merge the safe ones first.
Going further
For work spanning weeks, try a Project in the Agents Window sidebar. A coordinator agent plans, delegates to other agents, keeps files of shared context, and can subscribe to signals such as a Slack channel or a schedule. It requires Premium or higher, and isn't available with Privacy Mode (Legacy). Worktrees have a catch. Cursor keeps at most 25 per machine across all workspaces by default, and older ones get cleaned up, including those from git worktree add. Set cursor.worktreeMaxCount if you run many.
Common mistakes
- Pointing two agents at overlapping files and discovering the conflict after both finish.
- Starting more agents than you can review. An unread diff isn't finished work.
- Forgetting
.cursor/worktrees.json, so each worktree starts with no dependencies or.env. - Looking for worktree buttons in the editor. They're in the Agents Window, while the editor uses
/worktree.
Sources
- Agents Window, Cursor Docs
- What is multi-agent coding?, Cursor Help
- Worktrees, Cursor Docs
- Projects, Cursor Docs
- Reviewing and testing code, Cursor Learn
Checked 6 November 2026. Products change often, so confirm details with the vendor.