Repository marketplace resolution ignores .zcode-plugin/marketplace.json and picks .claude-plugin/marketplace.json first
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Read apps/zcode-cli/packages/adapters/src/plugins/marketplace.ts, especially findMarketplaceManifestPath and the candidate order in findPluginManifestPath. Add the ZCode marketplace manifest to lookup in the order described in the issue, then check the repository’s marketplace lookup tests. Done means a repository with both ZCode and Claude manifests resolves the ZCode manifest, while one with only the Claude manifest still resolves it.
Written by the indexing model from the issue text.
Description
问题 / Problem
如果一个仓库同时为多个 Agent 提供插件,zcode plugins marketplace add <owner>/<repo>(或 Git URL)总会读到 Claude Code 的清单。ZCode 用户装上的就是 Claude Code 的插件包,而不是 ZCode 的。
When one repository ships plugins for several agents, zcode plugins marketplace add <owner>/<repo> (or a Git URL) always reads the Claude Code marketplace manifest. ZCode then installs the Claude Code bundle, not the ZCode one.
原因 / Cause
ZCode v3.18.2 (fec97590), apps/zcode-cli/packages/adapters/src/plugins/marketplace.ts:
function findMarketplaceManifestPath(rootPath: string, explicitPath?: string): string | null {
const candidates = [
...(explicitPath ? [explicitPath] : []),
CLAUDE_MARKETPLACE_FILE, // .claude-plugin/marketplace.json
MARKETPLACE_FILE, // marketplace.json
];
插件清单的查找会先找 ZCode 自己的文件(findPluginManifestPath:.zcode-plugin/plugin.json → .claude-plugin/plugin.json → .codex-plugin/plugin.json),但市场清单的候选里没有 .zcode-plugin/marketplace.json。marketplace add 也没有参数能指定读哪个清单文件:--sparse 只决定检出哪些文件,source.path 也不会从命令行输入里填。
Plugin manifest lookup prefers ZCode's own file (.zcode-plugin/plugin.json first), but marketplace lookup has no .zcode-plugin/marketplace.json candidate. marketplace add also cannot point at another manifest: --sparse only limits the checkout, and source.path is never filled from the CLI input.
复现 / Reproduce
zcode plugins marketplace add EvoMap/evolver-agent-plugin --json
# registers "evolver-agent-plugin" from .claude-plugin/marketplace.json, which lists the Claude Code bundle (dist/claude-code)
该仓库为 Claude Code、Codex、Grok、Qoder、Cursor、WorkBuddy 等 Agent 各提供一份带命名空间的清单,现在也加了 .zcode-plugin/marketplace.json。
The repository has a namespaced manifest per agent (.claude-plugin/, .agents/plugins/, .grok-plugin/, .qoder-plugin/, .cursor-plugin/, .codebuddy-plugin/), and now .zcode-plugin/marketplace.json.
建议 / Proposal
在 findMarketplaceManifestPath 中把 .zcode-plugin/marketplace.json 放在第一位,与插件清单的查找顺序保持一致:
Put .zcode-plugin/marketplace.json first, matching the plugin-manifest order:
const ZCODE_MARKETPLACE_FILE = join(".zcode-plugin", "marketplace.json");
const candidates = [
...(explicitPath ? [explicitPath] : []),
ZCODE_MARKETPLACE_FILE,
CLAUDE_MARKETPLACE_FILE,
MARKETPLACE_FILE,
];
只放一份 .claude-plugin/marketplace.json 的仓库,行为不受影响。
Repositories with only .claude-plugin/marketplace.json behave as before.
目前的绕行方式 / Current workaround
通过原始 URL 登记 ZCode 专用清单(URL 来源会直接读取该文件),它的条目用 git-subdir 来源指向 dist/zcode。已在 ZCode 3.18.2 / CLI 0.17.1 上验证:
Register the ZCode-only manifest by its raw URL; a URL source reads that file directly, and its entry uses a git-subdir source for dist/zcode. Verified on ZCode 3.18.2 / CLI 0.17.1:
zcode plugins marketplace add https://raw.githubusercontent.com/EvoMap/evolver-agent-plugin/main/.zcode-plugin/marketplace.json
zcode plugins install evolver-plugin@evomap --scope user
上面的改动合入后,直接执行 marketplace add EvoMap/evolver-agent-plugin 就能正常工作。
With the change above, plain marketplace add EvoMap/evolver-agent-plugin would work directly.
- Dominant language
- Python
- Stars
- 152
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from zai-org/zcode-plugins
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
zai-org/zcode-plugins#107 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
zai-org/zcode-plugins#106 ·
Maintainers usually reply within 1 day
-
video-agent-kit (0.4.3): hooks invoke python3, which doesn't exist on Windows — SessionStart/UserPromptSubmit/Stop hooks fail on every triggerPossibly taken @dvd233 claimed this 57 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
zai-org/zcode-plugins#14 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
zai-org/zcode-plugins#194 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
zai-org/zcode-plugins#193 · 2 comments ·
Maintainers usually reply within 1 day
All issues in zai-org/zcode-plugins
Similar issues
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·
-
Internal ErrorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
frappe/frappe_docker#2071 ·
Maintainers usually reply within 1 day
-
bug python
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
traceloop/openllmetry#4717 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
The-Pocket/PocketFlow#161 ·
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day