Cursor GitHub App Does Not Have Issue View or Create Permissions

[Colin]

Hey @Brian_Heise!

Thanks for the feedback.

The cloud agent’s GitHub installation token does not include the issues scope. The GitHub App requests broad permissions at the app level (which users see in installation settings), but the token actually minted for the sandbox is scoped more narrowly.

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

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 ena…

Cursor GH app doesn't seem to have the correct permissions

Where does the bug appear (feature/product)? Background Agent (GitHub, Slack, Web, Linear) Describe the Bug Hi! This is still an issue, is this something being actively worked on or is still the suggested route using a gh token? Thanks. Steps to Reproduce Ask a cloud agent to fetch gh issues with a connected Cursor app with correct permissions. Expected Behavior Since the gh app is scoped to be able to read and write issues I would assume the cloud agent would be able to do that as well. O…

We have an open issue here to figure out what to do (either add issues scope to background agent runner GitHub token or update docs to remove Issues from supported permissions. Have added your feedback to that ticket!