{"version":"2.1.271","anchor":"settings-validator-now-flags-non-warning-issues-in-usersetti","canonical_anchor":"settings-validator-now-flags-non-warning-issues-in-usersetti","heading":"Settings validator now flags non-warning issues in userSettings\/flagSettings","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/settings-validator-now-flags-non-warning-issues-in-usersetti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Settings validator now flags non-warning issues in userSettings\/flagSettings\n\nSettings validator now detects fully broken user\/flag settings files, not just warnings\n\n**What**\n\nClaude Code's settings validator gained a new check that looks at `userSettings` and `flagSettings` (two of its settings sources) and flags the first one that failed to parse into a usable value while also having validation issues beyond simple warnings. This distinguishes a settings file that is effectively broken from one that merely triggered a warning.\n\n**Why**\n\nThis makes it possible to catch and report settings files that are genuinely unusable, rather than treating them the same as files with minor, non-blocking issues.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}