What
A marketplace entry that installs a plugin by running a command on your machine can now use mode: "link", where the directory the command produces is symlinked in place instead of copied. Link mode is refused on Windows. If the marketplace's command changed since you accepted it, the refusal now says specifically what changed, and the /plugin details pane shows the command and its mode.
Details
- the install record keeps the path the command produced and the paths previous runs produced, so a changed producer path is detectable
- consent is tied to the exact command text you approved
Evidence
Installed by running a command on this machine:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/plugin
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Create and distribute a plugin marketplace touched a line naming /plugin after this was published.
Paths resolve relative to the marketplace root, which is the directory containing `.claude-plugin/`. In the example above, `./plugins/my-plugin` points to `<repo>/plugins/my-plugin`, even though `marketplace.json` lives at `<repo>/.claude-…plugin-marketplaces see the edit
Confirmed since
Anthropic's documentation has since written up /plugin, on MCP, plugins, skills, and hooks.
| `.claude-plugin/plugin.json` | **Required.** Plugin manifest (name, description, version). Directories without this file are ignored. |third-party/claude-desktop/extensions see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /plugin, on MCP, plugins, skills, and hooks.
Anthropic's release notes agree
Added plugin marketplace command sources: a local command (e.g. an IDE) prints the plugin directory, which is re-resolved each session and…