Cloud Agents cannot access all authorized private GitHub repositories

Support Bug Reports
,
1

Describe the Bug

Hello Cursor Support,

I am experiencing a reproducible GitHub repository-access issue affecting Cursor Cloud Agents.

My GitHub account is De4ko6543. The Cursor GitHub App installation settings show All repositories selected.

However, both an existing Cloud Agent and a newly created Cloud Agent can access only one of my two private repositories:

  • De4ko6543/levy-barrier-option-toolkit — PASS
  • De4ko6543/quant-research-library — FAIL

Diagnostic results:

  • gh repo view and git ls-remote succeed for the Barrier Toolkit.
  • Both commands fail for the Research Library with “Repository not found.”
  • GitHub REST API returns HTTP 200 for the Barrier Toolkit and HTTP 404 for the Research Library.
  • The Cloud Agent’s installation token reports repository_selection=selected, with only one accessible repository.
  • The issue persists in a freshly created Cloud Agent after reviewing and refreshing the GitHub connection.

Request:

Could you investigate why Cursor Cloud Agents receive repository-restricted installation tokens when the GitHub App installation settings show access to all repositories?

Please advise how to enable access to both private repositories without disrupting existing agent conversations, branches or pull requests.

Thank you.

Steps to Reproduce

  1. Configure the Cursor GitHub App installation for the GitHub account De4ko6543 with access to All repositories.

  2. Confirm that both private repositories exist:

    • De4ko6543/levy-barrier-option-toolkit
    • De4ko6543/quant-research-library

  3. Start a Cursor Cloud Agent in levy-barrier-option-toolkit.

  4. Run gh repo view and git ls-remote against both repositories.

  5. Observe that access to levy-barrier-option-toolkit succeeds, while access to quant-research-library fails with “Repository not found” or HTTP 404.

  6. Inspect the agent’s GitHub installation token permissions. The token reports repository_selection=selected and exposes only one repository, despite the GitHub App settings showing All repositories.

  7. Refresh the Cursor GitHub connection and repeat the test in a newly created Cloud Agent.

  8. Observe that the same failure persists.

Expected result: Both private repositories should be accessible.

Actual result: Only the Barrier Toolkit repository is accessible to the Cloud Agent.

Expected Behavior

Cursor Cloud Agents should be able to access both private GitHub repositories because the Cursor GitHub App installation is configured for All repositories.

Operating System

Windows 10/11

Version Information

Version: 3.18.9 (user setup)
VS Code Extension API: 1.128.0
Commit: 2ba48ff3f7514cc4643c52ca9f7b3173d9b66130
Date: 2026-08-27T01:42:22.092Z
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.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @De4ko6543, thanks for the report and for checking the token yourself.

What you’re seeing is how Cloud Agents work today. Your GitHub App installation does have access to all repositories, but each Cloud Agent gets its own short-lived token that only covers the repositories in the environment it was started in. Your agents were started in a single-repo environment for the barrier toolkit, so their token covers only that repo, and the research library returns “Repository not found”.

To give an agent access to both repos:

  1. Open the Cloud Agents dashboard at cursor.com/agents and go to Environments.
  2. Create a new environment and select both repositories (the barrier toolkit and the research library).
  3. Start a new Cloud Agent in that environment.

That agent gets both repos cloned side by side, with a token that covers both, so it can read, push and open pull requests in either one.

None of this touches your existing agents. Their conversations, branches and pull requests stay exactly as they are. A running agent can’t add a second repository partway through a session, so for work that needs both repos, start a new agent in the multi-repo environment. It can check out your existing branch by name and continue from there.

Docs: Cloud Environment Setup | Cursor Docs (see “Multi-repo environments”)

Let me know if the new environment doesn’t pick up the second repo.