{"version":"2.1.287","anchor":"plugin-installupdate-now-distinguishes-a-held-plugin-direct","canonical_anchor":"plugin-installupdate-now-distinguishes-a-held-plugin-direct","heading":"Plugin installs now report a clashing plugin folder name with its own error","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-installupdate-now-distinguishes-a-held-plugin-direct","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugin installs now report a clashing plugin folder name with its own error\n\nInstalling or updating a plugin whose folder name is already taken now gives a separate error from a reserved marketplace name clash\n\n**Unclear.** Exactly which clash triggers the new folder-name message has not been confirmed.\n\n**What**\n\nWhen you install or update a plugin and its name clashes with an entry already in the plugin registry (the list of plugins and marketplaces Claude Code knows about), Claude Code now tells two cases apart:\n\n- Plugin folder name already taken: the error reads \"Plugin directory name held by another registry entry\".\n\n- Reserved marketplace name already taken: the existing error about a reserved marketplace name is kept for this case only.\n\nBefore, the reserved marketplace name message covered both.\n\n**Why**\n\nIf you hit a name clash, the message now points at what is actually taken, so it is easier to see what to rename or remove.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}