Background Agent (GitHub, Slack, Web, Linear)
When mentioning cursor to start a new agent, it doesn’t start up
Windows 10/11
No version
Yes - Cursor is unusable
Hey, thanks for the report. From the screenshot, it looks like the Cursor bot detected the mention, but it couldn’t start the agent itself.
A couple things to check:
Did this work for you before, or is this your first time trying to start an agent from GitHub?
If none of the above helps, message me and share the Request ID from the agent page so we can dig deeper.
Hello,
Still not working. Here the Request ID: bc-06c6b90b-7e6a-4a36-bb80-5430aeb5dfff
It worked before and On Demand Usage is activated (with enough usage left to reach the limit).
Thanks.
I am having an issue with github agents not firing also. When I use @cursor it does not even respond so maybe my issue is slightly different, but something is not working right.
If it helps at all I tried to disconnect and reconnect my github in case there was an expired auth or something and now I can’t even reconnect it. I keep getting this message no matter what I try to do.
Hi @gillesheinesch !
It looks like in this case, another user had already called @cursor on that same PR , which created a background agent tied to their account. When you then mentioned @cursor , the system tried to add your request as a follow-up to that existing agent rather than starting a new one – and since it’s owned by the other user, the access check denied it silently.
Are you collaborating on this PR with another Cursor user? Just want to make sure what I gleaned from the logs matches reality. 
Hi Colin,
Yes that’s right.
I’d suggest adding better error handling to clearly communicate to the user why the operation is failing (e.g. specific message + possible next steps).
Quick question: would it be feasible for multiple people to work on the same PR while each using their own @cursor background agent?
Thanks
Hello @Colin , any news on this one?
