Major GitHub Connection Issues

[ntyson (Nick Tyson)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

A private repo owned by my GitHub org does not appear in the Cloud repo picker (Start from scratch → Cloud), even though the Cursor GitHub App is installed at the org level with that repo granted. A different repo owned directly by my personal account appears normally in the same picker, so the picker itself is working.

Relevant history: the repo was originally created on a second personal GitHub account I also own (ACCOUNT-A), and the Cursor GitHub App was installed on ACCOUNT-A at that time. I later created an org, transferred the repo into it, and configured the Cursor app at the org level. My day-to-day account (ACCOUNT-B, the one my Cursor account is linked to) was a collaborator and is now an org owner. My guess is a stale installation record still pointing at the pre-transfer path.

Steps to Reproduce

Create a private repo on personal GitHub ACCOUNT-A, install the Cursor GitHub App on ACCOUNT-A, grant it the repo
Create a GitHub org and transfer the repo into it
Install/configure the Cursor GitHub App on the org and grant it the transferred repo (as an org owner — confirmed granted, no pending request)
Sign into Cursor desktop with an account linked to ACCOUNT-B, which is an org owner and has admin on the repo
Disconnect and reconnect the GitHub integration to force a fresh token
Open Start from scratch → Cloud
Result: the transferred repo is not listed. A repo owned directly by ACCOUNT-B is listed.

Expected Behavior

The org-owned repo appears in the Cloud repo picker, since the app installation has been granted access to it and the signed-in user is an org owner with admin on the repo.

There is an extra screenshot showing the new Codebase system is UNABLE to connect to GitHub.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

3.18.25 (Universal)

Additional Information

Even though screenshot shows “Connect” next to GitHub, when I click it, you see the other screenshot that shows its already connected. I have removed it, and reinstalled it and it still does the same thing.

Does this stop you from using Cursor

Yes - Cursor is unusable

[mohitjain (Mohit)]

Hey @ntyson
The org repo isn’t the problem - your Cursor account has a second GitHub account linked that’s no longer authorized, and that one dead link is failing the whole GitHub connection (all three screens). This isn’t intended behavior and it’s an issue we’re tracking.

To clear it:

1. On cursor.com/dashboard (logged in), open your browser console (right-click → Inspect → Console) and run: fetch('/api/dashboard/disconnect-github', {method: 'POST'})
2. Refresh the page - GitHub should show as disconnected.
3. On github.com → Settings → Applications, revoke Cursor on the older account so it doesn’t re-link.
4. In an incognito window, signed in to GitHub as your day-to-day account, click Connect next to GitHub.

Your org repo should then appear in Start from scratch → Cloud. If it doesn’t, reply here and we’ll clear the stale link from our side.