Plugin settings can now carry over to a new name

Claude Code can now move a plugin's saved settings and secrets to a new name instead of deleting them

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

PluginsArea: what it touches

ImprovementsKind: in v2.1.321, 09 Nov 26

ImprovementsSection of the release

Unclear It is not known when Claude Code moves the settings rather than deleting them.

What

When 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.

Why

Your plugin settings may survive when a plugin is renamed.

Read from

Names in the bundlepluginConfigs

How sure we are

Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.

The writer flagged doubtIt is not known when Claude Code moves the settings rather than deleting them.

Anthropic's release notes agree[VSCode] Fixed a plugin's permission request showing a name with hidden characters: it now reads "a plugin"

See this entry in the whole of v2.1.321 →

The build it came inv2.1.321

9 Nov 2026 · 418 entries, this one is #104.

Use it now28
You'll notice241
Nothing to try yet17
Under the hood132

Either side of it

v2.1.319Older
v2.1.322Newer

Open the release →

Names in this entry

settingpluginConfigs
Store the answers you gave a plugin's configuration dialog

Anthropic's note

Upstream's own release notes for v2.1.321 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

[VSCode] Fixed a plugin's permission request showing a name with hidden characters: it now reads "a plugin"

Is this right?