Our Cursor cloud agent cannot update pr descriptions or make pr comments. Our cloud agent has all the github app permissions cursor asks for but says it does not have the right permissoins to edit pr descriptions or add pr comments… is there a way we can do that? can cursor please include those permissions in their github integration?
This is a known limitation. Cloud agent tokens are intentionally scoped with conservative GitHub permissions for security reasons — they currently don’t include write access to PR descriptions or the ability to post PR comments, even if your GitHub App installation has those permissions granted.
The gap between what you see in the GitHub App settings and what the agent token actually gets is by design — the agent operates with a more restricted set of permissions than the full app installation.
Our team is aware of this and working on making cloud agent GitHub permissions more configurable. In the meantime, PR descriptions and comments would need to be managed manually or through other automation outside of the cloud agent.
Also, I noticed you posted this same question as a reply on another thread — for visibility, it’s best to keep it in this dedicated thread so our team can track it properly.
Cloud Agents can’t update the description of a PR they didn’t open. Please make it possible.
Our workflow: PRs are often opened by Claude Code or by a person. A Cursor Cloud Agent then fixes the review findings, pushes to the PR branch and runs our @claude review loop. After the fixes the PR description is out of date: it states the old defaults, misses new env vars, and so on.
What blocks it today:
ManagePullRequest update_prrefuses with “current description is not agent-managed”.- The runtime GitHub token is read-only on pull requests, by design according to earlier answers in this thread.
- We put our own fine-grained token in Cloud Agent secrets and explicitly allowed the agent to use it. The agent still refuses, because its instructions say a refused PR update is final for the run and it must not fall back to gh or the API.
The result is that a person has to paste the description by hand, on a Cursor Ultra plan, after the agent did all the real work.
Request:
- Let
update_predit any PR in a repo where the Cursor GitHub App has Pull requests: write, at least when the user explicitly asks. A user or team setting would be fine. - Or let the agent use a user-provided token secret for PR edits when the user opts in.
Related bug: a GitHub PR subscription does not deliver edits to issue comments. claude[bot] (the Claude Code Action) posts a “working…” comment and then edits it into the finished review, so the agent never gets the result and only notices it when the user tells it.
Because of this and similar annoyances, I am cancelling my Cursor Ultra subscription this month. Cursor used to be the best tool out there; now it is one of the worst.