{"version":"2.1.321","anchor":"new-claude-plugin-restore-set-aside-command-with-disca","canonical_anchor":"new-claude-plugin-restore-set-aside-command-with-disca","heading":"New command recovers or deletes plugin data set aside after a marketplace swap","tier":"use","area":"Plugins","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/new-claude-plugin-restore-set-aside-command-with-disca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### New command recovers or deletes plugin data set aside after a marketplace swap\n\n`claude plugin restore-set-aside ` gives set-aside plugin options and secrets to the current plugin, or deletes them with `--discard`\n\n**What**\n\nPlugins are add-ons that extend Claude Code. They come from a marketplace, which is a named catalogue of plugins. Your organization can declare a marketplace that replaces another one with the same name. When that happens, Claude Code now sets aside the old plugin's saved options and secrets. They no longer pass automatically to whatever plugin now uses that plugin id.\n\n- `claude plugin list` prints a note when data has been set aside.\n\n- `claude plugin restore-set-aside <plugin>` gives the set-aside options and secrets to the plugin that now holds that id.\n\n- `claude plugin restore-set-aside <plugin> --discard` deletes them instead of restoring them.\n\nOther data saved by the old source's plugins is moved elsewhere. Claude Code deletes it after the period set by `cleanupPeriodDays`, the setting that controls how many days Claude Code keeps data before removing it.\n\n**Why**\n\nThis prevents a plugin from a replacement marketplace from reading secrets that belonged to the plugin it replaced. You also get a clear way to recover that data or delete it.\n\n- Area: Plugins\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}