Coudn’t make use of the cloud agents, because I have to give it access to my github, when i click to grant permissions, and once when the redirect opens, I grant access to whatever its asks me to give permission to but I’m done saving my changes, nothing else happens, I go back to my cursor agent window, and I see the same loading screen dialog box. and it never ends, until I cancel
Steps to Reproduce
Try reconnecting github on cursor, and using cloud agents
Hey, thanks for the report. This looks like a known issue with reconnecting GitHub. After reconnecting, a stuck OAuth state can remain, and the callback doesn’t return to Cursor, so the dialog spins forever.
Try this cleanup:
On GitHub, go to Settings > Applications. Under Authorized GitHub Apps, find Cursor and click Revoke. Under Installed GitHub Apps, remove Cursor too if it’s there.
Clear cookies for cursor.com, or just open an incognito or private window.
Connect GitHub via the web dashboard at https://cursor.com/dashboard, not via the in-IDE dialog, then go back to Cursor.
If it still hangs after that, let me know. There’s probably some stale state on our side that needs to be cleared manually.
I followed all the steps to the dot!
→ Went back to github, uninstalled the cursor application → Went to cursor.com/dashboard, first of it was still displaying that it ha access to my repos(odd!), → Reconnect → Cursor application install happened → Gave it the permissions it was seeking
→ Went back to cursor agent ide → Repo chat which i wanted to tranfer to cloud → switched to cloud → redirected again to github for more permissions → I gave the permission to view, edit all the repos
→ Got redirected back to cursor IDE, with the dialog spin running → A pop up came in bottom right saying “Github has granted access to the repo, now re-configuring the cloud environment”, that was it. The spinner just kept spinning forever, nothing changed. I waited for 5mins.
→ I closed the dialog and again pressed to take to cloud. same loop again of granting access and the following steps i mentioned above.
ps. I’ve updated my my ide to version 3.9.16
also I want to mention that my cursor account is on another account, with the email [email protected] , so it might help you guys check things on your end!
Thanks for the detailed step-by-step breakdown, it helps.
Here’s what I got stuck on: you mentioned you have two Cursor accounts, 00aman****@gmail.com and 20b*****@iiitdwd.ac.in. It really looks like the issue is here. The GitHub installation might be linked to one account, while you’re starting the cloud agent from an IDE that’s logged into the other account. That also explains why the dashboard on the Gmail account still showed repo access after you uninstalled on the GitHub side, the old connection was still there.
Let’s check:
In the IDE, open Cursor Settings and see which account you’re logged into right now.
oh i made sure it was the same account i was loggeed in to, Its the one I told you , [email protected], also I noticed 2 peculiar things, I followed the steps exactly as you told me, if you look at the screenshots, both are displaying different names for my github account,
the one IDE loader is showing was my previous github account name
the dashboard one is the current one
however both redirect to the same page for permissions, weird.
to answer your question
Request ID: 05243171-a978-4744-bc49-5121829c9bfc
Email: [email protected]
Thanks for the screenshots, they really helped. This is exactly where the issue is: on the GitHub dashboard it’s connected as AmanGxpta, but in the Cursor IDE dialog it’s requesting access to areeguptaji/trace, which is your old GitHub username. Looks like the GitHub account was renamed from areeguptaji to AmanGxpta, and a link to the old owner is still saved somewhere, so the cloud agent keeps looping on re-configuring.
Let’s check a couple things:
In your local trace repo, check the remote:
git remote -v
If it shows the old name areeguptaji/trace, update it to the current one:
On GitHub: Settings > Applications > Cursor > Configure. Under Repository access, make sure the trace repo is explicitly added to the list. Right now the dashboard only shows orgs, so a personal repo might not be included in what was selected.
After that, start the cloud agent again from the same account [email protected].
I noted the Request ID. I’ll also check on our side in case there’s any stale state tied to the old GitHub username that needs to be cleared manually. Let me know what you see from git remote -v.
Yes!! That worked. crazy, I didn’t think the old remote could cause the issue as the commits were pushing to remote just fine. Now I feel a bit stupid. Thanks Dean!
