{"version":"2.1.282","anchor":"claude-doctor-no-longer-validates-strictpluginonlycustomiz","canonical_anchor":"claude-doctor-no-longer-validates-strictpluginonlycustomiz","heading":"claude doctor no longer checks strictPluginOnlyCustomization in managed settings","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/claude-doctor-no-longer-validates-strictpluginonlycustomiz","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### `claude doctor` no longer checks `strictPluginOnlyCustomization` in managed settings\n\n`claude doctor` has stopped warning about invalid or unrecognized `strictPluginOnlyCustomization` values in managed-settings.json\n\n**Unclear.** Whether this check moved somewhere else in Claude Code is not known.\n\n**What**\n\n`claude doctor` checks your installation for problems. It used to read the admin-managed `managed-settings.json` file and warn when `strictPluginOnlyCustomization` had an invalid value (anything other than true or a list) or contained values it did not recognize. That check has been removed. The check that warns when `otelHeadersHelper` failed on its last run is still there.\n\n**Why**\n\nAdmins no longer get this hint from `claude doctor`, so a mistyped `strictPluginOnlyCustomization` value will need to be caught another way.\n\n- Area: Elsewhere\n- Names: `claude doctor`, `strictPluginOnlyCustomization`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}