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

Support Bug Reports
, ,
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.