{"version":"2.1.281","anchor":"warning-when-settings-env-vars-are-overridden-by-the-launch","canonical_anchor":"warning-when-settings-env-vars-are-overridden-by-the-launch","heading":"Warning when settings env vars are overridden by the launch environment","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/warning-when-settings-env-vars-are-overridden-by-the-launch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Warning when settings env vars are overridden by the launch environment\n\nClaude Code now logs a warning naming settings env vars it ignored because the launch environment already set them differently\n\n**What**\n\nSettings files can list environment variables for Claude Code to use. Environment variables are named values a program reads when it runs. If the environment Claude Code was launched from already sets the same variable, the launch value wins and the settings value is dropped. That has not changed.\n\nWhat is new is that Claude Code now writes a warning to its log naming the variables that were dropped. The warning appears only when:\n\n- The settings value differs from the value already set at launch\n\n- That pairing of settings source and variable has not already been reported\n\n**Why**\n\nBefore, a value in settings could be silently ignored, which made it hard to understand why a setting seemed to have no effect. The log now tells you, and it says so once per variable instead of repeating.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}