{"version":"2.1.287","anchor":"plugin-option-deletion-verifies-settings-read-back","canonical_anchor":"plugin-option-deletion-verifies-settings-read-back","heading":"Removing a plugin's saved options now checks they were really removed","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-option-deletion-verifies-settings-read-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Removing a plugin's saved options now checks they were really removed\n\nWhen Claude Code deletes a plugin's saved options, it now reads settings back and reports it if they are unreadable or still there\n\n**What**\n\n`pluginConfigs` stores the answers you gave a plugin's configuration dialog. When Claude Code deletes those answers, it now reads your settings back afterwards and reports a problem in either case:\n\n- the settings cannot be read\n\n- the plugin's options are still there after a save that reported no error\n\n**Why**\n\nRemoving a plugin is less likely to leave its configuration behind without telling you.\n\n- Area: Plugins\n- Names: `pluginConfigs`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}