Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Environment variables from settings are applied earlier for programs Claude Code starts

Environment variables from your settings are now added before Claude Code filters the environment it passes to programs it starts

You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SettingsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear Exactly which settings variables now reach child programs that did not before, or the reverse, is not settled.

What

When Claude Code starts another program, such as a shell command, it builds an environment for it: the set of named values, like PATH, that the program can read. Claude Code now adds the environment variables defined in your settings before it removes the ones it does not pass on. Before, only colour-related settings values were added, and they were added last.

The merge now treats names that differ only in upper and lower case as the same name, and filters Windows-style names. CLAUDE_CODE_PERFORCE_MODE is protected so that it is kept when it is set to a true-like value.

Why

Variables you set in your settings may now reach the programs Claude Code starts differently than before. If a command behaves differently with respect to an environment variable, check what your settings define.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtExactly which settings variables now reach child programs that did not before, or the reverse, is not settled.

See this entry in the whole of v2.1.290 →

Feedback