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

Support Bug Reports
, ,
1

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.

Operating System

MacOS

Version Information

Not relevant since this is regarding cloud agents.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Unfortunately, this is still the case. The installation token the cloud agent uses in its sandbox doesn’t include the issues or pull_requests: write scopes yet, even though the GitHub App shows those permissions. Our team is aware and tracking it, but there’s no fix shipped or ETA to share at this point.

The Personal Access Token workaround that was suggested in your earlier thread is still the recommended approach:

  1. Create a Personal Access Token on GitHub with issues and pull_requests scopes for the repos you need

  2. Add GH_TOKEN=ghp_your_token to your cloud environment settings

After that, the gh CLI in the agent sandbox will authenticate with your token instead of the limited built-in one.