{"version":"2.1.268","anchor":"settings-env-vars-now-validated-invalid-namesvaluesnul-by","canonical_anchor":"settings-env-vars-now-validated-invalid-namesvaluesnul-by","heading":"Settings env vars now validated: invalid names\/values\/NUL bytes are dropped with a warning","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/settings-env-vars-now-validated-invalid-namesvaluesnul-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Settings env vars now validated: invalid names\/values\/NUL bytes are dropped with a warning\n\nInvalid environment variable names or values in settings.json are now dropped with a warning instead of silently used\n\n**What**\n\nEnvironment variables defined in an `env` block inside `settings.json` now go through a validation step before Claude Code applies them. Entries are stripped out, with a one-time warning logged per settings scope, if:\n\n- the key isn't a valid environment-variable name\n\n- the value isn't a string, number, or boolean\n\n- the value contains a NUL character\n\n**Why**\n\nThis catches malformed or invalid `env` entries in settings files early, rather than letting them silently fail or produce confusing behavior later.\n\n- Area: Settings\n- Names: `env`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}