{"version":"2.1.314","anchor":"folder-env-settings-untrusted-folder-env-block-now-warns-an","canonical_anchor":"folder-env-settings-untrusted-folder-env-block-now-warns-an","heading":"Claude Code now warns when it ignores a folder's environment settings","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/folder-env-settings-untrusted-folder-env-block-now-warns-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Claude Code now warns when it ignores a folder's environment settings\n\nIn sessions that cannot ask about folder trust, Claude Code warns once about ignored folder environment variables and allows a short safe list\n\n**What**\n\nA folder's settings files can set environment variables, which are named values that change how programs behave. Some sessions cannot show the question asking whether you trust a folder. In those sessions Claude Code drops most of these variables, and it now shows a one-time warning listing the ones it ignored.\n\nOnly a short list of variables is still allowed, such as `DISABLE_TELEMETRY=1`. Outside the stricter mode, values that pass Claude Code's shared check for safe values are also allowed.\n\n**Why**\n\nBefore, these variables were dropped silently, which made it hard to see why a project's environment settings had no effect, for example on self-hosted machines that run Claude Code automatically. The warning now says which ones were ignored.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}