{"version":"2.1.301","anchor":"settings-parse-error-logging-reduced-to-a-single-flag","canonical_anchor":"settings-parse-error-logging-reduced-to-a-single-flag","heading":"Broken settings files are reported once in total instead of once per file","tier":"internal","area":"Config File","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/settings-parse-error-logging-reduced-to-a-single-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Broken settings files are reported once in total instead of once per file\n\nClaude Code now records a single settings parse error in total, rather than one for each broken settings file\n\n**Unclear.** Whether a second broken settings file still gets its own error message is not stated.\n\n**What**\n\nWhen a settings file cannot be read because its contents are malformed, Claude Code logs a parse error. It used to keep track of which files it had already reported. It now keeps one yes-or-no record for all of them.\n\n**Why**\n\nThis cuts repeated error messages. If you fix one broken settings file, check your other settings files as well.\n\n- Area: Config File\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}