I asked Cursor Web to perform some work and create a pull request, but it failed to create a PR on GitHub.
The error shown in the task log is as follows:
$ cd /workspace && gh pr create --title "feat(headsup): add Stud Hi-Lo (Stud 8 or Better) game type" --body "$(cat <<'EOF'
...
EOF
)" --base main 2>&1
pull request create failed: GraphQL: Resource not accessible by integration (createPullRequest)
Creating a branch and pushing commits worked without any issues.
I also checked the GitHub Integration configuration, and it appears that the Cursor app has permissions for all repositories. The permissions shown are:
Read access to actions, commit statuses, deployments, metadata, packages, and pages
Read and write access to checks, code, discussions, issues, pull requests, and workflows
Is there any additional configuration required to allow PR creation?
Also, are there others who are experiencing the same issue, or conversely, people for whom PR creation works successfully from Cursor Web?
It looks like this is a known issue the team is already tracking. To help investigate your specific case, could you share:
Request ID: Open Cloud Agent at cursor.com/agents, click the menu (top right), and choose “Copy Request ID”
Repo type: Is this a personal repo or an org repo?
GitHub App install level: Is Cursor installed at the org level or on your personal account?
Also, please try reinstalling the GitHub app from GitHub Apps - Cursor · GitHub. Sometimes the app install can get corrupted or permissions can get out of sync.
Thanks for the extra info and for testing with a reinstall.
This is a known issue, and the team is working on a fix. To help investigate your case, could you also share the browser console logs?
Open the browser console (F12) on cursor.com/agents
Start a new task and try to create a PR
When the PR creation error shows up, copy any errors from the console
This will help the engineers understand why the GitHub App still hits the “Resource not accessible by integration” error even after a reinstall. I’ll pass both of your Request IDs to the team for further investigation.
We looked into it and found a likely issue: GitHub requires the branch to exist on the remote before you can create a PR. In the logs, we see warnings like “Auto-commit: not on target branch, not pushing”, which suggests the branch may have been created locally but not pushed.
Could you please check whether the branch with your changes exists on GitHub? Go to your repo https://github.com/oppai/yomi and look at the branch list. Do you see the branch the agent created?
This will help the team figure out what’s going on, whether the agent isn’t pushing the branch or if it’s something else.
The logs is `bc-82be1722-c4ef-458a-913c-4b4fe7be1bfd` as request id.
Cursor log is below. It means “cursor pushed commit to new remote branch `cursor/agent-documentation-update-e88d`. But it was failed to create new PR. Please create below link.“