Background Agent (GitHub, Slack, Linear,…)
Hello team,
My workspace spans three repositories, which Agent Mode handles fine. However, the background agent keeps asking me to pick a single Git repo, making it difficult to work across multiple repos (e.g. frontend and backend) simultaneously.
Would love to know if we have such a feature being addressed!
I second this, it would be very useful if background agents could work on workspaces.
In addition to this, spawning a background agent from a multi-repo workspace from within Cursor doesn’t let me change the selected repository, only the branch. So even if I do have a background task that’s contained to one repository, I have to open a separate Cursor window with only that repository to start the background agent.
1 on this please! One of the most powerful parts of using Cursor is workspaces and doing multi-repo updates all at once. Please add to remote agents 
We have a lot of IAC modules and template repositories that are private and often need their changes propagated to consumer repos. The changes are often more than a version number bump but minor changes like “you need to add this import now” or other work to implement a new feature. Very dry stuff an LLM is capable of but currently requires manual work by setting up a local shared workspace so the LLM can consume the info needed to make the change. The manual cost of setting that up, triggering the LLM, creating the PR, etc. is much higher than having the remote agents do it.
I would propose that the remote agents are able to reference at least one private repository in addition to the target repo. This could be indicated in the request to the agent like so:
```
Make changes from [my-org/my-repo] in [my-org/my-app] to update to the new version. See url-to-release-notes for the changelog.
```
We have dozens of repositories that this sort of process could help considerably with.
Absolutely want / need this, I often need to do multi repo analysis and dont want to have to always do this on my desktop. Especially where you have a b/e and f/e separation of repos and need to keep apis / interfaces aligned.
I can only guess us multi-repo folks are in the minority as this issue and related ones about multi-agent mode with multi-root workspaces don’t have many asking for the feature. “Just use a monorepo” is not a practical answer. Cursor works great on my desktop with the backend and frontend repos in a workspace – it’d be amazing to have this ability for cloud agents.
+1 …this would be REALLY helpful!