Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Project environment variables are now filtered against higher-priority settings

Which environment variables from a project's settings get dropped now depends on what your launch environment, flag and policy settings set

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

A project's .claude/settings.json file can set environment variables, which are named values handed to the programs Claude Code runs. Claude Code filters some of these out. That filter now also looks at variables set by sources that take priority over the project:

  • The environment Claude Code was started with, not counting names that user or global settings had already set
  • Flag settings
  • Policy settings

Before this change, the filter did not consider these higher-priority sources.

Why

Which of a project's environment variables actually apply can now differ depending on what those higher-priority sources set.

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 doubtIt is not clear whether this makes Claude Code drop more project environment variables or fewer.

See this entry in the whole of v2.1.282 →

Feedback