Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

claude plugin enable/disable refuses an ambiguous bare name

Use it now
Useful3 Signal1
Plugins

Enabling or disabling an ambiguous plugin name now stops and asks you to write plugin@marketplace.

claude plugin enableclaude plugin disable
What

If 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.

Details
  • The built-in candidate is resolved first; the clash triggers whether the same-named loaded plugin is currently enabled or disabled.
  • 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.
  • Dependent plugins are now listed by their display names rather than raw internal ids.
Usage
claude plugin disable my-plugin@my-marketplace
Evidence

names both a built-in and another loaded plugin. Use plugin@marketplace format.

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.

See this entry in the whole of v2.1.247 →