{"version":"2.1.275","anchor":"marketplace-add-now-refuses-to-overwrite-an-existing-marketp","canonical_anchor":"marketplace-add-gets-a-stricter-no-replace-safeguard-for-url","heading":"Adding a plugin marketplace no longer silently overwrites an existing one","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/marketplace-add-now-refuses-to-overwrite-an-existing-marketp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Adding a plugin marketplace no longer silently overwrites an existing one\n\nAdding a plugin marketplace by URL now refuses to silently replace an existing marketplace registered under the same name\n\n**What**\n\nWhen you add a plugin marketplace from a `url` source, Claude Code now hardlinks the downloaded catalog into the cache instead of always renaming it, and:\n\n- If a marketplace with that name is already registered from a different source, the add is refused with an error instructing you to run `\/plugin marketplace remove` first.\n\n- If finalizing the cache fails for another reason, a more explicit error is shown, explaining that adding a marketplace will never silently replace an existing one with the same name, and how to recover.\n\n**Why**\n\nThis prevents one marketplace from quietly clobbering another that happens to share a name, which could otherwise replace plugins you already trust without warning.\n\n- Area: Plugins\n- Names: `\/plugin marketplace remove`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}