{"version":"2.1.314","anchor":"warning-text-for-settings-env-vars-ignored-under-desktop-app","canonical_anchor":"warning-text-for-settings-env-vars-ignored-under-desktop-app","heading":"Clearer warning when the desktop app overrides a settings env var","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/warning-text-for-settings-env-vars-ignored-under-desktop-app","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Clearer warning when the desktop app overrides a settings env var\n\nThe warning now says the desktop app or runner supplies the value and your settings value is not used\n\n**What**\n\nYour settings file can set environment variables, named values that programs read, for Claude Code. When a session is started by the desktop app or a runner that already supplies one of those values, Claude Code shows a warning. The warning now says that the desktop app or runner that started the session supplies the value, so the value in your settings is not used. Before, it said the environment the session was launched with already set it.\n\n**Why**\n\nIt makes clearer why your settings value was ignored and where the value that is used comes from.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}