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