Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Settings env values are now tracked, with groundwork to withhold them from some sources

Claude Code now records which environment variables came from settings and adds a check to withhold settings env blocks, currently inactive

Group of 2 Nothing to try yet Internal Changes
JSON All of v2.1.281
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.281,
In DevelopmentSection of the release

Unclear The finding does not say which later checks use isSettingsSourcedEnvValue or what they do differently with the answer.

What

Settings files can set environment variables, the named values programs read at startup, through an env block. This release changes how those are handled.

  • The env manager now keeps a record of every env value offered by settings, keyed by the upper-cased variable name, and adds isSettingsSourcedEnvValue so later checks can tell whether a variable's current value came from settings. The record is cleared when settings are reset.
  • filterSettingsEnv now returns nothing for a settings source when withholdsEnvFrom(source) is true, and processWrapper goes through the same check instead of being read directly from each source. In this build the switch that would turn this on always returns false, so nothing is withheld yet.
  • Claude Code now warns when env keys meant for spawning host processes are dropped.
  • Settings are reset if the path of the user settings file moves while settings are being applied.

Why

For now this changes nothing you can see beyond the new warning. The members suggest it prepares for a mode where project or user settings cannot redirect environment variables for a pinned login.

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 doubtThe finding does not say which later checks use `isSettingsSourcedEnvValue` or what they do differently with the answer.

See this entry in the whole of v2.1.281 →

Feedback