{"version":"2.1.292","anchor":"plugin-uninstall-scan-handles-network-paths-and-de-duplicate","canonical_anchor":"plugin-uninstall-scan-handles-network-paths-and-de-duplicate","heading":"Plugin uninstall checks settings files earlier and says whether anything changed","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/plugin-uninstall-scan-handles-network-paths-and-de-duplicate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Plugin uninstall checks settings files earlier and says whether anything changed\n\nUninstalling a plugin now checks settings files are readable first, skips network paths, and says clearly whether anything was changed\n\n**What**\n\nWhen you uninstall a plugin, Claude Code edits your settings to remove it from `enabledPlugins`, the setting that turns plugins on or off. That process is now more careful:\n\n- Before editing, it checks that the settings file can be read. If the file is on a network path or cannot be read, uninstall stops with \"Nothing was changed.\" Before, the network-path check ran only after the settings had been written.\n\n- If something fails after the edit, it warns that the plugin may already have been removed from `enabledPlugins`.\n\n- When it looks for other settings files that still turn the plugin on, a file on a network path is reported as not read, with the reason. Files that point to the same place are checked only once. Unreadable settings files are logged as errors.\n\n- Messages for the case where the plugin is still switched on somewhere use more specific wording.\n\n**Why**\n\nYou can now tell from the message whether your settings were touched, and warnings about a plugin still being enabled elsewhere are more accurate.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}