claude-code - 💡(How to fix) Fix [DOCS] Plugin marketplace docs missing unrecognized source format behavior [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#53076Fetched 2026-04-25 06:12:59
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

Error Message

  • If the error says the plugin uses an unrecognized source format, update Claude Code and run /plugin marketplace update <marketplace-name> before retrying the install.
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/plugin-marketplaces#plugin-sources

Section/Topic

Plugin sources, marketplace validation/troubleshooting, and plugin installation failure behavior for plugin entries that use an unrecognized source.source format.

Current Documentation

The marketplace guide documents the currently supported plugin source types:

Plugin sources tell Claude Code where to fetch each individual plugin listed in your marketplace. These are set in the source field of each plugin entry in marketplace.json.

| Source | Type | Fields | Notes | | Relative path | string (e.g. "./my-plugin") | none | Local directory within the marketplace repo. Must start with ./. Resolved relative to the marketplace root, not the .claude-plugin/ directory | | github | object | repo, ref?, sha? | | | url | object | url, ref?, sha? | Git URL source | | git-subdir | object | url, path, ref?, sha? | Subdirectory within a git repo. Clones sparsely to minimize bandwidth for monorepos | | npm | object | package, version?, registry? | Installed via npm install |

The troubleshooting section covers generic marketplace and install failures:

Marketplace not loading

Symptoms: Can't add marketplace or see plugins from it

Solutions:

  • Verify the marketplace URL is accessible
  • Check that .claude-plugin/marketplace.json exists at the specified path
  • Ensure JSON syntax is valid and frontmatter is well-formed using claude plugin validate or /plugin validate
  • For private repositories, confirm you have access permissions

And:

Plugin installation failures

Symptoms: Marketplace appears but plugin installation fails

Solutions:

  • Verify plugin source URLs are accessible
  • Check that plugin directories contain required files
  • For GitHub sources, ensure repositories are public or you have access
  • Test plugin sources manually by cloning/downloading

What's Wrong or Missing?

Changelog v2.1.120 says Claude Code fixed /plugin marketplace loading when one marketplace entry uses an unrecognized source format: the marketplace entry is now shown, and attempting to install that plugin prompts the user to update.

The current docs list supported source formats, but they do not explain what happens when a marketplace contains a newer or otherwise unrecognized source format. That leaves two user groups without guidance:

A. Marketplace users cannot tell that a marketplace may still load even when one plugin entry cannot be installed by their current Claude Code version.

B. Marketplace authors cannot tell that an unrecognized source format should degrade at install time for that entry instead of making the whole marketplace unavailable.

The existing troubleshooting advice points users toward URL accessibility, JSON syntax, repository access, or manual cloning. Those checks do not fit the v2.1.120 compatibility case, where the catalog can be valid and accessible but one entry requires a newer Claude Code version that understands its source format.

Suggested Improvement

Add a short compatibility note under Plugin sources or Troubleshooting that explains unsupported source formats.

Suggested wording:

Unsupported source formats: If a marketplace contains a plugin entry whose source.source value is not recognized by your installed Claude Code version, the marketplace can still load and display the entry. Installing that plugin fails with guidance to update Claude Code. Update Claude Code, refresh the marketplace, then retry the install.

Also update the Plugin installation failures troubleshooting list with a bullet such as:

  • If the error says the plugin uses an unrecognized source format, update Claude Code and run /plugin marketplace update <marketplace-name> before retrying the install.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/plugin-marketplaces#plugin-sources222-234Lists supported plugin source formats but does not document unrecognized/future source format handling.
https://code.claude.com/docs/en/plugin-marketplaces#marketplace-not-loading934-943Marketplace troubleshooting does not distinguish whole-marketplace load failures from one unsupported plugin entry.
https://code.claude.com/docs/en/plugin-marketplaces#plugin-installation-failures964-973Plugin install troubleshooting omits the update-Claude-Code recovery path for unrecognized source formats.
https://code.claude.com/docs/en/discover-plugins#install-plugins246-264User-facing install flow does not mention that a visible marketplace entry can still require a newer client source parser.
https://code.claude.com/docs/en/discover-plugins#common-issues416-423Common plugin issues point to generic marketplace loading and source URL checks, not source-format compatibility.

Total scope: 5 page sections affected across 2 pages.

Source: Changelog v2.1.120: Fixed /plugin marketplace failing to load when one entry uses an unrecognized source format — that entry is shown but installing it prompts you to update

extent analysis

TL;DR

Add documentation for handling unsupported plugin source formats to the Plugin sources and Troubleshooting sections.

Guidance

  • Update the Plugin sources section to include a note about unsupported source formats, such as: "If a marketplace contains a plugin entry whose source.source value is not recognized by your installed Claude Code version, the marketplace can still load and display the entry. Installing that plugin fails with guidance to update Claude Code."
  • Add a bullet point to the Plugin installation failures troubleshooting list, such as: "If the error says the plugin uses an unrecognized source format, update Claude Code and run /plugin marketplace update <marketplace-name> before retrying the install."
  • Review the affected pages (listed in the Additional Context section) to ensure consistency in documenting unsupported source format handling.
  • Consider adding a note to the user-facing install flow (e.g., https://code.claude.com/docs/en/discover-plugins#install-plugins) to mention that a visible marketplace entry can still require a newer client source parser.

Example

No code snippet is necessary for this documentation update.

Notes

The suggested improvement aims to address the lack of guidance for users when encountering unsupported plugin source formats. By adding clear documentation, users can better understand the behavior and take appropriate actions to resolve issues.

Recommendation

Apply the suggested documentation updates to improve user understanding and troubleshooting of unsupported plugin source formats. This change will help users navigate compatibility issues and provide a better experience when working with marketplaces and plugins.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] Plugin marketplace docs missing unrecognized source format behavior [1 comments, 2 participants]