{"version":"2.1.284","anchor":"settings-validation-builds-a-schema-only-for-the-keys-a-file","canonical_anchor":"settings-validation-builds-a-schema-only-for-the-keys-a-file","heading":"Settings files are checked only against the settings they contain","tier":"internal","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/settings-validation-builds-a-schema-only-for-the-keys-a-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Settings files are checked only against the settings they contain\n\nClaude Code now validates a settings file by checking only the keys that file contains, instead of against the full list of every setting\n\n**Unclear.** Whether error messages or the handling of unknown settings keys changed is not settled.\n\n**What**\n\nWhen Claude Code reads a settings file, it checks the file's contents are valid. It now builds that check from only the keys the file actually contains and remembers it for reuse, rather than checking every file against one description of all possible settings. The same applies when managed settings (settings set by an administrator) are exported.\n\n**Why**\n\nThis most likely makes startup a little quicker. Settings that were valid before should still be valid.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}