Cursor is not responding at all to github @

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When I @cursor in github it typically responds and then updates its comment after it has done the work, but right now literally nothing happens (no emoji reaction, no comment).

Another problem (possibly what’s causing this) is that whenever I try to connect my Github integration (through the cursor admin) it says it failed because the tab is wrong even though it’s the one I am using. It then shows that I have github integrated in the cursor admin, but maybe that’s not actually correct?

Steps to Reproduce

Go to github on an issue and type in @cursor to get an agent running.

Expected Behavior

See above.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

n/a - it’s all on github

Does this stop you from using Cursor

No - Cursor works, but with this issue

Here is the other screenshot. Couldn’t attach both in one issue report form.

Hey, I’ve noticed you’ve run into this in a couple of threads now. The “Your session expired” error on the GitHub connection page is probably the root cause. If the integration isn’t properly connected, @cursor mentions on GitHub won’t trigger anything.

To fix the connection, try this:

  1. First, clean up old installations: GitHub > Settings > Applications > Installed GitHub Apps. Remove any Cursor entries. Also check Authorized GitHub Apps and revoke Cursor there.

  2. Open an incognito/private browser window, log into cursor.com, and start the GitHub connection from there. This helps rule out ad blockers, extensions, or cookie issues breaking the OAuth redirect.

  3. Important: complete the entire GitHub authorization flow in the same tab. Don’t open links in new windows.

  4. Once connected, verify on the dashboard that your repos are listed under the GitHub integration.

  5. Also confirm that on-demand usage billing is still enabled. That was the fix for your previous issue in this thread.

If incognito doesn’t help, check that third-party cookies are allowed and try without a VPN if you’re using one.

Let me know how it goes.

@deanrie Thank you for the response. I have followed all of those steps previously without any luck, but I just did them all again just to be sure and it still gives me the same error. I opened my console to see if there were any errors and there is some sort of 403 in there. I am not opening any new windows except the ones that automatically open when you are going through the process.

@deanrie Here is a video

Any other thoughts here? This is a huge bottleneck on my workflow.

@deanrie Ok this is even more weird now. Even though the auth says it is failing if I go back to the cursor dashboard it says it is connected. @cursor in my github issues still is not doing anything. I submit it and wait and no comment, no emoji- nothing. So this is the interesting part here…I made a change locally on my pc through the IDE and pushed up a branch. When I created a PR to merge Bugbot triggered and actually ran. So how is that possible that bugbot worked but not @cursor?

Didn’t change anything today and all of a sudden it works again. :man_shrugging:

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.