[BUG] Personal account repositories not visible in Claude web, only organization repositories work

Is there any update on this? Super frustrating.

Install the claude github app in the private repo to show the private repos.

I created an org, installed Claude code in there giving access to all repos and I'm experiencing the same

Edit: as last resort, I disconnected and connected GitHub again from settings. Now I see all repos from my account and org.

please fix this, is just annoying and everyone seems to be complaining

just canceled Claude for now until this is resolved. I will be using perplexity for now. let us know when its fixed.

Same problem here

I was able to fix this by disconnecting Claude from my GitHub user and then reconnecting it. This seemed to trigger some sort of refresh, and then I was able to add the organizations and repositories correctly.

As noted here https://github.com/anthropics/claude-code/issues/28738#issuecomment-4120321837 , this is a regression, as up until some weeks ago I was able to authorize only my personal github repos. It is now all-or-nothing, where I cannot add only my personal repos.

edit: resolved itself on my end, hiding my comment

This is a known limitation of the Claude GitHub App — personal account repos aren't always visible in the Claude web interface.
Workaround 1 — Use the CLI instead:

cd /path/to/your/personal/repo
claude

The CLI works directly with your local checkout, regardless of whether the GitHub App can see the repo.
Workaround 2 — Remote Control from CLI:
If you want the web/mobile convenience:

cd /path/to/your/repo
claude

Remote Control lets you interact with the session from your browser or phone, using the local repo.
Workaround 3 — Check GitHub App permissions:

1. Go to github.com/settings/installations
2. Find the Claude app → Configure
3. Verify "Repository access" includes your personal repos
4. Try toggling from "All repositories" to "Select repositories" and manually selecting them

Some users found that explicitly selecting repos (instead of "All") resolved the visibility issue.
Workaround 4 — Transfer repo to an org:
If you need the Claude web UI specifically, creating a free GitHub organization and transferring/forking the repo there may make it visible. Free orgs have no cost and the GitHub App seems to work more reliably with org repos.

so, spent 3 hours and create the solution

Fix: Claude "Failed to create marketplace"

When creating a marketplace in the Claude UI or via CLI, users get a generic "Failed to create marketplace" error or a technical error: "Invalid input: expected object, received string". This happens because the Anthropic marketplace validator now strictly requires a nested object structure that wasn't necessary in older versions.

You must create the configuration file directly in your GitHub repository (not just locally).
Path: .claude-plugin/marketplace.json (The dot at the start of the folder is mandatory).
Root Requirement: Ensure a README.md exists in the root of your repo, otherwise indexing will fail.

1. Correct JSON Schema

Copy and paste this exact structure into your marketplace.json:
{
"name": "your-unique-plugin-id",
"description": "Short description of your tools",
"owner": {
"name": "Your Name",
"email": "your-email@example.com"
},
"plugins": []
}

Use code with caution.

1. Key Features & Why It Works

The owner Object: Previously, owner could be a simple string (e.g., "owner": "name"). This is now deprecated. It must be a nested object { "name": "...", "email": "..." }. If a string is provided, the validator fails with "expected object".
The plugins Array: The "plugins": [] field is now mandatory. Even if empty, it must be an explicit array. If omitted, the schema returns undefined and blocks creation.
Naming Rules: Use lowercase only and hyphens. Names like claude-plugins-official are reserved and will be blocked by the system.
use AI to explain

so, spent 3 hours and create the solution Fix: Claude "Failed to create marketplace" When creating a marketplace in the Claude UI or via CLI, users get a generic "Failed to create marketplace" error or a technical error: "Invalid input: expected object, received string". This happens because the Anthropic marketplace validator now strictly requires a nested object structure that wasn't necessary in older versions. You must create the configuration file directly in your GitHub repository (not just locally). Path: .claude-plugin/marketplace.json (The dot at the start of the folder is mandatory). Root Requirement: Ensure a README.md exists in the root of your repo, otherwise indexing will fail. 3. Correct JSON Schema Copy and paste this exact structure into your marketplace.json: { "name": "your-unique-plugin-id", "description": "Short description of your tools", "owner": { "name": "Your Name", "email": "[your-email@example.com](mailto:your-email@example.com)" }, "plugins": [] } Use code with caution. 4. Key Features & Why It Works The owner Object: Previously, owner could be a simple string (e.g., "owner": "name"). This is now deprecated. It must be a nested object { "name": "...", "email": "..." }. If a string is provided, the validator fails with "expected object". The plugins Array: The "plugins": [] field is now mandatory. Even if empty, it must be an explicit array. If omitted, the schema returns undefined and blocks creation. Naming Rules: Use lowercase only and hyphens. Names like claude-plugins-official are reserved and will be blocked by the system. use AI to explain

doesn't work for me

Confirming this is resolved for me with the following sequence — sharing in case it helps others, since reinstalling only from the GitHub side did not work for me on its own:

1. Go to https://claude.ai/settings/connectors and disconnect the GitHub integration.
2. Go to https://github.com/settings/installations and uninstall the Claude GitHub App.
3. Back in https://claude.ai/settings/connectors, reconnect the GitHub integration.
4. Reinstall the Claude GitHub App from GitHub, granting access to the personal repos.

After this, my personal repositories finally appeared in Claude web. Thanks to @mribeiro and @brynary — their suggestion to disconnect from the Claude side was the missing piece; just reinstalling from GitHub alone didn't fix it for me.

This still seems like a bug worth fixing on the backend, since users shouldn't need to perform a four-step dance across both platforms to get personal repos to show up.

Confirming this is resolved for me with the following sequence — sharing in case it helps others, since reinstalling only from the GitHub side did not work for me on its own: 1. Go to https://claude.ai/settings/connectors and disconnect the GitHub integration. 2. Go to https://github.com/settings/installations and uninstall the Claude GitHub App. 3. Back in https://claude.ai/settings/connectors, reconnect the GitHub integration. 4. Reinstall the Claude GitHub App from GitHub, granting access to the personal repos. After this, my personal repositories finally appeared in Claude web. Thanks to @mribeiro and @brynary — their suggestion to disconnect from the Claude side was the missing piece; just reinstalling from GitHub alone didn't fix it for me. This still seems like a bug worth fixing on the backend, since users shouldn't need to perform a four-step dance across both platforms to get personal repos to show up.

I can confirm this works for me as well. Thanks for finding a solution.

Confirming this is resolved for me with the following sequence — sharing in case it helps others, since reinstalling only from the GitHub side did not work for me on its own: 1. Go to https://claude.ai/settings/connectors and disconnect the GitHub integration. 2. Go to https://github.com/settings/installations and uninstall the Claude GitHub App. 3. Back in https://claude.ai/settings/connectors, reconnect the GitHub integration. 4. Reinstall the Claude GitHub App from GitHub, granting access to the personal repos. After this, my personal repositories finally appeared in Claude web. Thanks to @mribeiro and @brynary — their suggestion to disconnect from the Claude side was the missing piece; just reinstalling from GitHub alone didn't fix it for me. This still seems like a bug worth fixing on the backend, since users shouldn't need to perform a four-step dance across both platforms to get personal repos to show up.

This worked for me, thanks! Specifically it seemed disconnecting the connector on the claude side made the difference.

Actually this is security issue with github, as even after I removed a repository for claude he could still access it! until I disconnected him completely. so the refresh issue is very serious.

Fixed for me via https://support.claude.com/en/articles/10167454-using-the-github-integration#h_1844b9b7b5

Connecting to private repositories If Claude cannot access a repository after you enter a valid URL, it most likely means you're attempting to connect Claude to a private repository: Follow the link to our GitHub App, where you can grant access to repos if you're a GitHub administrator, or send a request to your GitHub organization's administrators. Grant access yourself if you can: You can choose between letting Claude access all repos or specific ones. Request access if you don't have the necessary permissions: The administrators of your GitHub organization will receive an email notification about your request. Once they approve the request, you'll be able to sync and access the repository in Claude.

Experiencing the same.

Reinstalled the Claude GitHub App on my organization with "All repositories" selected. Disconnected and reconnected GitHub in claude.ai settings. The web picker simply doesn't show up with any repos.

Can I ask Claude to trigger a backend repository index reset for my GitHub account: @keinsaasforever

How is this still not fixed?

Workaround that worked for me: open the repo once in the Claude mobile app, then refresh the browser.

Same symptom as this thread — on claude.ai/code (web) the "Select repo" picker showed
"No repos match" and my repos never appeared, even though the Claude GitHub App was
installed and the repos were granted.

Things that did not work (so you can skip them):

• Reinstalling / reconfiguring the Claude GitHub App
• Granting under "Only select repositories" and "All repositories"
• Creating a fresh org + repo and installing the app on the org via the claude.ai connect flow
• Removing the org's third-party application access restriction
• Many hard refreshes, logout/login, waiting it out

What did fix it:

1. Open the Claude mobile app (iOS/Android), signed into the same account.
2. Start a session on the repo there — it showed up fine in the app even though the

browser couldn't see it.

1. Back in the browser, refresh claude.ai/code → the repo now appears in the picker,

and repos I add afterwards show up too.

My guess: the mobile app completes a GitHub connection/verification step the web client
doesn't trigger on its own. Can't fully rule out propagation timing, but the mobile
session was the clear turning point — web was empty for a long stretch before, populated
immediately after. (Plan: Max. Repos: private — a personal repo and an org repo, both
became visible after the mobile step.)

My issue was that the Connector was somehow not installed on the Anthropic side despite the App being installed via Claude Code for Web's links on the GitHub side.

This solved my related issue in Claude desktop app for Mac where I only saw in Claude Code my private repos and not public repos (no "org" involved).

Fixed for me via https://support.claude.com/en/articles/10167454-using-the-github-integration#h_1844b9b7b5 > Connecting to private repositories > If Claude cannot access a repository after you enter a valid URL, it most likely means you're attempting to connect Claude to a private repository: > Follow the link to our GitHub App, where you can grant access to repos if you're a GitHub administrator, or send a request to your GitHub organization's administrators. > Grant access yourself if you can: You can choose between letting Claude access all repos or specific ones. > Request access if you don't have the necessary permissions: The administrators of your GitHub organization will receive an email notification about your request. Once they approve the request, you'll be able to sync and access the repository in Claude.

Still had issue.
But solved this way:

1. Disconnected Github from Claude settings at https://claude.ai/customize/connectors
2. Revoked Claude/Antrophic from https://github.com/settings/apps/authorizations
3. Now again https://claude.ai/customize/connectors reconnected github using steps.

Now I can see my private repos!!

For me it was this link that fixed it: https://github.com/apps/claude/installations/select_target
On https://claude.ai/customize/connectors it was connected already.

Please trigger a backend repository index reset for my GitHub account: hamzaomair07-netizen

For me it was this link that fixed it: https://github.com/apps/claude/installations/select_target On https://claude.ai/customize/connectors it was connected already.

This forced the approval workflow to give Claude access to my repositories... but then gave me an error on Claude's side:

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

<img width="1464" height="766" alt="Image" src="https://github.com/user-attachments/assets/e7ca60e9-6128-4932-83bb-54661282bd81" />