Cloud Agent cannot access private GitHub repository despite correct GitHub App permissions

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cursor Cloud Agent cannot access my private GitHub repository even though the GitHub integration is connected to the correct account and the Cursor GitHub App explicitly has access to the repository.

Cursor Dashboard shows GitHub as connected to the account “555ml”. In GitHub, the Cursor App is installed and both private repositories are selected under Repository access. However, starting a Cloud Agent still produces an error saying Cursor cannot access the repository.

Affected repository: 555ml/IEEE-TAPandAWPL

Steps to Reproduce

  1. Connect GitHub in Cursor Dashboard > Integrations.
  2. Confirm that the integration shows “Connected as 555ml”.
  3. Open GitHub Settings > Applications > Installed GitHub Apps > Cursor > Configure.
  4. Select “Only select repositories”.
  5. Explicitly add:
    • 555ml/IEEE-TAPandAWPL
    • 555ml/IEEE-Auto-Report
  6. Save the GitHub App configuration.
  7. Restart Cursor.
  8. Select the ieee-tapandawpl repository in Cursor.
  9. Select Cloud mode.
  10. Ask the agent to inspect or explain the repository.
  11. Cursor reports that it cannot access 555ml/IEEE-TAPandAWPL.

Expected Behavior

Cursor Cloud Agent should be able to clone, inspect, and work with the selected private repository because the GitHub integration is connected and the Cursor GitHub App explicitly has access to it.

Screenshots / Screen Recordings

01.png
01.png2046×1610 117 KB
02.png
02.png2849×1658 267 KB
03.png
03.png2136×1911 245 KB

Operating System

Windows 10/11

Version Information

Version: 3.15.6 (user setup)
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Sonnet 5 High

For AI issues: add Request ID with privacy disabled

1748022f-3022-499f-8c81-1ae8c2b397d3

Additional Information

Troubleshooting already attempted:

  • Confirmed that the repository exists and is private.
  • Confirmed that the connected GitHub account is 555ml.
  • Confirmed that Cursor Dashboard reports GitHub as connected.
  • Confirmed that the Cursor GitHub App is installed.
  • Confirmed that 555ml/IEEE-TAPandAWPL is explicitly selected under Repository access.
  • Saved the repository access configuration again.
  • Reconnected GitHub from Cursor Dashboard.
  • Restarted the Cursor client.
  • Retried the Cloud Agent request.

The same error persists.

Error message:

“Cursor cannot access repository 555ml/IEEE-TAPandAWPL. The repository may have been deleted, renamed, made private, or removed from the Cursor GitHub App installation. Check the repository and update the Cursor GitHub App installation, then try again.”

Because both the GitHub connection and repository permissions appear correct, this may be a stale or incorrect GitHub App installation mapping on Cursor’s backend.

Could you please inspect the Request ID and refresh or clear the GitHub installation mapping associated with my Cursor account?

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report. Having the logs and the Request ID makes this a lot easier to debug.

One important note: Cursor doesn’t store an access cache. Every time the agent starts, we ask GitHub directly in real time. Your GitHub App reinstall created a completely new installation, but GitHub still responds with 404 when we request access to 555ml/IEEE-TAPandAWPL and 555ml/IEEE-Auto-Report using the installation token. So this isn’t a stale mapping on our backend. The request is fresh and it’s still being rejected on GitHub’s side.

Let’s do one diagnostic step to narrow this down:

  1. GitHub → Settings → Applications → Cursor → Configure
  2. Temporarily change Repository access from Only select repositories to All repositories, then save
  3. Try running the Cloud Agent again

Then there are two possibilities:

  • The agent works: the issue was with the grant for the selected repos. Sometimes the UI shows a repo as selected, but the actual access didn’t get applied. You can switch back to Only select repositories and re-add both repos.
  • You still get 404 even with All repositories: that means GitHub is blocking API access to private repos at the account level. This can happen if an account is under restrictions or flags. The owner can see everything normally, but third-party integrations get 404. In that case, you’ll need to contact GitHub Support.

Also, please double-check the repos weren’t renamed and that the owner is exactly 555ml with the same spelling.

Let me know what happens with the All repositories test. That will tell us what to try next.