The cursor should be able to work on multiple code repositories. For example, if a change we make in our NextJS UI repository requires a change in the API, it should make that change.
Hey, thanks for the question. I get what you’re trying to do, this is a common full-stack workflow.
Right now:
- Parallel Agents / Worktrees only work within a single Git repo (isolated copies of different branches).
- Multi-root workspaces (multiple repos opened at once) don’t support Multi-Agents yet.
Workaround: You can open a multi-root workspace (File > Add Folder to Workspace) to view both repos in one window. The agent can still see code from both projects via @-mentions and context, but it will work sequentially, not in parallel.
Multi-root workspaces (multiple repos opened at once) don’t support Multi-Agents yet.
Any ETA on this, or with worktrees with multi root repos?
Hey, there’s no specific ETA for this yet. Multi-root workspaces plus parallel agents and worktrees is a request the team is aware of, but I can’t promise a timeline right now.
For now, the workaround is still the same: use a multi-root workspace and run the agent sequentially. Not in parallel, but at least you can stay in one window and access both projects.
If this is critical for your workflow, please upvote that thread. It helps with prioritization.
Will do! Ty for the reply!
I can see we can work on multiple repos on cursor.com/agents, but not in the Agents Window on the MacOS app. Any idea when this would be shipped?
The web/app difference is probably the confusing part for users.
For full-stack work, multi-repo support is not just convenience. The change often has to cross the API, frontend, shared types, and deployment config together. If one surface supports that better than another, it would help to make the boundary very explicit.
Hey, good request. The difference is real, and I get why it’s confusing.
As of today:
- Cloud agents at cursor.com/agents and Cloud Agents in the IDE can work in multi-repo setups. They can see multiple repos at once and make coordinated changes across frontend, backend, shared types, with a PR. More details: Cloud Agents | Cursor Docs
- The local Agents Window in the desktop app parallel agents and worktrees is still limited to a single Git repo. You can open a multi-root workspace to view both projects in one window, but the local agent will go through them one by one, not in parallel.
So multi-repo support is currently on the cloud agent side, not in local parallel mode. I don’t have a specific ETA for bringing this to the local Agents Window, and I don’t want to promise timelines.
@Jason_Luo1, I hear your feedback that we should make the web vs app boundary explicit, and I’ll pass it along. If there’s an update on parity, I’ll reply in the thread.