strictPluginOnlyCustomization

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.

Releases whose published page names strictPluginOnlyCustomization.

1. v2.1.284 28 Sep 2026
   claude mcp add is refused when managed settings allow only plugin MCP servers

   If managed settings restrict MCP servers to plugins, claude mcp add now stops with an error instead of adding a server that never loads

   found in this entry's text, named in this entry

2. v2.1.282 24 Sep 2026
   A malformed strictPluginOnlyCustomization policy now locks down instead of being ignored

   An invalid strictPluginOnlyCustomization value in managed settings is now treated as true, and bad payloads are rejected with an error

   found in this entry's text, named in this entry

3. v2.1.282 24 Sep 2026
   claude doctor no longer checks strictPluginOnlyCustomization in managed settings

   claude doctor has stopped warning about invalid or unrecognized strictPluginOnlyCustomization values in managed-settings.json

   found in this entry's text, named in this entry

4. v2.1.282 24 Sep 2026
   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 enabledPlugins entry no longer voids the rest

   found in this entry's text

5. v2.1.81 20 Mar 2026
   strictPluginOnlyCustomization Policy [In Development]

   found in this entry's text

6. v2.1.81 20 Mar 2026
   Plugin Skill Discovery Policy Enforcement

   found in this entry's text

The earliest release whose published evidence quoted strictPluginOnlyCustomization was v2.1.81, 20 Mar 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.

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