{"version":"2.1.282","anchor":"project-scope-env-drop-now-weighs-launch-env-flag-and-polic","canonical_anchor":"project-scope-env-drop-now-weighs-launch-env-flag-and-polic","heading":"Project environment variables are now filtered against higher-priority settings","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/project-scope-env-drop-now-weighs-launch-env-flag-and-polic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Project environment variables are now filtered against higher-priority settings\n\nWhich environment variables from a project's settings get dropped now depends on what your launch environment, flag and policy settings set\n\n**Unclear.** It is not clear whether this makes Claude Code drop more project environment variables or fewer.\n\n**What**\n\nA project's `.claude\/settings.json` file can set environment variables, which are named values handed to the programs Claude Code runs. Claude Code filters some of these out. That filter now also looks at variables set by sources that take priority over the project:\n\n- The environment Claude Code was started with, not counting names that user or global settings had already set\n\n- Flag settings\n\n- Policy settings\n\nBefore this change, the filter did not consider these higher-priority sources.\n\n**Why**\n\nWhich of a project's environment variables actually apply can now differ depending on what those higher-priority sources set.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}