Unclear The case-insensitive matching was inferred rather than confirmed.
What
The enabledPlugins setting turns individual plugins on or off. Built-in plugins, the ones that ship with Claude Code, are named like name@builtin.
For these, Claude Code now also finds an enabledPlugins entry whose name differs only in letter case, and uses the built-in plugin's own spelling. Before, only an exact match counted.
Why
A setting for a built-in plugin typed with the wrong capitalisation now works instead of being silently ignored.
Names in the bundleenabledPlugins
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Configure server-managed settings touched a line naming enabledPlugins after this was published.
* A cached [`prependPlugins`](https://code.claude.com/docs/en/settings-reference#prependplugins), [`appendPlugins`](https://code.claude.com/docs/en/settings-reference#appendplugins), or [`enabledPlugins`](https://code.claude.com/docs/en/se…server-managed-settings see the edit
Confirmed since
Anthropic's documentation has since written up enabledPlugins, on Manage Claude Code plugins for your organization.
Every key in the table is a managed setting, apart from `enabledPlugins`, `syncClaudeAiPlugins`, `CLAUDE_CODE_DISABLE_OFFICIAL_MARKETPLACE_AUTOINSTALL`, and `allowManagedModsOnly`:plugins/org see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The case-insensitive matching was inferred rather than confirmed.
Anthropic's documentation agrees
Anthropic's documentation has since written up enabledPlugins, on Manage Claude Code plugins for your organization.