Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Built-in plugins renamed, with old and new names treated as the same plugin

Built-in plugins gain cc-plugin-* names, and enabledPlugins lookups and writes now treat old and new spellings as one plugin

Group of 2 You'll notice Improvements
JSON All of v2.1.285
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.285,
ImprovementsSection of the release

What

Plugins add features to Claude Code, and the enabledPlugins setting turns them on or off. Some built-in plugins now have new names starting with cc-plugin-, such as cc-plugin-responsive-mode. The bundled security plugin is now cc-plugin-sec-default@builtin.

To keep existing settings working:

  • Looking up, enabling or disabling a plugin now matches every spelling of a built-in plugin's name. Before, only an exact name match counted.
  • Checks for duplicate plugin names also treat the old and new spellings as the same plugin.
  • Writing enabledPlugins replaces older spellings of a plugin id instead of adding a second entry.
  • The documentation says to keep listing the security plugin as sec-default@builtin for older releases.

Why

The rename should not leave you with the same plugin listed twice, or with a plugin switched off because your settings still use its old name. Administrators who order hooks in managed settings should know that the bundled security plugin now goes by cc-plugin-sec-default@builtin.

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 doubtWhich names count as aliases of which marketplace is not spelled out.

See this entry in the whole of v2.1.285 →

Feedback