Desktop Plugins panel cannot browse git marketplaces (regression)
Desktop Plugins panel cannot browse git marketplaces (regression)
Version: Claude Code 2.1.79 · Claude desktop app, Code tab · Windows 11
Summary
The desktop Plugins panel has no way to browse or install plugins from a git-based
marketplace. Discover → Filter → Source offers only All sources, Anthropic,
and Your organization — a configured git marketplace is not a selectable source, and
its uninstalled plugins never appear anywhere in the panel.
The panel's Add ⌄ menu does offer Add marketplace, so a git marketplace can be
registered through the UI but not browsed through it. That combination is the core
of the bug: the UI invites you to add a source it can't then read.
This previously worked — available plugins from a git marketplace were visible in the UI.
Repro
- Configure a git marketplace (
~/.claude/settings.json→extraKnownMarketplaces,
or the panel's Add ⌄ → Add marketplace):
``json``
"prolink": {
"source": { "source": "git", "url": "https://github.com/ORG/REPO.git" }
}
- Ensure the marketplace catalog contains at least one plugin that is not installed.
- Open Settings → Plugins →
Discover. - Try
Filter→Source. OnlyAll sources/Anthropic/Your organizationexist. - The uninstalled git-marketplace plugin appears under neither
Discovernor
Your plugins, and the search box does not find it.
Expected
Git marketplaces should be a selectable Source, and their uninstalled plugins should be
browsable and installable from Discover — matching what the CLI already returns.
Actual
Git-marketplace plugins are invisible in the panel until installed by CLI. After a CLI
install they show up under Your plugins, so the panel can render them; it just won't
offer them.
The CLI has the data
claude plugin list --available --json
...correctly returns the uninstalled plugin in its available array with the rightmarketplaceName. So this is a UI gap, not a catalog or config problem.
Workaround
claude plugin marketplace update <marketplace-name>
claude plugin install <plugin-name>@<marketplace-name>
Note that claude plugin install <plugin>@<marketplace> fails withPlugin "<plugin>" not found in marketplace "<marketplace>" if the marketplace clone is
stale — the documented pre-install refresh did not happen here, somarketplace update was required first. That may be a second, separate bug.