What
When a plugin marketplace no longer sits where Claude Code recorded it, the refusal now explains the problem and the two ways out: re-add the marketplace, or, if it genuinely lives on a network path, declare it under extraKnownMarketplaces in your user or managed settings. The old text just pointed at /feedback.
Details
- Always on; this is the error path itself, not a gated feature.
Evidence
extraKnownMarketplaces in user or managed settings
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleextraKnownMarketplaces
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.
Confirmed since
Anthropic's documentation has since written up extraKnownMarketplaces, on Configure permissions.
| Frontmatter hooks in a project [subagent](/docs/en/sub-agents#hooks-in-subagent-frontmatter), a project [`@skills-dir` plugin](/docs/en/plugins/loading#plugins-shared-through-a-repository), and [`extraKnownMarketplaces`](/docs/en/setting…permissions see the edit
Added since
A small documentation edit on Configure cloud environments touched a line naming extraKnownMarketplaces after this was published.
| Plugins and marketplaces declared in your repo's `.claude/settings.json` | No | A cloud session doesn't install the plugins a repository turns on under [`enabledPlugins`](/docs/en/settings-reference#enabledplugins), including ones from t…cloud-environments see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Configure cloud environments touched a line naming extraKnownMarketplaces after this was published.