{"version":"2.1.323","anchor":"plugin-managed-settings-env-filter-exception","canonical_anchor":"plugin-managed-settings-env-filter-exception","heading":"One blocked environment variable can now survive settings cleanup","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-managed-settings-env-filter-exception","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### One blocked environment variable can now survive settings cleanup\n\nClaude Code can now keep one specific blocked environment variable when it cleans up environment variables in settings\n\n**Unclear.** Which environment variable is kept, and under what condition, is not stated.\n\n**What**\n\nSettings can define environment variables, which are named values passed to programs. Claude Code removes some names that are on a blocklist. It can now keep one specific blocked name when a certain condition is met. Before, every blocked name was removed.\n\n**Why**\n\nThis loosens a rule that strips risky environment variables from settings.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}