Feature request for product/service
Background Agent (GitHub, Slack, Linear,…)
Describe the request
Right now, once a Background Agent is created, it is permanently bound to the GitHub repo that was selected at setup. If you want to move the agent from the upstream repo to your personal fork, the only option is to delete and recreate the agent.
This creates a lot of friction:
- Cursor may try to resume runs on non-existent branches in the new repo (errors like “Failed to fetch branch/tag ref … HttpError: Not Found”).
- There’s no simple way to “point” the agent at a different remote without recreating everything.
Feature request: Please add a simple UI setting per repo to switch the Background Agent between repos (e.g. from rsyslog/rsyslog → alorbach/rsyslog). Even just being able to re-bind an agent to a different fork in the same GitHub account would solve most of these headaches.
Reason: I do not want to pollute the main project repo with too many agent-created branches. Having agents run only against my fork keeps the upstream project clean and avoids cluttering it with experimental branches.
This would save time, avoid errors, and make the workflow much smoother.
Thanks for considering!
Operating System (if it applies)
Windows 10/11
MacOS
Linux