[BUG] GitHub Connector connected in Claude Desktop but not recognized by Claude

The "Add to GitHub" part has been activated, but why is my account unaware?

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/29415
2. https://github.com/anthropics/claude-code/issues/30457
3. https://github.com/anthropics/claude-code/issues/2682

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

Same issue, connection doesn't work.

<img width="2141" height="1264" alt="Image" src="https://github.com/user-attachments/assets/cada1a1e-e5bb-460e-87ea-8edd32f3d7f8" />

<img width="1887" height="1257" alt="Image" src="https://github.com/user-attachments/assets/ec12ee28-c520-4e5f-9c9f-e8faa327f7ef" />

@claude

There are a lot of the same issues and they are global.
It would be nice if there was a PR that could fix this part.

@claude I too am facing the same problem as @kss2002

What I see is that there all no tools listed in Github connector, unlike other connectors. So something is problematic

<img width="1154" height="1010" alt="Image" src="https://github.com/user-attachments/assets/c258f585-40fa-4443-9948-0890876d52b0" />

<img width="1110" height="932" alt="Image" src="https://github.com/user-attachments/assets/03871967-bb0f-4c2b-9b10-b1c0e74e38c4" />

GitHub_Connector_Bug_Report.docx

same error.
I was using claude with github configured and now isn´t working

Yep. Same error here too. No repositories displayed and if I paste a repo link, that still doesn't work.

I solved! translate to english, i speak spanish hehe
Despues de probar muchisimas maneras y distintas formas de escribir el json en el %appdata%, tambien probar con DOCKER y wsl con ubuntu, y buscar y buscar, entendi que puedo crear una token classic, pasarle a Claude en un nuevo chat, dandole el contexto de mi proyecto y actividades pendientes, le digo que accione directamente con el token, y lo hace!
Asi que: solo pasale tu token y dale instrucciones, dile que actue y haga cambios al repositorio directamente con el token que le diste.

Same here, the connector is not working.

Same issue

same issue here.

Same issue.

same issue here.

I have same issue with Drive connector. I am new en claude.ai

Stuff like this is why I'm cancelling my subscription. The token usage for code is also broken, i can max out my usage in 30 minutes with a single prompt. Codex is 100x better.

Same issue here

Same here

Same here

Same here

same here

Same here

I have the GitHub Connector installed and connected, I have the CLI installed and authenticated... but Claude cannot even give me a listing of my repositories. The GitHub does not display as an option in either Cowork or Code... only chat, and even there when I choose the Select a repository button, it is only displaying 4 of my repositories.

Still same issue.

I also have the same issue, on the latest version of claude desktop, reconnecting or anything doesn't work

We also have the same issue at our organization.

same issue. organization account of pro, personal account of max with two desktop instances exhibiting same problem.

Same issue here

Same issue

Same issue here

<img width="1626" height="891" alt="Image" src="https://github.com/user-attachments/assets/ed2ed0b5-6e2f-4808-af13-31d1cf2ab4de" />

Same issue

same here , happened suddenly after installing mac tahoe

heard so many good things about claude, decided to get max, cant even connect to github ?????

I resumed it would be able to read to and write from my repos but it does nothing.

Same here

Same issue here

<img width="807" height="1363" alt="Image" src="https://github.com/user-attachments/assets/2dbe5e90-c134-4cfd-81aa-b3635f4febe1" />

<img width="1709" height="1029" alt="Image" src="https://github.com/user-attachments/assets/494f5c65-7a98-4311-93a6-5155833b3987" />

Same issue here

same issue

same here
+1

Same here +1

Tried to give permission on my github but still not working with the connector, i can add a custom github?

[sorry my english in advance]

WORKAROUND - Custom github mcp

Guys i had to add a new custom tool as a workaround, go to the claude_desktop_config in app_data claude folder, and added the json

``` JSON
{
"preferences": {
"coworkWebSearchEnabled": true,
"coworkScheduledTasksEnabled": false,
"ccdScheduledTasksEnabled": false,
"sidebarMode": "chat"
},
"mcpServers": {
"github": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "Your classic github token"
}
}
}
}

then restarted my cloud desktop and it worked.

You can ask the claude for help to config this

Tried using the GitHub MCP Server by adding a custom connector to https://api.githubcopilot.com/mcp, but it only has access to public repositories.

Same here +1

same here +1

Same problem! I already tried to Connect and Disconnect GitHub connector too many times, still the same problem. Claude does not recognize the GitHub connector, and when I try to browse my repos, it shows me an empty repository even though I have 1 private repository.

Same Problem here after i did the last update of the desktop version. Also not working in any of the other versions. Chats dont recognize anything in my repositories.

<img width="1656" height="823" alt="Image" src="https://github.com/user-attachments/assets/da657748-d2f8-4a3f-9c43-6200ebfd799e" />

i was having the same problem. then i noticed i can actually create a new project and then add a repo from github:

<img width="1345" height="517" alt="Image" src="https://github.com/user-attachments/assets/19600d09-4850-4635-a844-76cebb343b46" />

maybe this is how they intend it to be used.

Came here out of desperation assuming user error or config issue. Happy to see that it isn't my ineptitude, quite disappointed to see this has been an issue for so long.

Still occurs on version Claude 1.2.234 (2d1855) 2026-04-01T07:58:22.000Z

Same here, cannot access GitHub and keep getting errors saying gh cannot be found. Even after selecting the issue in the specialized UI in the desktop app to start the session, Claude still fails to actually read the issue.

I've connected the GitHub connector and get the following output every single time. Had no issues updating and defining GitHub issues inside the desktop app last week.

<img width="738" height="666" alt="Image" src="https://github.com/user-attachments/assets/46e6b8df-10d1-457b-9205-a997e79eade1" />

@Moabe124 solution worked wonders for me !

I think this might be intentional. The Google Drive integration works the same way - it shows up in chat when you click the + button, and you select exactly what you want to give it access to for that chat. That isn't very useful to me, though.

GitHub's own instructions cover adding it as an MCP server, which will allow Chat/Cowork to use it when it decides it needs to: https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-claude.md - this has been working great for me.

I think this might be intentional. The Google Drive integration works the same way - it shows up in chat when you click the + button, and you select exactly what you want to give it access to for that chat. That isn't very useful to me, though. GitHub's own instructions cover adding it as an MCP server, which will allow Chat/Cowork to use it when it decides it needs to: https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-claude.md - this has been working great for me.

I don't think what Claude calls 'Connectors' is the same as adding a mcp server, at least from an external stand point.

And in my case, github doesn't show up when clicking + > Connectors

@rikkitissier

The GitHub connector is used for Claude Code on the web to connect to your GitHub repos. It's not an MCP that provides Claude access to things like getting GitHub Issues. I can see why it's confusing but others have noted how it differs from the Google Calendar connector for example.

If you're using Claude Code, the official GitHub MCP is worth a look. Or, install the GitHub CLI which Claude can use.

@amorriscode

The GitHub connector is used for Claude Code on the web to connect to your GitHub repos. It's not an MCP that provides Claude access to things like getting GitHub Issues. I can see why it's confusing but others have noted how it differs from the Google Calendar connector for example.

If you're using Claude Code, the official GitHub MCP is worth a look. Or, install the GitHub CLI which Claude can use.

Hey Anthony, thanks for your response!

It does leave me puzzled then since I have the GitHub CLI installed and Claude actually tries to use it but with no luck.

I am able to select the issue in the session creation window using the little plus icon and them importing the GitHub issue, have the GitHub CLI installed, and then Claude actually tries to run the GitHub CLI commands but then says the CLI is not available.

I suppose there might be an issue with reaching the GitHub CLI from the desktop app? I don't see the use case for selecting a GitHub issue in the Claude Code desktop app when the issue cannot be read, though I suppose this might be an entirely different issue.

When asking to read the same issue in my terminal and in the desktop app. On the same branch:

<details><summary>Terminal</summary>
<p>

<img width="589" height="200" alt="Image" src="https://github.com/user-attachments/assets/67168f85-58f0-4fbe-bac1-8543bfad1f10" />

</p>
</details>

<details><summary>Desktop app</summary>
<p>

<img width="698" height="525" alt="Image" src="https://github.com/user-attachments/assets/41e4be5c-fb64-4f41-b2c0-0b72b0f172b4" />

</p>
</details>

@amorriscode
Sorry for the follow up, but I can apparently convince Claude that he does have access to the MCP tooling and it works? lol

Doesn't always work

Tool call when it worked
ToolSearch select:mcp__github__issue_read

<img width="748" height="656" alt="Image" src="https://github.com/user-attachments/assets/1cfcba9f-79a9-4e97-b594-0790182622f0" />

Potential Cause

Seems that in the first try Claude messed up the tool call.

<img width="348" height="149" alt="Image" src="https://github.com/user-attachments/assets/3f6de8fb-bb06-4d9f-b659-3d9259fccf42" />

@xKelvin thanks for the screenshots. It looks like there might be a bug with the path because your screenshot shows that gh could not be found. I'd be curious to see the expanded tool calls after you said it has access to the MPC.

@amorriscode
Sure no problem. I suppose you mean this one?

<img width="768" height="173" alt="Image" src="https://github.com/user-attachments/assets/babb9e3c-0a10-4f52-9fc4-8e73d6afed49" />

In short, the first time it tried to call:
select:mcp__github__get_issue and failed

Then after my retry, it tried to call:
select:mcp__github__issue_read, and succeeded.

Also, as a test, I had claude update the issue but after trying a whole bunch of commands it failed again.
I often use the desktop app for issue definition, and I've seen this work in the past. Though it stopped working a few weeks ago.

<details><summary>Write tool call attempt</summary>
<p>

読み込まれたツール, ツールを使用しました
Issue Write
ToolSearch select:mcp__github__issue_write
No matching deferred tools found
ToolSearch github issue write update

The mcp__github__issue_write tool was already loaded earlier. Let me call it directly with the updated body (checklist removed).


読み込まれたツール, ツールを使用しました
Issue Write
ToolSearch +github issue
ToolSearch select:mcp__github__issue_write,mcp__github__issue_read
No matching deferred tools found

It seems the GitHub MCP tools were loaded during the earlier call but may have been evicted from the tool cache. Let me try to reload them.

読み込まれたツール
ToolSearch mcp github issue write
ToolSearch select:mcp__github__issue_write
No matching deferred tools found

Let me try calling the tool directly — it was listed as available in the system and may already be loaded.

読み込まれたツール, ツールを使用しました
Issue Write
ToolSearch select:mcp__github__issue_read,mcp__github__issue_write,mcp__github__add_issue_comment
No matching deferred tools found

ToolSearchgithub write update

I'm having trouble finding the mcp__github__issue_write tool schema through ToolSearch despite it being listed as available. Let me try one more approach.

読み込まれたツール, ツールを使用しました
Issue Write
ToolSearch select:mcp__github__issue_write,mcp__github__issue_read,mcp__github__add_issue_comment,mcp__github__create_or_update_file
No matching deferred tools found

I'm sorry — the mcp__github__issue_write tool appears to be listed but isn't actually functional in this session. The issue_read tool worked fine earlier, but write access to issues seems unavailable.

</p>
</details>

Had the same issue and that took care of it:

Add GitHub as a custom MCP connector — In Claude (web or desktop), go to Settings → Connectors → Add custom connector and point it at GitHub's MCP server: https://api.githubcopilot.com/mcp/. You'll authenticate with your GitHub account, and Claude will then be able to browse repos, read files, open issues, and review PRs in future conversations.

Note that you'll need OAuth credentials (not optional), because api.githubcopilot.com/mcp authenticates each user individually rather than using a shared token.

Here's how to get them:

Go to: https://github.com/settings/developers → OAuth Apps → New OAuth App

Fill in:

Application name: anything (e.g., "Claude MCP")
Homepage URL: https://claude.ai
Authorization callback URL: https://claude.ai/api/mcp/auth_callback (Claude should display the exact callback URL during the connection flow — use that if it differs)

Click Register application
On the next page, copy the Client ID
Click Generate a new client secret and copy it immediately (you won't see it again)
Paste both into the Claude "Add custom connector" dialog's Advanced settings
Click Add → Claude will redirect you to GitHub to authorize, and that flow will let you grant private repo access

Note that you'll need OAuth credentials, because api.githubcopilot.com/mcp authenticates each user individually rather than using a shared token. Without them, the connector has no way to prove who you are to GitHub.
Here's how to get them:

Go to: https://github.com/settings/developers → OAuth Apps → New OAuth App

Fill in:

Application name: anything (e.g., "Claude MCP")
Homepage URL: https://claude.ai
Authorization callback URL: https://claude.ai/api/mcp/auth_callback (Claude should display the exact callback URL during the connection flow — use that if it differs)

Click Register application
On the next page, copy the Client ID
Click Generate a new client secret and copy it immediately (you won't see it again)
Paste both into the Claude "Add custom connector" dialog's Advanced settings
Click Add → Claude will redirect you to GitHub to authorize, and that flow will let you grant private repo access

@laudusseau - you're a life saver thank you so much for the tip above :)

This issue has been fully solved for me with the new desktop app and the GitHub MCP.

The default "GitHub Connector" is not working.

Version: Claude 1.2773.0 (884b37) 2026-04-15T14:32:09.000Z

<img width="600" alt="Image" src="https://github.com/user-attachments/assets/4b668d39-9363-4826-9d30-8278a4dd7c60" />

<img width="600" alt="Image" src="https://github.com/user-attachments/assets/61e890cb-db41-48c8-8462-bb449f0b5557" />

---

As of now, only the custom GitHub MCP works. Solution suggested by @laudusseau https://github.com/anthropics/claude-code/issues/32479#issuecomment-4226575677

<img width="600" alt="Image" src="https://github.com/user-attachments/assets/6a352a1d-6450-43ef-af8b-d1b7d5ba533e" />

<img width="600" alt="Image" src="https://github.com/user-attachments/assets/ece06671-7ec7-4e48-aa9d-22173ffb441c" />

I also thought the default "Github Connector" did not work. However, it might even work, is just super limited in functionality. And also it is not configurable like other connectors in Claude, so that behavior is normal, even it seems not working.
You can test if it works by opening the + in a chat and see if it says "Add from Github". but you can only add specific folders or files, very limited in size. And Claude would also not be able to interact with Github in any other way, like you would normally expect it from a connector.

If you don't see that option, you can trigger a new authentication from github. In your settings, under applications, authorized github apps, you can revoce Claude access and once you restart Claude, and reconnect the Github connector, it will reauthenticate and you'll be able to see the add from Github Option.

<img width="968" height="721" alt="Image" src="https://github.com/user-attachments/assets/bba09021-e0c5-4e9a-b371-84cca8dd5037" />

But again, the functionality is very limited, so if you want to work with Github from Claude web, Desktop Chat or Cowork, then I highly recommend to add the Github MCP as a custom connector as described here https://github.com/anthropics/claude-code/issues/32479#issuecomment-4226575677

The GitHub connector is used for Claude Code on the web to connect to your GitHub repos. It's not an MCP that provides Claude access to things like getting GitHub Issues. I can see why it's confusing but others have noted how it differs from the Google Calendar connector for example. If you're using Claude Code, the official GitHub MCP is worth a look. Or, install the GitHub CLI which Claude can use.

For Claude Code it works, but sometimes you want Claude Cowork to have some access to your code or github repo for other stuff than just coding

Unable to find official connector or create a custom one. I'm on Claude 1.7196.0 (2dbd78). What is the current way of connecting it?

Using the Github OAuth App is not secure, your giving the model full on read and write access to everything.

I think the issue is clear — this is a UX bug.

When you add the GitHub connector, it’s actually being added to Claude in the cloud, not to the desktop app. One clear sign of this is that if you disconnect GitHub and reconnect it, you get redirected to Claude Web.

Another way to confirm it: open Claude Web, click the + icon, and you’ll see the GitHub connector there.

also needing to use custom connector pretty annoying

Found a fix:

In the claude desktop app:

• Open a new chat
• Press the + icon in the bottom left
• Press "add from github"
• Click the link icon
• Search for one of your private repos
• It will most likely say it does not have access, click the link it gives you to install permission
• It takes you to github where you install some claude connected
• Restart claude and you can now add files through that same "add from github" workflow

did this after already having connected it in claude (without it working)

it still claims to not have access to github when just asking it, but you can work with files from private repos through the add from github workflow. Maybe I have misunderstood how it is supposed to work, either way this works for now

UPDATE: give it a minute, when restarting the desktop app it now works without the "add from github" workaround. works as of 22/6/2026

I am seeing the same thing, I connected GitHub, I authorized access through the redirection that gave permissions. It shows that it is connected in Claude. When I add a GitHub repo and try to ask about it, it tells me that it is private. When I ask in chat/cowork/code for it to show me the tools available is says it has no tools available. I showed it the screenshot that it was enabled and it tried to tell me various things to try, all of which had no impact on the issue at hand. Just remove the connector if it does not work, this was a beyond frustrating experience with no clear resolution.

Found a fix: In the claude desktop app: Open a new chat Press the + icon in the bottom left Press "add from github" Click the link icon Search for one of your private repos It will most likely say it does not have access, click the link it gives you to install permission It takes you to github where you install some claude connected Restart claude and you can now add files through that same "add from github" workflow did this after already having connected it in claude (without it working) it still claims to not have access to github when just asking it, but you can work with files from private repos through the add from github workflow. Maybe I have misunderstood how it is supposed to work, either way this works for now UPDATE: give it a minute, when restarting the desktop app it now works without the "add from github" workaround. works as of 22/6/2026

This somewhat worked for me.

Preface: I was trying to setup a scheduled routine that needed access to a private repo.

Doing the above worked, but after it finished it claimed I needed an enterprise plan for this feature. I pressed back and the OAuth went through successfully without it firing an enterprise check again. Then I was able to run the routine on the private repo. I am guessing this is actually a bug in their enforcement logic, but it works for now. I wouldn't be surprised if this is patched or changed though.

Fixed the issue on my end. The claude_desktop_config.json I was editing to put in my PAT was not the same one as it brings you to when you click Settings -> Developer -> Edit Config. Put your PAT in there and if there is already info, you might ask claude to help you combine them (or if you know what you are doing...). So glad to see this one fixed!

After fixing that and restarting, it lists the github MCP server in Settings -> Developer. Hope that helps some others!

is there any update on this issue? It's very frustrating that this worked great before but has now been broken for some time.

Got this same issue today, have been working fine over the last week, Claude desktop shows that GitHub is connected, I then Started a new session and the new session to work on something and now Claude says it can't access the repo because it's private and Claude doesn't have permission to access it. Previous sessions had no issues connecting to the repo

Same issue for me. It was working then stopped. Disconnected and reconnected many times. Removed my work account in case it was a corporate setting. Still no joy. Refuses to acknowledge that it has any tools related to Github.

> Found a fix: > In the claude desktop app: > > Open a new chat > Press the + icon in the bottom left > Press "add from github" > Click the link icon > Search for one of your private repos > It will most likely say it does not have access, click the link it gives you to install permission > It takes you to github where you install some claude connected > Restart claude and you can now add files through that same "add from github" workflow > > did this after already having connected it in claude (without it working) > it still claims to not have access to github when just asking it, but you can work with files from private repos through the add from github workflow. Maybe I have misunderstood how it is supposed to work, either way this works for now > UPDATE: give it a minute, when restarting the desktop app it now works without the "add from github" workaround. works as of 22/6/2026 This somewhat worked for me. Preface: I was trying to setup a scheduled routine that needed access to a private repo. Doing the above worked, but after it finished it claimed I needed an enterprise plan for this feature. I pressed back and the OAuth went through successfully without it firing an enterprise check again. Then I was able to run the routine on the private repo. I am guessing this is actually a bug in their enforcement logic, but it works for now. I wouldn't be surprised if this is patched or changed though.

I went through the same flow you described, but it's still not showing the repository's files and branches as it used to. This has been going on for too long. It's really frustrating

What solution I ended up going with:

• Download GitHub desktop & connect to your GitHub account.
• Clone your target GitHub repo locally using the cloning feature in GitHub desktop.
• Go to the claude desktop app, go to claude code, give it full access to folder you just created with the clone feature.
• Claude now has full read & write access to your project locally. If you ask claude to make any changes to the project, it will show up in GitHub desktop. You can commit the changes from the GitHub desktop app and it will automatically sync to your project on GitHub.

Any other way to achieve this is ineffective. This works like a charm, have never had any issues with it since I started using this workflow.

@Archibald1948

Connector shows as connected (GitHub Integration, Web, with a checkmark in Connectors), but its MCP tools are not available in the session. At session start the server reported that it required authorization and was dropped from the toolset. I re-authorized mid-session; the connector UI kept showing connected, but the tools never appeared — three tool searches returned zero GitHub tools. Claude had to fall back to telling me to run git push myself.

Two issues: (1) re-authorizing mid-session does not reload the server's tools, and (2) the Connectors UI shows a connected state that does not reflect whether the tools are actually usable in the current session.

same for me, connected but unable to interact

same for me too, connected, but claude unable to interact

same for me, connected but unable to interact

Same here, unable to use github connector in simple chats or cowork.

+1 to @arasaka-inc answer. That's the only path that has worked for me. Direct connector between Claude desktop with Github web hasn't worked just as many users over last 2 days and in hte past have described.

same for me, it stopped working today.

one working option is to use a locally hosted MCP server, e.g. like this in Docker:

exec docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN="$TOKEN" ghcr.io/github/github-mcp-server

which can be added to claude_desktop_config.json like this:

  "mcpServers": {
    "github": {
      "command": "exec docker run -i ...."
    }
  }

ideally included using an executable file which also takes the PAT necessary from keychain using a command

TOKEN=$(security find-generic-password -a "$USER" -s "key-you-used-in-keychain-for-the-token" -w)

same for me, unable to interact in chat with github connector. Github Connector shows a connected status and Github shows Claude as an authorized Github App.

Same for us - we used it for an internal project for our team accessing our GitHub hosted scripts - not working anymore since about a month. any insights if this is being looked into would be appreciated - or is this on Githubs end, as this is labelled "invalid"?

How much do you need to pay that anthropic fixes this not us btw?

Having the same issue. And on top of that, Claude (Sonnet 5) doesn't seem to know its own documentation. It took me through countless loops that didn't make sense and guessed solutions

Same issue here.
Why isn't anyone resolving this issue?
cc:
@anthropic-xabi, @ah-anthropic , @km-anthropic , @np-anthropic , @wim-anthropic

I faced the same issue. There is a workaround with local github mcp server.
add mcp server config in the claude_destop_config.json, then restart claude desktop.

"mcpServers": {
"github": {
"command": "/bin/sh",
"args": [
"-c",
"GITHUB_PERSONAL_ACCESS_TOKEN=$(/opt/homebrew/bin/gh auth token) exec /opt/homebrew/bin/github-mcp-server stdio"
]
}

<img width="939" height="519" alt="Image" src="https://github.com/user-attachments/assets/4b38268e-8842-4406-bde6-306ed923ead6" />

<img width="688" height="426" alt="Image" src="https://github.com/user-attachments/assets/1d537ff5-8b18-4d62-8981-bb164ce98d19" />

MCP is an nice idea, might use that. but srsly, they should fix that.

This is a clever way for all of us to spend a ton of tokens...

declare a custom connector, the URL will be the MCP server for github. call it gh, then use the default settings the interface presents. When you use it, it will oauth you in.

Now, paste the URL for your repo, it doesn't work unless you tell it to use the connector gh you just created.

Free Palestine! Bye

This works for me, thanks @squidjam. I had Claude (browser extension) drive most of the setup. I also asked Claude to help with this comment (good way to spend tokens?). It added more on its steps:

Key detail: the Remote MCP server URL is https://api.githubcopilot.com/mcp/ (GitHub's official one). Named the connector gh, used Anthropic's hosted client metadata for the OAuth client, left everything else default, then hit Connect and signed in through GitHub's OAuth flow.

i did some debugging in my case

git config maintenance.auto false
git config gc.auto 0

this did not really fix my issue, but it turned out some of those files/objects created by git/claude where instantly readonly (e.g. .git/zz_unlink_probe ✓ removed rm -f .git/objects/maintenance.lock
rm -f .git/refs/bundle-test-verify.lock)

this is not an final debug, but claude build some clever (and not so clever) workarounds because he claimed "the device bridge is wretched" and the proxy would refuse his push requests. Also check the app sessions in your github application permissions. If you select the repos you want manage with claude are in the array of allowed repos. In doubt, do the usual thing (re-connect integration, restart application) and what i tried, do a new project and start asking wtf is going wrong. claude will weasel around asking you to do stuff. instruct him that he lives in his VM and should do the git settings at his side (or he will ask you strange workarounds to mitigate the actual issue)

on a mac the "device" sessions (on top there is a cloud (like a browser session)) or an desktop symbol. The local (desktop ons) are running encapsulated on a mac it looks like this:

<img width="790" height="24" alt="Image" src="https://github.com/user-attachments/assets/8e6d04ae-bc5e-4f6c-a912-d363d1dad0df" />

it will mount the directorys you share inside this VM and running commands with the mount/device bridge when it writes the "ran a command on your computer".

If the reply is odd, remind him that he is actually trapped in his VM and that he should check if he can actually change stuff. he got a nice workaround to move files away that he could not delete and build a direcotry _to_delete that contained those git .lock files.

When multiple "ran a command" lines start dropping, ask him "what are you doing". he might do crazy loops of bs.

Also if you go to "get help" in on your profile you can actually request to get money back from anthropic. Did that, will report back if this device bridge saga is accepted as an reason to not pay an pro plan and looping agents start roaming around. You will get an ID number and the promise that a "human" would look into it.

Any update on this? I'm seeing this too

I started to give it access via gh and that works kind of. still super bad that this seems an bug within cowork / the desktop app but not tine to debug depper as the software creator should do that. have a look at hermes agent ;)

Same failure here, plus the business impact [BLOCKER]

Adding our timeline and a business-impact data point, in case either helps with prioritisation.

How it degraded for us

• Mid-April 2026: activated the connector. Worked without issues for a week or two.
• Late April 2026: prompts to re-authenticate this connector started appearing, roughly daily from what I recall. No other connector behaved this way.
• Mid-May 2026: total loss of function. Claude no longer identifies the connector as present when asked whether it is available, while every other connector on the same account continues to work normally.

A colleague hit the identical progression on a separate account, having started using the connector in early May, so this is not isolated to one profile or one machine.

Worth noting the shape of it: working, then repeated re-auth prompts, then the connector silently dropping out of the tool list entirely. That reads more like token or session expiry than a local configuration problem, and it reproduced across two independent accounts in our org.

Impact: this blocks the customer-feedback loop for Customer Success

We run a small team with a single full-time CS function, and the first-party GitHub connector is the only automated link between our customer-facing tooling (CRM, support desk) and the product backlog. With it connected but not exposing tools, two core CS capabilities are blocked.

Inbound: customer feedback into product. Defects and feature requests arrive through client meetings, written messaging and support tickets. Turning those into well-formed GitHub issues, with reproduction steps, account context and the business justification attached, is now entirely manual re-entry. Claude can draft the issue but cannot file it, so every item needs a human to copy it across. In practice feedback gets delayed before it reaches engineering.

Outbound: product updates back to customers. Closing the loop is the other half, and it is the half that customers actually notice. When an issue is commented on, fixed or shipped, CS needs to identify which accounts asked for it and tell them. Without read access to issue state we cannot check status across the open items raised on behalf of clients, so the people who reported something get no proactive update. Every "what happened to the thing I reported?" is answered late and by hand.

Neither of these is cosmetic. They are the basic mechanics of a working feedback loop, and this bug converts both into manual effort that does not scale past a handful of accounts.

On the custom MCP server workaround

We have attempted a custom GitHub MCP connector as a workaround more than once without success. Our take is that permissions work is disproportionate to the use case: PAT versus GitHub App scoping, per-repository allow lists, org-level approval, plus the token handling and rotation that follows. For what is a narrow CS need (create an issue, read issue state, read release notes) the configuration overhead is not justifiable, and it pushes credential management onto a non-engineering function.

Each attempt has ended in one of two places: a connector that authenticates cleanly but exposes no tools, which is the same failure mode as this bug, or a scope combination our org will not approve.

The first-party connector working as documented is the only realistic path for us. Happy to supply logs if that is useful.

Adding a business impact data point, since this issue is labelled invalid but is clearly reproducible across accounts.

We are a Claude customer on a paid plan and the GitHub connector shows as connected but exposes zero tools in every session since mid-May 2026. Still failing today, 2 October 2026. The CRM and Support platform connectors work fine in the same environment, so this is isolated to the GitHub connector.

Impact: our Customer Success team cannot create GitHub issues from customer feedback or check issue status to report fixes back to customers.

I have also opened a support request with Anthropic. Could a maintainer clarify whether this belongs here or in another tracker, and point to the right place for a fix? Related open reports: #61682, #57589, #94532, #52549.

Same issue

Thanks @PedroPalhoto for linking #61682 here. It's the same bug, reported for Cowork on Windows 11 on 23 May, with 33 comments since across Windows, macOS and Linux. Linking back so the reports sit together.

Still happening for me: GitHub shows "Connected" in Customize > Connectors, but no GitHub tools load in any Cowork session, while my other connectors work fine. Given how many accounts reproduce this, could the invalid label be reviewed?