{"version":"2.1.281","anchor":"uninstalling-a-plugin-now-verifies-its-stored-options-and-se","canonical_anchor":"uninstalling-a-plugin-now-verifies-its-stored-options-and-se","heading":"Uninstalling a plugin now verifies its stored options and secrets are gone","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/uninstalling-a-plugin-now-verifies-its-stored-options-and-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Uninstalling a plugin now verifies its stored options and secrets are gone\n\nDeleting a plugin's saved options now checks that its settings and secrets are really gone, and reports what failed\n\n**What**\n\nWhen a plugin's stored options are deleted, Claude Code now checks afterwards that the deletion worked. It clears `pluginConfigs` (the answers you gave a plugin's configuration dialog) from your user settings. It also clears `pluginSecrets` from secure storage, the protected place where secrets such as keys are kept. Then it reads both back. If something went wrong, it reports one of these reasons:\n\n- `settings_unreadable`\n\n- `settings_write_failed`\n\n- `secrets_write_failed`\n\n- `secrets_unreadable`\n\n- `secrets_remain`\n\n**Why**\n\nBefore, a failed cleanup could pass silently and leave a removed plugin's settings or secrets on your machine. Now a failure is named, so you learn when something may still be stored."}