[BUG] GitHub repository sync broken in Claude Projects - files not accessible despite "Connected" status

Found 1 possible duplicate issue:

1. https://github.com/anthropics/claude-code/issues/1884

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

It's not exactly the same problem, plus the other ticket is less accurate.
I dont have an infinite loader as described in the other ticket.
My loading seems "complete" but does not work at all.

++

I have the same issue. I am connected to GitHub (both on web and desktop) and I can access the repositories, even the private ones.

I select the files.

But syncing is not working, and I can't send any messages unless I remove the connection to the repo in the chat field

+1

+1

+1

+1

+1

+1

+1

+1

It's fixed for me! Remove the existing GitHub repo and re-attach it again. Other users have reported that it's fixed also.

It is still not fixed for me. I've removed the connector/added it back again tried conversations etc still not working.

It works now !

I will wait a bit before closing it.

Hi, this GitHub is focused on Claude Code but this seems to be an issue with Claude.ai chat. Going to close and pass along the feedback to the chat team. Thanks!

I have the same issue. I am connected to GitHub (both on web and desktop) and I can access the repositories, even the private ones. I select the files. But syncing is not working, and I can't send any messages unless I remove the connection to the repo in the chat field

+1

i am able to sync the github repo with my project, but claude won't see it on the project info, has anyone the same problem?

It is still down, the sync has never been THAT broken. THe project isnt aware of the content of the projet (it used to work quite well but no longer does)

2 weeks of failure is too much for its price.

+1

+1

+1

+1

+1

+1

+1

+1

+1

It is still not working...

It's been 3 days for me. So slow and most of the time not working, even I left it sync for hours.

+1

+1

+1

• please fix this!!

+1

Anyone got any official reply from Antrhopic? This is so frustrating!

It’s now working on my end as of November 14, 2025, 11:50 AM (UTC+8).

Still not working for me.

I love claude.ai, but honestly, it's very buggy.

It used to work perfectly.. :(

Today...it's working for me again. So odd.

Before, it was working for me, but now it’s not. It seems like someone is messing with their codebase haha.

Not working for me either. File views are stale. It has been this way on and off for months actually. Works for days, then an update, then fails to fetch new data. Even disconnecting/reconnecting the service does nothing to improve it.

A few weeks back syncing got broken, then it was fixed, but now it does not work again. Very frustrating.

As other users described the re-occurrence of this issue makes using claude.ai a gamble. On some days the github connection works perfectly, on others you are stuck with infinite sync attempts. This became really frustrating and makes using claude as part of any work flow very unreliable and high risk. The lack of communication about this bug and what is done to address the issue doesn't help, either.

(Edit: updating for clarity, removing fluff)

The issue in my case seems to be "Github connector" enabled in claude web causing the oauth flow to never complete fully.

After disabling the connector in Claude.ai conversation settings, the next attempt completed as expected.

Note: 100% doesn't work to 100% work scenario is what I experienced. Also, on GitHub side, I had revoked and uninstalled GitHub app, and any oauth permissions granted to any Claude client variants several times during troubleshooting. the GitHub Connector doesn't seem to be affected by that either. And only shows up in the conversation settings across platforms.

Steps for anyone hitting this: (could be other issues too tbc)

1. Claude.ai → Settings → Connectors
2. Disable the GitHub connector
3. Go to claude.ai/code
4. Click "Install GitHub App"
5. Done

Also, for some reason this issue shows up in the support request I had raised. I would like to not add to confusion, so I'll be cleaning up and verifying with repro etc. I do want to point out that the GitHub Connector and installing the GitHub app for Claude code web are two different integrations.

Are there workflows that require the GitHub Connector specifically? Given Claude code is available now via Claude.ai/code is it the expected way for integration?

I will dig in to understand better, and share if something potentially useful surfaces.

I'm curious to know about the mentioned workflows in general.

Root Cause Analysis (Conjecture) & Workarounds

Note: This issue is filed in claude-code, but the root cause involves interaction between Claude Code's GitHub App and the separate GitHub Connector in Claude.ai web. Flagging for cross-team visibility.

---

The Problem

There are three separate GitHub integration systems in Anthropic's products:

1. GitHub Connector — Claude.ai web/Projects — not visible on GitHub
2. GitHub App — Claude Code (web/CLI) — visible as OAuth + App install
3. GitHub MCP Server — Claude Desktop/Code — visible if configured

When both the Connector and GitHub App are enabled, they conflict. OAuth succeeds, tokens are created, but the repo list returns empty.

---

Evidence: OAuth Succeeds, Integration Fails

GitHub security logs confirm successful OAuth:

oauth_access.create - token_id: 2834160058 - 02:20:51
oauth_authorization.create - integration: Claude - 02:20:51  
oauth_access.create - token_id: 2834162316 - 02:21:42
integration_installation.create - integration: Claude - 02:20:51

Multiple tokens created within 51 seconds = repeated attempts, all succeeding on GitHub's side.

Browser localStorage showed:

{ "value": [], "tabId": "...", "timestamp": 1763281407921 }

OAuth works. Tokens exist. Repo list returns empty. The failure is on Anthropic's backend when the Connector is also enabled.

---

GitHub App Permissions (Already Granted)

The Claude GitHub App receives:

• Read access to actions, checks, and metadata
• Read and write access to code, discussions, issues, pull requests, and workflows
• Repository access: All repositories

These permissions are sufficient for any GitHub integration across Claude products. The tokens already exist on Anthropic's servers.

---

What Fixed My Issue

Disable the GitHub Connector, then install the GitHub App:

Claude.ai → Settings → Connectors → GitHub → Disable
Then: claude.ai/code → Install GitHub App → Works

After 500+ failed attempts across multiple devices, browsers, and networks (including cellular), disabling the Connector fixed it on the first try.

---

Workarounds by Use Case

Claude Code users (web or CLI):
Disable the GitHub Connector. Use only the GitHub App. Full agentic access (clone, edit, commit, push, PRs).

Dev-comfortable, Claude Desktop users + Claude Code CLI users:
Consider the [GitHub MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/github). More control, works locally, requires configuration.

Claude.ai chat/Projects only (no Claude Code):
Use the Connector only. Don't install the GitHub App, or expect conflicts.

Multiple products:
Pick one integration, disable others. But this doesn't work across all interfaces:

Interface x Integration Support Matrix

| | GitHub Connector | GitHub App | GitHub MCP Server |
|-----------------------------|:----------------:|:----------:|:-----------------:|
| Claude.ai web (chat) | ✅ | ❌ | ❌ |
| Claude.ai Projects | ✅ | ❌ | ❌ |
| Claude Code (web) | ❌ | ✅ | ❌ |
| Claude Code (CLI) | ❌ | ✅ | ✅ |
| Claude Desktop | ❌ | ❌ | ✅ |
| Claude mobile (iOS/Android) | ✅ | ❌ | ❌ |

There is no single GitHub integration that works everywhere. If you use multiple Claude interfaces, you currently cannot have unified GitHub access.

Also, if the issue is intermittent then consider whether the flips align with switching interfaces, it could be that one succeeds and then causes the other one to fail. Maybe. Again, this is just conjecture, based on partial data. I do not have access to anthropic data.
---

Why This Is Happening (Speculation)

This appears to be an organizational alignment issue rather than a technical limitation:

• The GitHub App already has full OAuth permissions
• The Connector doesn't leverage these existing credentials
• MCP is open but limited to Desktop/Code CLI
• Three teams, three systems, no unified auth

The fix is straightforward: The Connector should leverage the GitHub App's existing OAuth tokens. One authorization → works everywhere. This requires internal coordination, not protocol changes.

---

## Root Cause Analysis (Conjecture) & Workarounds > Note: This issue is filed in claude-code, but the root cause involves interaction between Claude Code's GitHub App and the separate GitHub Connector in Claude.ai web. Flagging for cross-team visibility. ### The Problem There are three separate GitHub integration systems in Anthropic's products: 1. GitHub Connector — Claude.ai web/Projects — _not visible on GitHub_ 2. GitHub App — Claude Code (web/CLI) — _visible as OAuth + App install_ 3. GitHub MCP Server — Claude Desktop/Code — _visible if configured_ When both the Connector and GitHub App are enabled, they conflict. OAuth succeeds, tokens are created, but the repo list returns empty. ### Evidence: OAuth Succeeds, Integration Fails GitHub security logs confirm successful OAuth: `` oauth_access.create - token_id: 2834160058 - 02:20:51 oauth_authorization.create - integration: Claude - 02:20:51 oauth_access.create - token_id: 2834162316 - 02:21:42 integration_installation.create - integration: Claude - 02:20:51 ` Multiple tokens created within 51 seconds = repeated attempts, all succeeding on GitHub's side. Browser localStorage showed: { "value": [], "tabId": "...", "timestamp": 1763281407921 } **OAuth works. Tokens exist. Repo list returns empty.** The failure is on Anthropic's backend when the Connector is also enabled. ### GitHub App Permissions (Already Granted) The Claude GitHub App receives: * Read access to actions, checks, and metadata * Read and write access to code, discussions, issues, pull requests, and workflows * Repository access: All repositories These permissions are sufficient for any GitHub integration across Claude products. The tokens already exist on Anthropic's servers. ### What Fixed My Issue **Disable the GitHub Connector, then install the GitHub App:** ` Claude.ai → Settings → Connectors → GitHub → Disable Then: claude.ai/code → Install GitHub App → Works `` After 500+ failed attempts across multiple devices, browsers, and networks (including cellular), disabling the Connector fixed it on the first try. ### Workarounds by Use Case Claude Code users (web or CLI): Disable the GitHub Connector. Use only the GitHub App. Full agentic access (clone, edit, commit, push, PRs). Dev-comfortable, Claude Desktop users + Claude Code CLI users: Consider the [GitHub MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/github). More control, works locally, requires configuration. Claude.ai chat/Projects only (no Claude Code): Use the Connector only. Don't install the GitHub App, or expect conflicts. Multiple products: Pick one integration, disable others. But this doesn't work across all interfaces: ### Interface x Integration Support Matrix GitHub Connector GitHub App GitHub MCP Server Claude.ai web (chat) ✅ ❌ ❌ Claude.ai Projects ✅ ❌ ❌ Claude Code (web) ❌ ✅ ❌ Claude Code (CLI) ❌ ✅ ✅ Claude Desktop ❌ ❌ ✅ Claude mobile (iOS/Android) ✅ ❌ ❌ There is no single GitHub integration that works everywhere. If you use multiple Claude interfaces, you currently cannot have unified GitHub access. ## Also, if the issue is intermittent then consider whether the flips align with switching interfaces, it could be that one succeeds and then causes the other one to fail. Maybe. Again, this is just conjecture, based on partial data. I do not have access to anthropic data. ### Why This Is Happening (Speculation) This appears to be an organizational alignment issue rather than a technical limitation: The GitHub App already has full OAuth permissions The Connector doesn't leverage these existing credentials MCP is open but limited to Desktop/Code CLI Three teams, three systems, no unified auth The fix is straightforward: The Connector should leverage the GitHub App's existing OAuth tokens. One authorization → works everywhere. This requires internal coordination, not protocol changes.

man you saved my day, god bless you!

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.