{"version":"2.1.296","anchor":"plugin-secrets-and-options-handling-changed","canonical_anchor":"plugin-secrets-and-options-handling-changed","heading":"Plugin option and saved-secret clean-up logic reworked","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/plugin-secrets-and-options-handling-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Plugin option and saved-secret clean-up logic reworked\n\nClaude Code changed how it looks up plugin options and which saved plugin secrets it keeps when it tidies them up\n\n**Unclear.** It is not clear whether this changes which saved plugin secrets are removed or whether the two changes cancel each other out.\n\n**What**\n\nPlugins can have options, which are settings you fill in for them, and some of those options are secrets such as tokens. Claude Code now looks up a plugin's options through a shared helper instead of reading them directly.\n\nThe step that clears out saved plugin secrets (`pluginSecrets`) has also changed. The test that decides which secrets to drop was reversed, and the routine that applies it was replaced.\n\n**Why**\n\nIf the old and new routines treat that test the same way, the reversal changes which saved plugin secrets are removed. If they do not, the two changes cancel out and nothing changes in practice.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}