{"version":"2.1.166","anchor":"managed-settings-validation-errors-reported-to-stderr","canonical_anchor":"managed-settings-validation-errors-reported-to-stderr","heading":"Managed settings validation errors reported to stderr","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.166\/e\/managed-settings-validation-errors-reported-to-stderr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.166","markdown":"### Managed settings validation errors reported to stderr\n\nWhen managed settings contain entries that fail schema validation, Claude now writes descriptive errors to stderr at startup:\n\n- For invalid entries that are dropped but don't affect enforcement: \"Managed settings contain invalid entries (remaining valid policies are still enforced):\"\n- For invalid entries that prevent a policy from being enforced at all: \"Managed settings failed to load; policies from the failed source are NOT in effect:\"\n\nSpecific field-level messages include things like `\"allowedMcpServers\" was present but invalid; enforcing an empty allowlist (no MCP servers admitted) until it is fixed.`\n\n**Evidence**\n\nNew validation error reporter (search for `\"Managed settings contain invalid entries\"`)"}