When I used Claude Code’s cloud agent. I could start work on a repo, then say “Oh yea I need to do this, submit a PR over there”. It could then find that repo (in the same organization), clone it, do the work, push a branch, submit a PR, subscribe to events on the PR and automatically follow-up on review feedback. It cannot do this cross-org.
Cursor is disappointingly limited in this regard. You can create “multi-repo environment”, but you can’t add a repo later. You can set repositoryDependencies but that doesn’t give access to submit PRs.
I created a GITHUB_TOKEN for it to fall back to in these scenarios, but it seems its own prompting forbids use of gh do this and it refuses.
A Cloud Agent can open pull requests on any repo that is a full repository in its multi-repo environment. Repos listed only under repositoryDependencies are there for the agent to read and work in, but opening PRs on them isn’t supported. Include the second repo when you create the environment: Cloud Environment Setup | Cursor Docs
You also can’t add a repository to an environment after it exists, or have a running agent pick up another repo in the org partway through a session. GitHub access stays scoped to the repos in that environment, which is why a GITHUB_TOKEN isn’t used for gh writes.
Once a PR is open, ask the agent to watch it. It can follow review comments and CI on its own: Capabilities | Cursor Docs
We’ve let the team know about pulling in any repo in the org during a session.
Thanks for confirming what can and can’t be done. Hopefully this feature can be improved, because it’s the biggest gap we’ve experienced from Claude Code’s cloud agents. About half my team refuse to switch because of the multi-repo limitations you confirmed.