# Cloud Agent gh/git token missing issues:write despite GitHub App being granted Issues: Read & write **URL:** \ **Category:** Bug Reports\ **Tags:** github, automations, cloud-agents\ **Created:** [June 16, 2026, 10:09am UTC](https://forum.cursor.com/t/cloud-agent-gh-git-token-missing-issues-write-despite-github-app-being-granted-issues-read-write/163389 "2026-06-16T10:09:19Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [June 16, 2026, 11:23am UTC](https://forum.cursor.com/t/cloud-agent-gh-git-token-missing-issues-write-despite-github-app-being-granted-issues-read-write/163389/5 "2026-06-16T11:23:50Z")
Hey @MishaTheMisha Thanks for raising this! This is a known limitation we are working on resolving. > [@Cursor GitHub App Does Not Have Issue View or Create Permissions](https://forum.cursor.com/t/cursor-github-app-does-not-have-issue-view-or-create-permissions/161308/5): > > Hey @Brian_Heise! Thanks for the feedback. The cloud agent’s GitHub installation token does not include the issues scope. The GitHub App requests broad permissions at the app level (which users see in installation settings), but the token actually minted for the sandbox is scoped more narrowly. We have an open issue here to figure out what to do (either add issues scope to background agent runner GitHub token or update docs to remove Issues from supported permissions. Have added your feedb… In the meantime, some users have found a workaround by adding a `GH_TOKEN` with the `repo` scope in their Cloud Agent settings. > [@Cloud Agent cannot read GitHub Issues — “GraphQL: Resource not accessible by integration (repository.issues)”](https://forum.cursor.com/t/cloud-agent-cannot-read-github-issues-graphql-resource-not-accessible-by-integration-repository-issues/156790/4): > > Hey, this is a known issue. The token the cloud agent gets in the sandbox environment does not include the issues scope, so gh issue list and gh issue view fail with “Resource not accessible by integration”. The team is aware. Related reports: [Cloud Agent not able to load GitHub issue](https://forum.cursor.com/t/cloud-agent-not-able-to-load-github-issue/155241)[Pull request create failed: GraphQL: Resource not accessible by integration (createPullRequest)](https://forum.cursor.com/t/pull-request-create-failed-graphql-resource-not-accessible-by-integration-createpullrequest/153425) Two workarounds: Paste the issue content (title, description, comments) directly into the agent prompt instead … --- _[View the full topic](https://forum.cursor.com/t/cloud-agent-gh-git-token-missing-issues-write-despite-github-app-being-granted-issues-read-write/163389)._