[BUG]GitHub App reinstall required after claude.ai reconnect silently fails; reinstall itself redirects to inaccessible org-settings page for non-Team/Enterprise accounts

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Preflight Checklist

• [x] I have searched existing issues and this specific combination (broken reconnect flow + broken org-settings callback on a personal/Pro account + cross-session connector desync) hasn't been reported together before, though several individual symptoms overlap with existing issues (linked below).
• [x] This is a single bug report covering one coherent failure chain (I've kept it to one report rather than splitting, since each step below was discovered while diagnosing the same original symptom).
• [x] I am using the latest version of Claude Code (web/cloud sessions via claude.ai/code, also reproduced via the iOS app).

What's Wrong?

Category: Bug Report — GitHub integration / cloud session provisioning

Title: GitHub App reinstall required after claude.ai's own "disconnect/reconnect" silently fails to fix cloud-session cloning; the reinstall path itself is also broken for non-Team/Enterprise accounts (redirects to an inaccessible "organization settings" page)

Summary:
A Claude Code cloud session (started from the iOS app, session type "claude-code · Default") repeatedly failed at the "Cloning repository" step with:

Authentication failed while accessing the git_repository source. Check that your GitHub token or credentials have read access to this repository. If using a private repo, verify the integration is authorized for it.

This happened against a private, personal-account repository with the Claude GitHub App already installed with "All repositories" access and full read/write permissions. The failure was intermittent (succeeded 1 time out of ~4 attempts on the unmodified installation). Using claude.ai's own Settings → Connectors "disconnect/reconnect" toggle for GitHub did not fix it. The only thing that did fix it was manually uninstalling the GitHub App entirely on GitHub's side and reinstalling it fresh via github.com/apps/claude — but that reinstall path itself hit a separate bug (see step 5 below) and the account is still left in an inconsistent connector state afterward (see step 6).

Environment

• Claude.ai account tier: individual Pro (not Team/Enterprise)
• Entry points tested: Claude Code cloud sessions via the iOS app / iPadOS app, and claude.ai web (desktop browser)
• Target repository: private, personal-account-owned, ~472MB .git history / ~3.8GB working tree, no Git LFS, largest tracked file ~50MB
• GitHub App: "Claude" (github.com/apps/claude, developed by anthropics)

Timeline (dates approximate, all 2026)

1. Aug 8 — first occurrence: New Cloud Code session from the iOS app fails immediately at session init with the "Authentication failed while accessing the git_repository source" error. GitHub App "Claude" was already installed (per its own settings page, installed "last week" at that point) with "All repositories" access and correct permissions (read access to commit statuses/metadata; read+write to actions, checks, code, discussions, issues, pull requests, hooks, workflows).
2. Aug 8 — reconnect attempt: Disconnected and reconnected GitHub in claude.ai Settings → Connectors. Retried the session. Same error persisted.
3. Aug 8 — intermittency confirmed: Retried again on the same, unmodified installation. This time "Cloning repository" succeeded (checkmark), and the session proceeded to "Run setup script". So the same GitHub App installation, with no changes in between, failed 3 times and succeeded once — indicating the failure is not a static permissions/scope problem.
4. Aug 9 — forced test, App fully removed: To test whether the GitHub App installation itself was the issue, uninstalled the "Claude" GitHub App completely from github.com/settings/installations (confirmed via screenshot: "No installed GitHub Apps"). Went back to claude.ai and used the GitHub "reconnect" flow again — it completed successfully without ever redirecting to GitHub to reinstall the App. claude.ai showed GitHub as "connected" even though, at that exact moment, zero GitHub Apps were installed on the account. This strongly suggests claude.ai's reconnect flow only performs an OAuth-level re-authorization and does not reliably re-trigger (or verify) the GitHub App installation step.
5. Aug 9 — manual reinstall via GitHub's own flow: Went directly to github.com/apps/claude and started the install flow manually (bypassing claude.ai's broken reconnect UI). Partway through — before landing back on a normal Claude page — GitHub redirected to a claude.ai URL that returned:

> You don't have access to organization settings
> Organization settings are available on Claude Team and Enterprise plans.

This account is an individual Pro subscriber, not Team/Enterprise. It looks like the GitHub App's configured "Setup URL" (the callback GitHub calls after installation completes) points to a claude.ai page that assumes an organization/Team-Enterprise context, and breaks for individual accounts. Despite this broken callback, checking github.com/settings/installations immediately afterward showed the "Claude" App was successfully installed on the GitHub side ("Installed 2 minutes ago", All repositories, correct permissions) — so the GitHub-side install succeeded even though the claude.ai-side callback/landing page did not.

1. Aug 9 — inconsistent connector state across sessions: After the above, claude.ai's Connectors panel (opened in one browser/session) showed "GitHub Integration" as connected (checkmark). The same account's Connectors panel opened in a different session/device ("desktop") showed GitHub Integration as not connected, with an active "Connect" button still present. Same account, same point in time, two different displayed states.
2. Aug 9 — resolution (partial): Despite the broken callback in step 5 and the inconsistent state in step 6, starting a fresh Cloud Code session from the iOS app afterward succeeded — "Cloning repository" completed and the session became usable. The original symptom is resolved for now via the manual GitHub-side reinstall, but steps 4–6 above are still-open bugs in their own right, and the original intermittency (step 3) was never explained — it's unclear whether it will recur.

Root cause hypothesis (not confirmed by Anthropic — this is inference from the above plus public issue history)

The generic "Authentication failed while accessing the git_repository source" message appears to conflate at least three distinct GitHub-auth surfaces: (a) the OAuth-only Connectors toggle in claude.ai settings, (b) the actual GitHub App installation/repo-scope, and (c) any CLI-side /web-setup token sync. claude.ai's reconnect flow only reliably exercises (a), which is why disconnecting/reconnecting there did not fix a cloning failure rooted in (b). Separately, the GitHub App's post-install Setup URL callback appears hard-coded to an org-settings-scoped claude.ai page, which is unreachable for individual/Pro accounts — meaning any individual/Pro user who needs to (re)install this GitHub App via GitHub's own install flow will hit this same dead-end page, even though the underlying GitHub-side installation still completes. The cross-session connector-status inconsistency (step 6) suggests the "is GitHub connected" state shown in claude.ai's UI is cached per-session/per-device rather than being read fresh from a single source of truth, which likely also explains part of the original intermittency in step 3 (different backend workers/sessions holding different, possibly stale, views of the connection/token state).

Related existing issues (checked individually, all confirmed real)

• #64130 — GitHub integration connects via OAuth only — private repos inaccessible in remote agents (matches step 4 above almost exactly)
• #56988 — Mobile remote control fails with "GitHub repository access check failed" for private repositories (open at time of writing; matches the mobile-specific entry point used here)
• #72933 — Cloud sessions lost connected-account GitHub access overnight — repo reads now 403 demanding GitHub App org install, contradicting docs (open at time of writing)
• #57017 — Claude GitHub App authentication fails on specific personal repositories despite valid installation
• #68517 — Claude can't access a private personal GitHub repo despite Claude GitHub App being granted full access (backend index/sync issue)
• #22277 — Claude Code Web/Mobile: "Repository or branches not found" — persistent 404 on the internal git_proxy endpoint, wrapped in a misleading UI message
• #48769 — Remote agent GitHub connector: "re-authorize GitHub in settings" error has no resolution path in settings UI
• #49318 — Remote triggers with git_repository source lose GitHub authentication and require manual re-authorization

None of the above, individually, covers the specific organization-settings redirect on reinstall for a non-Team/Enterprise account (step 5) or the cross-session connector-status inconsistency (step 6) — those two look like they may not have been reported yet, which is the main new information this report is trying to add.

What would help

1. Please check what the GitHub App's configured Setup URL actually is, and whether it unconditionally routes through an organization-settings-gated claude.ai page — if so, that should branch based on account tier, or at minimum degrade gracefully instead of a dead-end "no access" page, for individual/Pro accounts installing/reinstalling the app.
2. Please check why claude.ai's Settings → Connectors "disconnect/reconnect" for GitHub does not detect or re-trigger a missing GitHub App installation — ideally it should recognize when the App isn't installed and route the user to github.com/apps/claude/installations/new rather than completing as "connected" via OAuth alone.
3. Please check why the same account's GitHub connector status can show differently ("connected" vs "not connected, Connect button live") across different sessions/devices at the same point in time — this looks like a caching/sync issue rather than two genuinely different states.
4. If useful, I'm happy to share session IDs/timestamps for the original intermittent failures (3 failures, 1 success, same installation, no config changes in between) privately if that helps trace backend logs — didn't capture exact session IDs at the time, but can approximate timestamps.

What Should Happen?

Claude Code cloud sessions should reliably clone a private repository on the
first attempt whenever the installed GitHub App already has correct "All
repositories" access — not succeed only intermittently (1 in ~4 attempts)
with no configuration change in between.

If the GitHub App installation is missing, broken, or mis-linked to the
account, claude.ai's Settings > Connectors "reconnect" flow should detect
this and route the user through GitHub's actual App-installation screen —
not silently complete as "connected" via OAuth alone while zero GitHub Apps
are actually installed.

Installing or reinstalling the "Claude" GitHub App from GitHub's own side
(github.com/apps/claude) should complete cleanly for individual Pro-tier
accounts, not redirect to a claude.ai "organization settings" page that
Pro-tier accounts cannot access.

The GitHub connector's "connected" status shown in claude.ai should be
consistent across sessions/devices for the same account at the same point
in time, not show "connected" in one session and "not connected" in another.

Error Messages/Logs

Steps to Reproduce

1. Have the "Claude" GitHub App installed on a personal (non-Team/Enterprise)

GitHub account, with "All repositories" access, on a private repo.

1. Start a new Claude Code cloud session from the iOS/iPadOS app, bound to

that private repo.

1. Observe intermittent "Authentication failed while accessing the

git_repository source" at the "Cloning repository" step (not 100%
reproducible — roughly 1 success in 4 attempts on an unmodified
installation).

1. In claude.ai Settings > Connectors, disconnect and reconnect GitHub.

Observe this does not fix the failure.

1. To force a fix, uninstall the GitHub App entirely from

github.com/settings/installations, then manually reinstall it via
github.com/apps/claude. During/after reinstall, observe a redirect to a
claude.ai page showing "You don't have access to organization settings —
Organization settings are available on Claude Team and Enterprise plans"
(on a Pro-tier account), even though the GitHub-side install itself
completes successfully.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.226

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_