Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS + FEATURE] Cross-marketplace plugin dependencies: docs cite an allowlist but never define it [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#49620•Fetched 2026-04-17 08:36:01
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
chrisvaillancourtchrisvaillancourt
Participants
chrisvaillancourtchrisvaillancourtgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

plugin.json dependencies can include a marketplace field to reference a plugin in another marketplace. The docs say an allowlist gates this feature but never document it. Users cannot declare cross-marketplace dependencies.

Root Cause

plugin.json dependencies can include a marketplace field to reference a plugin in another marketplace. The docs say an allowlist gates this feature but never document it. Users cannot declare cross-marketplace dependencies.

Fix Action

Fix / Workaround

Workaround: I copied the agent files verbatim under Apache-2.0 attribution, with per-file blob-SHA tracking and drift-detection tooling. A usable marketplace field would eliminate this overhead.

RAW_BUFFERClick to expand / collapse

Summary

plugin.json dependencies can include a marketplace field to reference a plugin in another marketplace. The docs say an allowlist gates this feature but never document it. Users cannot declare cross-marketplace dependencies.

The documentation gap

From plugin-dependencies.md, the marketplace field reads:

A different marketplace to resolve name in. Cross-marketplace dependencies are blocked unless the target marketplace is allowlisted in the root marketplace's marketplace.json.

Neither plugin-marketplaces.md nor the plugins reference specifies:

  • The allowlist's JSON field name in marketplace.json
  • The allowlist entry schema (bare name? owner/repo? source object?)
  • A worked example
  • Whether the mechanism is implemented, stubbed, or admin-only

strictKnownMarketplaces is managed-settings-only and controls which marketplaces users can add — unrelated to dependency resolution.

Real-world impact

I maintain a private curated marketplace. One of its embedded plugins needed to extend agents from pr-review-toolkit in anthropics/claude-plugins-official. Declaring {"name": "pr-review-toolkit"} failed with pr-review-toolkit@<my-marketplace> not installed — the resolver scoped to my own marketplace. I found no documented way to declare a cross-marketplace dependency.

Workaround: I copied the agent files verbatim under Apache-2.0 attribution, with per-file blob-SHA tracking and drift-detection tooling. A usable marketplace field would eliminate this overhead.

Requested resolution

One or both of:

  1. DOCS: Specify the allowlist's field name, schema, and an example on plugin-marketplaces.md, linked from plugin-dependencies.md.
  2. FEATURE: If the allowlist is not production-ready, add a requiredMarketplaces field to marketplace.json that prompts users to add any missing companion marketplace at install time.

Related

  • #26122 — Cross-marketplace plugin references (stale-closed with no Anthropic engagement)
  • #48864 — [DOCS] Plugin docs missing plugin.json dependency declarations and auto-install behavior
  • #49311 — [DOCS] Plugins reference missing dependency version requirement and recovery docs

extent analysis

TL;DR

To resolve cross-marketplace plugin dependencies, the marketplace.json file needs to be updated with a clear allowlist configuration, which is currently undocumented.

Guidance

  • Review the plugin-dependencies.md and plugin-marketplaces.md documentation to understand the current state of cross-marketplace dependencies.
  • Consider adding a requiredMarketplaces field to marketplace.json to prompt users to add missing companion marketplaces at install time.
  • Verify that the strictKnownMarketplaces setting is not interfering with dependency resolution, as it controls which marketplaces users can add.
  • Check the related issues (#26122, #48864, #49311) for potential insights into the problem and possible solutions.

Example

No code snippet is provided as the issue is primarily related to documentation and configuration.

Notes

The current documentation gap makes it difficult to provide a definitive solution. The allowlist configuration and schema are unknown, and the marketplace field is not fully documented.

Recommendation

Apply a workaround by manually configuring the marketplace.json file or using the proposed requiredMarketplaces field, as the feature is not fully implemented or documented. This will help mitigate the issue until the documentation and feature are updated.

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…
#memory optimization#batch processing#GPU compatibility#latency issue#model 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 + FEATURE] Cross-marketplace plugin dependencies: docs cite an allowlist but never define it [1 comments, 2 participants]