A misplaced marketplace now tells you to re-add it or declare it under extraKnownMarketplaces.
What's wrong with this entry?
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.
- Always on; this is the error path itself, not a gated feature.
extraKnownMarketplaces in user or managed settings
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Invalid
extraKnownMarketplacesentries are dropped with a warningBoth mention extra known marketplace
-
v2.1.228
extraKnownMarketplaces merges instead of being replaced
Both mention extra known marketplace
-
v2.1.232
additionalMarketplacessettings aliasBoth mention extra known marketplace