{"version":"2.1.282","anchor":"plugin-uninstall-refuses-while-a-settings-file-still-enables","canonical_anchor":"plugin-uninstall-refuses-while-a-settings-file-still-enables","heading":"Plugin uninstall now stops if a settings file still switches the plugin on","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/plugin-uninstall-refuses-while-a-settings-file-still-enables","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Plugin uninstall now stops if a settings file still switches the plugin on\n\nUninstalling a plugin now fails with a clear message if a settings file still turns it on or cannot be checked\n\n**What**\n\nWhen 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:\n\n- the plugin still reads as switched on in a settings file\n\n- a settings file could not be read\n\n- a settings file sits on a network path that Claude Code does not read\n\nThe 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.\n\nThe failed-plugin details screen in `\/plugin` and the automatic removal of plugins taken off a marketplace skip this check.\n\n**Why**\n\nBefore, 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.\n\n- Area: Plugins\n- Names: `enabledPlugins`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}