{"version":"2.1.284","anchor":"settings-schema-validated-lazily-per-present-key-flagging-k","canonical_anchor":"settings-schema-validated-lazily-per-present-key-flagging-k","heading":"Managed settings are now checked only against the keys a file actually contains","tier":"internal","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/settings-schema-validated-lazily-per-present-key-flagging-k","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Managed settings are now checked only against the keys a file actually contains\n\nClaude Code now builds its managed-settings check only for the keys present in a settings file, and reuses it, instead of building it in full\n\n**Unclear.** It is not clear whether the new message can ever appear to a user.\n\n**What**\n\nManaged settings are settings an organisation can set for Claude Code. Claude Code checks them against a schema, a description of which keys are allowed and what they may contain.\n\nBefore, it built the full schema for every possible key. It now builds the schema only for the keys a settings document actually contains, and keeps it for reuse. It also has a new safety check: if a document holds a key the saved schema was not built for, it reports \"This settings schema was built for a document without this key\".\n\n**Why**\n\nThis is probably meant to make startup faster, with the new message guarding against a schema being reused for the wrong document.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}