GitHub connector links repositories successfully but Claude cannot access content for ANY repository (account-wide, public and private alike) — recent regression

Re: the auto-applied "invalid" label — this report is intentionally filed here because the GitHub connector bug affects the same Claude account/app ecosystem, and similar GitHub-integration bugs (e.g. #32479, #33875) have been filed and discussed in this repo despite not being Claude Code CLI issues. Flagging in case a maintainer wants to redirect this to a more appropriate tracker — happy to move it if one exists.

I've been facing this issue too.

Revoked claude connection in both claude.ai and github settings. Relink doesnt work.

Inspected network tab and it does successfully fetch info from github api. (hoping this might narrow somethings down)

Add repository button adds a link to the repo in chat (prev. the interface could retrieve all selected files and sync knowledge before the message was sent)

<img width="908" height="394" alt="Image" src="https://github.com/user-attachments/assets/7f430ee5-4eec-44dc-91bd-39a20075ff5f" />

same issue here

Experiencing the same issue today.

same issue here today

Same issue here.

it's been almost a week if not longer than that.

Same issue here

Same issue for me.

Same regression here.

Environment: claude.ai web chat (browser), Claude Pro, Windows 10.

Symptom matches exactly. Adding a repo via "+ → Add from GitHub" in chat completes without error, and my repositories do show up in the picker, but only an inert reference (the bare repo URL) gets attached. Claude cannot read the file tree or any file contents and has no GitHub tools available in the session.

Where the break actually is (network-tab observation): the GitHub-facing calls succeed. After selecting the repo, the frontend successfully loads the repo metadata and the full tree (paths, sizes, SHAs, with "truncated": false). So fetching from GitHub works end to end in the browser, but the data never reaches the model's chat context. This points at the frontend-to-context ingestion step, not at GitHub auth or retrieval.

Ruled out on my side: verified the Claude GitHub App's installed permissions, disconnected and re-authorized the connector from scratch (in both claude.ai and GitHub settings), and re-selected the repository and branch several times. No change. The connection itself is healthy; only the ingestion into chat fails.

One more observation, since I'm not sure whether it's intended: only the repos themselves are listed, with no tree to drill into. This may well be part of the redesign — if file selection is meant to move into the conversation instead of happening up front — but I can't tell from the outside whether it's intentional or a side effect of whatever broke the retrieval.

Addition: Surface-specific, important narrowing: the regression appears limited to the in-chat attach. But the Project knowledge dialog ("Add content from GitHub → select files to add to this project") still shows the full file tree with per-file checkboxes and lets me select individual paths, exactly as before — in a chat inside that project the file content is read correctly there. Same connector, same repo, two entry points, only the chat one is broken.

Still broken as of June 28, 2026. (Written with help from Claude)

Hi Guys, this is still going on. Since they removed the bug tag and added the invalid tag, will that mean that they'll just ignore this?

The issue persists and there is no fix yet. I am using repomix as a workaround. As like many other I did verify the Claude GitHub App's installed permissions, disconnected and re-authorized the connector from scratch (in both claude.ai and GitHub settings), and re-selected the repository and branch several times. No change. The connection itself is healthy; only the ingestion into chat fails.

Here is fragment of the chat transcript while i asked it to fetch me the file tree of my repo. [Repo Name changed Intentionally].

'''
The user is asking me to "generate a full file tree of this repository branch so I can confirm you see everything" with a link to https://github.com/NeoOne601/RepoName/tree/main
Let me think about what I actually have access to here:

I don't have live access to the GitHub repo - my earlier attempts to web_fetch this URL failed with ROBOTS_DISALLOWED
What I DO have is the repomix-output.xml file that was uploaded in the previous turn, which contains a directory_structure section that I already read and viewed

The user wants me to "confirm I see everything" - this is a verification/trust check. Given the conversation history, I should:

Be honest that I cannot live-browse the GitHub URL (confirmed earlier - ROBOTS_DISALLOWED error)
What I actually have is the repomix-output.xml snapshot from their last upload, which contains a full directory_structure listing
I should generate the file tree FROM that repomix snapshot, not pretend I'm fetching live from GitHub

This is important for honesty/transparency given the established pattern in this conversation - I already made mistakes by assuming things about the codebase without verification, and the user has been testing/correcting me on this. I should not pretend to fetch the live GitHub URL again (it will fail) or pretend that what I'm showing is a live fetch. I need to be precise: this is the file tree AS OF the repomix-output.xml file they uploaded earlier in this conversation, which represents a snapshot, not necessarily the absolute live HEAD of main if they've pushed anything since then.
Let me try the web_fetch first to see if it works now (maybe worth a quick check), but I recall it failed with ROBOTS_DISALLOWED. Let me just try once via web_search to see if there's a cached/alternate view, but I should not spend too much time on this since I already know from earlier this conversation that:I will eventually fail.
'''

same issue here

same issue

Hi Guys, this is still going on. Since they removed the bug tag and added the invalid tag, will that mean that they'll just ignore this?

i think its marked invalid due to this being the repo for claude code, not the claude ai, or llm, or whatever but im sure u get my point

Dang! I thought I was alone! This is killing me! We need to find a way to fix this :)

@Antares9879 can you try to change the label back to a bug? You specified that this is not a claude code issue, but the web interface, but it still got flagged as invalid. Did you find a workaround?

driving me crazy

same pb here

@bcherny can you please let other teams know of this issue so it can be fixed.

Same problem here

issue exist still today

same issue here for a week, even after updating to the latest version Claude 1.18286.0 (259c3f). Also happens in the browser.

does anyone knows how can we escalate this further, so that it reaches the team and a human eye?

Since this is a claude.ai web connector issue, not Claude Code CLI, it is NOT being addressed.

Per Claude:
What actually gets this in front of the right people, in order of effectiveness:

1.) In-product feedback (highest signal for claude.ai bugs): Use the thumbs-down / feedback option directly in a claude.ai chat where the GitHub connector fails, and reference issue #71542 in the description. This routes to the claude.ai product team, not the open-source CLI repo.

2.) support.anthropic.com — file a support ticket describing the regression (dates, consistent account-wide failure, both public/private repos affected). Support tickets get triaged internally to engineering, unlike a public GitHub issue that lives in an unrelated repo.

up - impacting myself and multiple other users I know, on Max plans. this is breaking and will potentially necessitate a switch to Codex.

same pb here. lost several hours.

same issue here!

Same issue here. I've been with the product pretty much since it came out, I never seen such a prominent bug dragged on like this.
I understand the preference of users using the CLI (much higher TPS, more $), but I need to be frugal while pre-rev.
Please fix this ASAP.

Same issue here. Claude GitHub App is installed with "All repositories" access on my personal GitHub account, and the connector shows as connected. Repository names ARE selectable in the picker (unlike some other reports), but after selecting a repo, the folder/file tree comes back completely empty — for every repository, public and private alike.

Tried: uninstalling and reinstalling the GitHub App with All repositories access, disconnecting/reconnecting the connector in Claude Desktop settings, fully restarting the app. No change.

Client: Claude Desktop (project "Add content from GitHub" flow)
GitHub username: mitokondoria211
Example repo: mitokondoria211/techMemo-front
Claude plan: individual (Free/Pro/Max)

Same Issue here

Same issue here

I've tried @davidhunter-em 's recommendation. I assume nobody has seen/heard any updates/actions on this by the developers?

I have this same issue in the Claude Desktop app as well as the Web App.

SAME ISSUE HERE.

This has been really frustrating and it is breaking how I actually work.

I am on the MacOS desktop chat, not Claude Code. Sharing a GitHub repo into a normal conversation used to work perfectly and it was my main way of using Claude for coding. I would attach a repo, and used Claude for work from normal chat interface.
Now it is dead. I open "Add content from GitHub", pick my repo and branch, click the white "Add repository" button, and all it does is paste the plain repo URL into my message box. The repo never attaches. Claude cannot see the file tree or any file!!

I have disconnected and reconnected the GitHub App and reselected the repo and branch many times. Nothing changes.

This leaves me stuck, because Claude Code is not an option for me. I find it relentless and exhausting to work with, so sharing a repo straight into a normal chat was the ONLY method that actually fit how I code. Now that it is broken I am back to pasting files one by one.

PLEASE FIX QUICKLY

I've submitted a link to this thread to the Claude help bot, labelled it as a technical issue and detailed both the issue at hand, and the fact that the thread has been tagged as invalid bc it's been submitted to the claude code page - rather than the Claude app page.

Their team does review chats with the help bot that are categorised as a technical issue. I'd recommend that everyone else also submits the link to this thread with a short summary of the issue, in order to get it in front of the dev team as quick as possible.