{"version":"2.1.299","anchor":"settings-files-that-fail-validation-are-reported-at-startup","canonical_anchor":"settings-files-that-fail-validation-are-reported-at-startup","heading":"Claude Code tells you at startup when a settings file did not load","tier":"notice","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/settings-files-that-fail-validation-are-reported-at-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude Code tells you at startup when a settings file did not load\n\nAt startup Claude Code now lists settings files that failed to load, including their hooks and permission rules, and entries it skipped\n\n**What**\n\nWhen a settings file fails its checks, Claude Code now prints a notice at startup on its error output. The notice lists the settings files that did not load, saying that nothing in them is in effect, including hooks and permission rules. It also lists entries that were skipped because they are not supported. Nothing is printed when the output format is `json` or `stream-json`.\n\n**Why**\n\nA broken settings file used to drop its permission rules without a word, which could leave you less protected than you thought. Now you can see it and fix the file.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}