Cloud Agent cannot read GitHub Issues — “GraphQL: Resource not accessible by integration (repository.issues)”

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cloud agents on web/mobile cannot access GitHub Issues despite the Cursor GitHub App having correct permissions. The agent reports gh issue list fails with GraphQL: Resource not accessible by integration (repository.issues). The GitHub App installation clearly shows “Read and write access to checks, code, discussions, issues, pull requests, and workflows” and the repository has Issues enabled with 8 existing issues.
This appears to be a token scope issue — the integration token used inside the cloud agent VM may not be requesting the issues scope even though the GitHub App installation has it granted.

Steps to Reproduce

Have a GitHub repository with Issues enabled and existing issues (private repo)
2. Verify the Cursor GitHub App installation has read/write access to issues (confirmed under /settings/installations)
3. Open cursor dot com agents on mobile
4. Start a new cloud agent session connected to the repository
5. Ask the agent: “do you see issues on connected github?”
6. Agent runs gh issue list and returns:
GraphQL: Resource not accessible by integration (repository.issues)

Expected Behavior

The agent should be able to list and read GitHub Issues from the connected repositoty

Screenshots / Screen Recordings

IMG_6342.png
IMG_6342.png1290×2796 269 KB

Operating System

MacOS

Version Information

cursor.com/agents

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

Hey, this is a known issue. The token the cloud agent gets in the sandbox environment does not include the issues scope, so gh issue list and gh issue view fail with “Resource not accessible by integration”. The team is aware.

Related reports:

Two workarounds:

  1. Paste the issue content (title, description, comments) directly into the agent prompt instead of asking it to fetch it by number.

  2. Create a Personal Access Token at Sign in to GitHub · GitHub with the needed scopes and add it as an environment variable GH_TOKEN=ghp_... in your cloud environment settings. After that, the gh CLI will use that token instead of the built-in one.

Let me know if either of these helps.

6

hi @deanrie , thank you! I tried #2 and it works. thanks.