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.281 ·

Config env application resets cached state afterwards

Applying environment variables from settings now always runs a reset step afterwards, and ending a session gained a cleanup step

Entry
JSON All of v2.1.281
EntryKind: in v2.1.281,
ChangesSection of the release
What

Claude Code can set environment variables (named values handed to programs it runs) from your configuration. Two routines do this: applySafeConfigEnvironmentVariables and applyConfigEnvironmentVariables. New wrappers around both now always run a reset step afterwards, even if applying the variables fails partway.

The code that runs when a session (one continuous conversation with Claude Code) ends also gained a cleanup step that always runs.

Why

In practice, information Claude Code has stored and reused is cleared after environment variables from your configuration are applied, so it does not keep using values from before the change.

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 what the reset step clears or what the new cleanup at session end does.

See this entry in the whole of v2.1.281 →

Feedback