Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.247entry #73

Claude Code v2.1.247 ·

claude plugin enable/disable refuses an ambiguous bare name

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

Use it now Improvements
JSON All of v2.1.247
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.247,
What probably matters to youSection of the release
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.

Read from
Names in the bundleclaude plugin enableclaude plugin disable
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up claude plugin disable, on Plugins reference. * **Turn one off**: in the synced session, run `claude plugin disable <name>@synced`, or ask Claude to run it. Claude Code saves the choice as `"<name>@synced": false` in that environment's user-level [`enabledPlugins`](/docs/en/settings-r… plugins-reference see the edit
Confirmed since Anthropic's documentation has since written up claude plugin enable, on Plugins reference. * **Turn one off**: in the synced session, run `claude plugin disable <name>@synced`, or ask Claude to run it. Claude Code saves the choice as `"<name>@synced": false` in that environment's user-level [`enabledPlugins`](/docs/en/settings-r… plugins-reference see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude plugin enable, on Plugins reference.
Anthropic's release notes agreeImproved plugin marketplace hardening: names containing control or invisible characters are rejected, and marketplace-supplied text in…

See this entry in the whole of v2.1.247 →

Feedback