{"version":"2.1.319","anchor":"settings-env-keys-that-name-a-use-case-are-ignored-with-a-wa","canonical_anchor":"settings-env-keys-that-name-a-use-case-are-ignored-with-a-wa","heading":"Some environment variables set in settings are now ignored with a warning","tier":"notice","area":"Settings","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/settings-env-keys-that-name-a-use-case-are-ignored-with-a-wa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Some environment variables set in settings are now ignored with a warning\n\nCertain env keys in settings that name a use case are now dropped, and Claude Code logs a warning for each one\n\n**Unclear.** Which environment variable names fall into the ignored set is not stated.\n\n**What**\n\nYour settings file can set environment variables (named values programs read at startup) through its env section. Claude Code now drops certain of these keys entirely and logs a warning once for each one.\n\nThe warning says the key names a use case, and that only the environment Claude Code is started with can set it. To use such a variable, set it in your shell or launcher before starting Claude Code, not in settings.\n\n**Why**\n\nIf you set one of these variables in `settings.json`, it stops having any effect. The warning is the only sign of this, so check your logs if a setting seems to have stopped working.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}