Failed to Create a GitHub Pull Request from Cursor Web

Support Help
26

Hello @deanrie , no update on this yet above? :slight_smile:

27

Hey @Mark_Allison @marciska, thanks for your Request ID.

It’s the same issue: the installation token that the cloud agent gets doesn’t include all write permissions, even if the GitHub App is set up correctly. This affects both PR creation and GitHub Issues. @marciska, your case has the same root cause. The team is aware, but there’s no ETA yet.

A workaround that works for other users: create a Personal Access Token at Sign in to GitHub ¡ GitHub with the scopes you need pull requests, issues, etc., then add it to your cloud environment as an environment variable:

GH_TOKEN=github_pat_...

After that, the gh CLI will use this token for auth instead of the installation token.

Let me know if this helps.

1 Like
28

@deanrie I tried it with your workaround, but it didn’t work unfortunately:

https://cursor.com/agents/bc-c1d5ff57-8edb-4dd8-bc47-a3c1df04b553

Even after giving it a token of literally every read+write access it could do, it fails to do in creating a simple issue entry. Set it on “all repositories“ as well, and refreshed the session when creating new GH PAT Tokens.
Thank you though for addressing :person_bowing:

1 Like
29

Cursor cloud agents would be promising, but not being able to make a simple gh pr comment complicates usability.