{"version":"2.1.307","anchor":"host-rule-message-for-env-values-that-cannot-be-overridden","canonical_anchor":"host-rule-message-for-env-values-that-cannot-be-overridden","heading":"Some environment values can only come from Claude Code's starting environment","tier":"notice","area":"Environment Variables","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/host-rule-message-for-env-values-that-cannot-be-overridden","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Some environment values can only come from Claude Code's starting environment\n\nClaude Code now refuses some changes to environment values, keeping them unless they came from its starting environment or from itself\n\n**Unclear.** Which environment variables this applies to, and what triggers the message, is not clear.\n\n**What**\n\nAn environment variable is a named value that programs read. Some of these values can now only be set by the environment Claude Code starts with, or by Claude Code itself. When something else tries to give one of them a value, Claude Code leaves it as it was and says it \"is unchanged: only the environment Claude Code starts with, or Claude Code itself, may give it this value (host rule)\".\n\n**Why**\n\nIn practice, setting one of these values later in a session does not take effect. It has to be set before Claude Code starts.\n\n- Area: Environment Variables\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}