{"version":"2.1.321","anchor":"plugin-deletion-can-migrate-pluginconfigs-to-a-new-key","canonical_anchor":"plugin-deletion-can-migrate-pluginconfigs-to-a-new-key","heading":"Plugin settings can now carry over to a new name","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/plugin-deletion-can-migrate-pluginconfigs-to-a-new-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Plugin settings can now carry over to a new name\n\nClaude Code can now move a plugin's saved settings and secrets to a new name instead of deleting them\n\n**Unclear.** It is not known when Claude Code moves the settings rather than deleting them.\n\n**What**\n\nWhen Claude Code clears a plugin's options, it can now move them to a different name instead of deleting them. This covers the plugin's saved `pluginConfigs`, the answers you gave its configuration dialog, and its secrets. Before, these were always deleted. The check that looks for leftover settings belonging to no plugin now skips some names.\n\n**Why**\n\nYour plugin settings may survive when a plugin is renamed.\n\n- Area: Plugins\n- Names: `pluginConfigs`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}