{"version":"2.1.323","anchor":"settings-env-ignore-warning-generalized","canonical_anchor":"settings-env-ignore-warning-generalized","heading":"Warning when a settings file tries to set a variable it can't set","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/settings-env-ignore-warning-generalized","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Warning when a settings file tries to set a variable it can't set\n\nClaude Code now warns when a settings file sets an environment variable that only your startup environment or Claude Code itself may set\n\n**What**\n\nA settings file can set environment variables, which are named values programs read when they start. Some variables cannot take their value from a settings file. When a settings file tries to set one of those, Claude Code now warns that no settings file can give it this value, only the environment Claude Code is started with or Claude Code itself. Before, it warned only for one particular group of variables.\n\n**Why**\n\nYou now hear about it when Claude Code ignores a variable you put in a settings file, instead of having it silently not apply.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}