{"version":"2.1.301","anchor":"global-config-env-vars-now-read-via-a-helper","canonical_anchor":"global-config-env-vars-now-read-via-a-helper","heading":"Environment variables from global configuration are applied differently","tier":"internal","area":"Environment Variables","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/global-config-env-vars-now-read-via-a-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Environment variables from global configuration are applied differently\n\nEnvironment variables from Claude Code's global configuration are now applied through a different step than before\n\n**Unclear.** It is not clear whether this changes which environment variables from global configuration are applied or how.\n\n**What**\n\nClaude Code's global configuration can set environment variables, which are named values passed to the programs it runs. These are now read and applied through a different step instead of directly from the configuration.\n\n**Why**\n\nThis could change how those variables are cleaned up or where they are taken from.\n\n- Area: Environment Variables\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}