{"version":"2.1.287","anchor":"marketplace-add-refuses-name-collisions-with-extraknownmarke","canonical_anchor":"marketplace-add-refuses-name-collisions-with-extraknownmarke","heading":"Adding a marketplace can be refused when it clashes with one in your settings","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/marketplace-add-refuses-name-collisions-with-extraknownmarke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Adding a marketplace can be refused when it clashes with one in your settings\n\nA marketplace add can now be refused if its name or clone folder matches one in `extraKnownMarketplaces` with a different source\n\n**Unclear.** It is not clear which ways of adding a marketplace turn the name-clash check on.\n\n**What**\n\nA marketplace is a catalog Claude Code installs plugins from. When the name-clash check is turned on for an add, Claude Code refuses to add a marketplace if either of these matches a marketplace declared under `extraKnownMarketplaces` in your settings that comes from a different source:\n\n- its name\n\n- the folder its GitHub copy would be cloned into\n\nBefore, names were only checked against marketplaces already added.\n\nMany marketplace errors now also carry a short failure code, such as `source_blocked_by_policy`, `manifest_invalid` or `invalid_source`.\n\n**Why**\n\nA marketplace declared in your settings can no longer be overwritten by adding a different one with the same name.\n\n- Area: Plugins\n- Names: `extraKnownMarketplaces`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}