enabledPlugins
A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.138 and was gone by v2.1.284.
Turn individual plugins on or off per scope
Anthropic's own wording. Read off All settings, captured 2026-10-22.
In the changelogs
33Releases whose published page names enabledPlugins.
-
v2.1.305
Plugin changes are refused when your organisation's managed settings already decide them
Changing a plugin's on or off state now fails with
managed_settings_overridewhen managedenabledPluginssettings already set that pluginfound in this entry's text, named in this entry
-
v2.1.304
Choose which plugins load when Claude Code runs as an MCP server
CLAUDE_CODE_MCP_SERVE_ENABLED_PLUGINSlets a program that launchesclaude mcp servepick which plugins are turned onfound in this entry's text
-
v2.1.302
Plugins disabled by your organization can now be marked as held off
In the organization-managed plugin list, disabled plugins in a held set are now marked with heldOff: true
found in this entry's text, named in this entry
-
v2.1.295
Plugin settings summary now includes a separate seat layer
The summary of plugin and marketplace settings now includes a seat section with its own plugin and marketplace values
found in this entry's text
-
v2.1.295
New check on plugin settings loaded from machine-level files
Claude Code now checks plugin-related settings that come from settings files users cannot write to
found in this entry's text
-
v2.1.292
Plugin uninstall checks your settings first and says whether anything changed
Uninstalling a plugin now checks the settings file can be read before editing it, and its error messages say whether anything was changed
found in this entry's text
-
v2.1.288
Sensitive settings from the launch folder can now be dropped before they apply
Unless a launch-folder policy allows them, settings such as enabledPlugins and modelOverrides from the launch folder are now removed
found in this entry's text
-
v2.1.285
Built-in plugins have new names starting with cc-plugin-
The plugins that ship with Claude Code were renamed with a cc-plugin- prefix, such as agents-md becoming cc-plugin-agents-md
found in this entry's text
-
v2.1.285
Plugins match across alternative names of built-in marketplaces
Finding, enabling and disabling plugins now treats a built-in marketplace's alternative names as the same marketplace
found in this entry's text
-
v2.1.285
Bundled security plugin renamed to cc-plugin-sec-default@builtin
The bundled security plugin is now
cc-plugin-sec-default@builtin, and writingenabledPluginsreplaces other spellings of the same pluginfound in this entry's text
-
v2.1.284
Plugin dependencies named without a marketplace now match your installed plugin
A plugin dependency given by name alone is now satisfied by, and resolves to, the matching enabled plugin from a marketplace
found in this entry's text
-
v2.1.284
Built-in plugins in
enabledPluginsare matched regardless of letter caseAn
enabledPluginsentry for a built-in plugin now takes effect even if its name differs from the plugin's only in upper or lower casefound in this entry's text, named in this entry
-
v2.1.284
Failed plugin installs clean up according to why they failed
When a plugin install fails, Claude Code now undoes only what that failure left behind, and can suggest updating a dependency that is too old
found in this entry's text
-
v2.1.283
Plugin sync leaves the installed plugins file alone when it holds unreadable records
If
installed_plugins.jsonholds records this version cannot read, theenabledPluginssync is skipped and the file is left untouchedfound in this entry's text, named in this entry
-
v2.1.282
Plugin uninstall now stops if a settings file still switches the plugin on
Uninstalling a plugin now fails with a clear message if a settings file still turns it on or cannot be checked
found in this entry's text, named in this entry
-
v2.1.282
Invalid managed settings now fall back to their strict value in one consistent way
Bad values in managed settings now fall back to the strict choice by one shared rule, and one bad
enabledPluginsentry no longer voids the restfound in this entry's text
-
v2.1.281
Plugin uninstall keeps install paths still shared by other plugins
Uninstalling plugins no longer removes install folders or settings entries that other installed plugins still use
found in this entry's text
-
v2.1.277
/plugin uninstall/removal flow now cleans up stray references across all settings scopes
/plugin uninstall now cleans up leftover plugin references across every settings scope, not just one
found in this entry's text
-
v2.1.267
User-writable settings files can no longer set secDefault/prependPlugins/appendPlugins or enable plugins via enabledPlugins
User-writable settings files can no longer set secDefault, prependPlugins, appendPlugins, or enable plugins
found in this entry's text
-
v2.1.261
Marketplace-scoped enabledPlugins now records marketplace explicitly
Policy-configured enabled plugins now track their marketplace explicitly instead of just a name.
found in this entry's text
-
v2.1.248
Two new settings keys named: WSL settings inheritance and managed-source behaviour
Two settings keys are named for WSL inheriting Windows settings and managed-source behaviour.
found in this entry's text
-
v2.1.239
Cloud sessions can be handed forwarded plugin settings
Cloud sessions can accept a pushed plugin configuration, but it stays off without server values.
found in this entry's text
-
v2.1.232
Two new spellings for the marketplace settings keys
You can now write
additionalMarketplacesandallowedMarketplacesas aliases for the older marketplace settings keys.found in this entry's text
-
v2.1.223
Skills discovery skips disabled plugins
Skills belonging to plugins you disabled no longer show up in skill discovery.
named in this entry, found in this entry's text
-
v2.1.222
Resume snapshots carry user settings without plugin keys
Resumed sessions now carry your settings files along, with plugin registrations stripped out.
named in this entry, found in this entry's text
-
v2.1.221
Plugin install now tells you when higher-precedence settings keep it disabled
Plugin install now tells you when a higher-priority settings file is what's keeping the plugin disabled.
named in this entry, found in this entry's text
-
v2.1.221
Batch plugin install distinguishes disabled-by-default from disabled-in-settings
Batch plugin installs now tell you which plugins are off by default versus off in your settings.
found in this entry's text
-
v2.1.193
Plugin Renaming in Marketplace Manifests
found in this entry's text
-
v2.1.133
Better Documentation for Plugin Setting Precedence
found in this entry's text
- v2.1.83
- v2.1.47
-
v2.0.42
Settings Update Error Handling
found in this entry's text
-
v2.0.28
Enhanced Marketplace Removal Cleanup
found in this entry's text
First cited
1The earliest release whose published evidence quoted enabledPlugins was v2.1.223, 5 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
2Build by build
149One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.