Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
In a Cloud Agent run, the injected GitHub App installation token can read the repo and push commits (contents:write), but every Issues API call fails with 403 Resource not accessible by integration. Our org’s Cursor GitHub App is granted Issues: Read and write, so the agent token appears to be minted with a narrower permission set than the installation actually holds. This blocks automations that file GitHub issues (e.g. a code-audit agent that opens triaged issues for findings).
Environment
- Cursor Cloud Agent (background automation, cron-triggered)
- Repo: GitHub organization, private
- GitHub App: Cursor — confirmed granted Issues: Read and write at the org installation
- Token type observed on VM: GitHub App installation token (x-access-token:… git remote)
Questions for Cursor
- Is issues intentionally excluded from the Cloud Agent installation token? If so, can it be opt-in (e.g. per-repo or per-automation setting)?
- Is there a setting that makes the agent token inherit the full granted permission set of the installed GitHub App?
Steps to Reproduce
- Run a Cloud Agent on a repo whose Cursor GitHub App has Issues: write granted.
- From the agent, run
gh issue create …(orgh api -X POST /repos/{owner}/{repo}/issues).
Expected Behavior
Issue is created, since the installation has Issues: Read and write.
Actual
HTTP/2.0 403 Forbidden
X-Accepted-Github-Permissions: issues=write
{"message":"Resource not accessible by integration","status":"403"}
Evidence / diagnosis (run from inside the agent VM)
Operation Result Required perm
`GET /repos/{owner}/{repo}` 200 metadata=read ✅
`git push` (new branch) success contents=write ✅
`POST /repos/{owner}/{repo}/issues` 403 issues=write ❌
`POST /…/issues/{n}/comments` 403 issues=write; pull_requests=write ❌
The token is clearly not blanket read-only (it has contents:write); it is specifically missing issues. Since the org installation grants Issues: write, this points to the per-run agent token being down-scoped to a subset of the app’s permissions, rather than an org-side configuration gap.
Operating System
MacOS
Version Information
No updates available
Version: 3.7.36
VS Code Extension API: 1.105.1
Commit: 776d1f9d76df50a4e0aeca61819a88e7c1b861e0
Date: 2026-06-13T00:31:56.287Z (3 days ago)
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0
For AI issues: which model did you use?
Opus 4.8
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor