{"version":"2.1.247","anchor":"claude-plugin-enable-disable-refuses-an-ambiguous-bare-name","canonical_anchor":"claude-plugin-enable-disable-refuses-an-ambiguous-bare-name","heading":"claude plugin enable\/disable refuses an ambiguous bare name","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/claude-plugin-enable-disable-refuses-an-ambiguous-bare-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### `claude plugin enable\/disable` refuses an ambiguous bare name\n\nEnabling or disabling an ambiguous plugin name now stops and asks you to write plugin@marketplace.\n\n**What**\n\nIf you pass a plain plugin name that matches both a built-in plugin and a different loaded plugin with the same name, the command now stops and tells you to disambiguate with `plugin@marketplace` instead of quietly picking one.\n\n**Details**\n\n- The built-in candidate is resolved first; the clash triggers whether the same-named loaded plugin is currently enabled or disabled.\n- The disable command's check for other plugins that depend on the one you are disabling was narrowed: unless a build check passes, plugins from the synced marketplace are left out of that dependent set. That build check could not be tied to a named flag.\n- Dependent plugins are now listed by their display names rather than raw internal ids.\n\n**Usage**\n\n`claude plugin disable my-plugin@my-marketplace` **Evidence** `names both a built-in and another loaded plugin. Use plugin@marketplace format.`\n\n- Area: Plugins\n- Names: `claude plugin enable`, `claude plugin disable`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}