You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release
What
When you uninstall a plugin, Claude Code removes it from the enabledPlugins list in your settings. A plugin is an add-on that gives Claude Code extra commands or tools, and enabledPlugins is the settings entry that turns each one on or off. Claude Code now reads the settings back afterwards to check. The uninstall is refused, and names the file, when:
the plugin still reads as switched on in a settings file
a settings file could not be read
a settings file sits on a network path that Claude Code does not read
The message tells you to take the plugin out of enabledPlugins in that file yourself and then uninstall again. If an older local settings file is not valid JSON, the uninstall goes ahead with a note instead. The success message can also explain that saved options, secrets or data were kept.
The failed-plugin details screen in /plugin and the automatic removal of plugins taken off a marketplace skip this check.
Why
Before, a plugin could look uninstalled while another settings file kept switching it back on. Now you get a clear failure that tells you which file to fix.
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 sinceAnthropic's documentation has since written up enabledPlugins, on Claude Code changelog.* Fixed `claude plugin uninstall` removing the other of two installed plugins whose ids differ only in case, with its options and secrets, when the one named had no `enabledPlugins` entry at that scopechangelogsee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up enabledPlugins, on Claude Code changelog.
