{"version":"2.1.280","anchor":"settings-validation-now-warns-about-invalid-values-instead-o","canonical_anchor":"settings-validation-now-warns-about-invalid-values-instead-o","heading":"Settings validation now warns about invalid values instead of silently misbehaving","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/settings-validation-now-warns-about-invalid-values-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Settings validation now warns about invalid values instead of silently misbehaving\n\nClaude Code now warns when a settings.json value fails validation instead of silently ignoring it\n\n**What**\n\nA new validation pass checks settings values and flags keys whose configured value doesn't pass validation. It also distinguishes between a setting that \"counts as off\" versus one that \"counts as unset\" as a result of the invalid value, and suggests fixing it through `\/config` or deleting the key entirely.\n\n**Why**\n\nPreviously an invalid setting value could silently misbehave with no indication of the cause. Now you get a clear warning and a concrete way to fix it.\n\n- Area: Settings\n- Names: `\/config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}