# Cloud Agents claim they can't access gh CLI (403) **URL:** \ **Category:** Bug Reports\ **Tags:** github, cloud-agents\ **Created:** [July 10, 2026, 12:48pm UTC](https://forum.cursor.com/t/cloud-agents-claim-they-cant-access-gh-cli-403/165401 "2026-07-10T12:48:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![durden](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/durden/32/111800_2.png) [@durden](https://forum.cursor.com/u/durden)\ **Post date:** [July 10, 2026, 12:48pm UTC](https://forum.cursor.com/t/cloud-agents-claim-they-cant-access-gh-cli-403/165401/1 "2026-07-10T12:48:18Z")
### Where does the bug appear (feature/product)? Cloud Agent (GitHub, Slack, Web, Linear) ### Describe the Bug My Cursor Cloud Agents claim they are unable to utilize the GitHub CLI (and don’t utilize the GitHub MCP Tooling). I am working with @mattpocock’s skills, which I have configured for GitHub for ticketing. Local agents have no problem utilizing gh/MCP seamlessly, but I have noticed Cloud Agents are claiming 403. GitHub is authorized and connected to all of my repos, installed on this one, and cursorbots/cursotagents all work seamlessly in all other scenarios to my knowledge. ### Steps to Reproduce Get into a chunk of “best practices” agentic work for codebase architecture review or /wayfinder map work. The agent will follow the SKILLS.md instruction for GitHub and attempt to use the gh CLI, and hit a 403. ### Expected Behavior Cloud Agents should be able to utilize GitHub CLI / API seamlessly as they do as Local Agents. ### Screenshots / Screen Recordings ### Operating System MacOS ### Version Information Version: 3.10.20 VS Code Extension API: 1.125.0 Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0 Date: 2026-07-07T07:03:33.071Z Layout: Agent Window Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.256 OS: Darwin arm64 25.2.0 ### For AI issues: which model did you use? Cursor Grok 4.5 High Fast ### For AI issues: add Request ID with privacy disabled bc-ddf3f34d-709b-4ad5-b5a7-5099c29602ec ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**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:** [July 10, 2026, 1:44pm UTC](https://forum.cursor.com/t/cloud-agents-claim-they-cant-access-gh-cli-403/165401/5 "2026-07-10T13:44:09Z")
Hi @durden This is a known limitation of Cloud Agents where they don’t have the `issues` scope. We want to fix this long-term, but we aren’t there yet. Some known workarounds are mentioned in this thread. > [@Cursor GH app doesn't seem to have the correct permissions](https://forum.cursor.com/t/cursor-gh-app-doesnt-seem-to-have-the-correct-permissions/159885/7): > > Unfortunately, this is still the case. The installation token the cloud agent uses in its sandbox doesn’t include the issues or pull\_requests: write scopes yet, even though the GitHub App shows those permissions. Our team is aware and tracking it, but there’s no fix shipped or ETA to share at this point. The Personal Access Token workaround that was suggested in your [earlier thread](https://forum.cursor.com/t/pull-request-create-failed-graphql-resource-not-accessible-by-integration-createpullrequest/153425/13) is still the recommended approach: Create a [Personal Access Token](https://github.com/settings/personal-access-tokens) on GitHub with issues and pull\_requests scope… ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [August 16, 2026, 3:08pm UTC](https://forum.cursor.com/t/cloud-agents-claim-they-cant-access-gh-cli-403/165401/8 "2026-08-16T15:08:45Z")
Closed on August 16, 2026, 3:08pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.