[GitHub integration]
Screenshot
Issue: GitHub MCP tools return 404 for repos that the connection status checker confirms are accessible.
Setup:
GitHub account connected: JKrivoX
Claude GitHub App installed on JKrivoX (personal), set to "All repositories," with read/write on code, PRs, issues, actions, workflows
Settings → Connectors → GitHub Integration → "Check repository status" for JKrivoX/joe-delta-dashboard returns: "Claude Code cloud sessions can work in JKrivoX/joe-delta-dashboard" (green check)
Problem: In an active Cowork/cloud session with the GitHub MCP server connected, every repo-level call fails with a genuine 404 from GitHub's API — not the "access not enabled for this session" message, an actual 404 Not Found from api.github.com. This happens for all three of my private repos (JKrivoX/joe-delta-dashboard, JKrivoX/convergence-app, JKrivoX/Antigravity_System), which I've confirmed exist under exactly those names and are owned by JKrivoX.
Repro:
Connect GitHub Integration, confirm "All repositories" + JKrivoX installed
In a Cowork session, call any github MCP tool against a real owned repo, e.g. list_branches(owner: "JKrivoX", repo: "joe-delta-dashboard")
Result: 404 Not Found from https://api.github.com/repos/JKrivoX/joe-delta-dashboard/branches
get_me() via the same MCP connection correctly identifies as JKrivoX — so the connection is authenticated, just can't see any repo content
What I'd expect: Since the status checker explicitly confirms cloud sessions can work in this repo, the GitHub MCP tools in an actual session should be able to read it. Instead every repo-scoped call 404s, suggesting the session's GitHub tool isn't actually using the same authorization the status checker is checking against.
This has been consistent across multiple sessions started with the repo already selected, and persists after reinstalling/reconfirming the GitHub App settings on the GitHub side.
What were you trying to do?
Issue: GitHub MCP tools return 404 for repos that the connection status checker confirms are accessible.
Setup:
GitHub account connected: JKrivoX
Claude GitHub App installed on JKrivoX (personal), set to "All repositories," with read/write on code, PRs, issues, actions, workflows
Settings → Connectors → GitHub Integration → "Check repository status" for JKrivoX/joe-delta-dashboard returns: "Claude Code cloud sessions can work in JKrivoX/joe-delta-dashboard" (green check)
Problem: In an active Cowork/cloud session with the GitHub MCP server connected, every repo-level call fails with a genuine 404 from GitHub's API — not the "access not enabled for this session" message, an actual 404 Not Found from api.github.com. This happens for all three of my private repos (JKrivoX/joe-delta-dashboard, JKrivoX/convergence-app, JKrivoX/Antigravity_System), which I've confirmed exist under exactly those names and are owned by JKrivoX.
Repro:
Connect GitHub Integration, confirm "All repositories" + JKrivoX installed
In a Cowork session, call any github MCP tool against a real owned repo, e.g. list_branches(owner: "JKrivoX", repo: "joe-delta-dashboard")
Result: 404 Not Found from https://api.github.com/repos/JKrivoX/joe-delta-dashboard/branches
get_me() via the same MCP connection correctly identifies as JKrivoX — so the connection is authenticated, just can't see any repo content
What I'd expect: Since the status checker explicitly confirms cloud sessions can work in this repo, the GitHub MCP tools in an actual session should be able to read it. Instead every repo-scoped call 404s, suggesting the session's GitHub tool isn't actually using the same authorization the status checker is checking against.
This has been consistent across multiple sessions started with the repo already selected, and persists after reinstalling/reconfirming the GitHub App settings on the GitHub side.
What happened instead?
Issue: GitHub MCP tools return 404 for repos that the connection status checker confirms are accessible.
Setup:
GitHub account connected: JKrivoX
Claude GitHub App installed on JKrivoX (personal), set to "All repositories," with read/write on code, PRs, issues, actions, workflows
Settings → Connectors → GitHub Integration → "Check repository status" for JKrivoX/joe-delta-dashboard returns: "Claude Code cloud sessions can work in JKrivoX/joe-delta-dashboard" (green check)
Problem: In an active Cowork/cloud session with the GitHub MCP server connected, every repo-level call fails with a genuine 404 from GitHub's API — not the "access not enabled for this session" message, an actual 404 Not Found from api.github.com. This happens for all three of my private repos (JKrivoX/joe-delta-dashboard, JKrivoX/convergence-app, JKrivoX/Antigravity_System), which I've confirmed exist under exactly those names and are owned by JKrivoX.
Repro:
Connect GitHub Integration, confirm "All repositories" + JKrivoX installed
In a Cowork session, call any github MCP tool against a real owned repo, e.g. list_branches(owner: "JKrivoX", repo: "joe-delta-dashboard")
Result: 404 Not Found from https://api.github.com/repos/JKrivoX/joe-delta-dashboard/branches
get_me() via the same MCP connection correctly identifies as JKrivoX — so the connection is authenticated, just can't see any repo content
What I'd expect: Since the status checker explicitly confirms cloud sessions can work in this repo, the GitHub MCP tools in an actual session should be able to read it. Instead every repo-scoped call 404s, suggesting the session's GitHub tool isn't actually using the same authorization the status checker is checking against.
This has been consistent across multiple sessions started with the repo already selected, and persists after reinstalling/reconfirming the GitHub App settings on the GitHub side.
Diagnostics
Filed from: GitHub settings for Claude Code on claude.ai
Report code: GH-YCJ3FP
Page: claude.ai/customize/connectors/integration-github
Client: desktop