{"version":"2.1.285","anchor":"plugin-names-alias-across-marketplace-name-variants","canonical_anchor":"plugin-names-alias-across-marketplace-name-variants","heading":"Built-in plugins renamed, with old and new names treated as the same plugin","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/plugin-names-alias-across-marketplace-name-variants","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Built-in plugins renamed, with old and new names treated as the same plugin\n\nBuilt-in plugins gain cc-plugin-* names, and enabledPlugins lookups and writes now treat old and new spellings as one plugin\n\n**Unclear.** Which names count as aliases of which marketplace is not spelled out.\n\n**What**\n\nPlugins 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`.\n\nTo keep existing settings working:\n\n- 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.\n\n- Checks for duplicate plugin names also treat the old and new spellings as the same plugin.\n\n- Writing `enabledPlugins` replaces older spellings of a plugin id instead of adding a second entry.\n\n- The documentation says to keep listing the security plugin as `sec-default@builtin` for older releases.\n\n**Why**\n\nThe 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`.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}