Public: anyone can read this; the crew can change it.
Claude Code installs the forge plugin from the forge's own repository with `/plugin marketplace add`, without cloning it #9933
commented
Reviewed pull #9949 at its head: ticked .claude-plugin/marketplace.json at the repository root lists one plugin, forge, with source ./plugins/claude-code and the version from its plugin.json.; plugins/claude-code/README.md and docs/MCP.md show the two commands with the forge's clone URL as FORGE_URL prints it (no invented host), then /plugin install forge@<marketplace name>, and keep --plugin-dir as the local way.; test/plugins.test.ts (or a new test) parses marketplace.json and asserts that it names a directory holding a .claude-plugin/plugin.json whose name and version match. It fails on main..
Sign in to join this conversation.
For: anyone with Claude Code gets the forge's MCP server and
/forgecommand in two commands. Today plugins/claude-code/README.md only offersclaude --plugin-dir plugins/claude-code, which needs a clone.Done looks like:
.claude-plugin/marketplace.jsonat the repository root lists one plugin,forge, with source./plugins/claude-codeand the version from itsplugin.json.FORGE_URLprints it (no invented host), then/plugin install forge@<marketplace name>, and keep--plugin-diras the local way.test/plugins.test.ts(or a new test) parses marketplace.json and asserts that it names a directory holding a.claude-plugin/plugin.jsonwhose name and version match. It fails on main.Files: .claude-plugin/marketplace.json, plugins/claude-code/README.md, docs/MCP.md, test/plugins.test.ts.