Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release
Unclear The finding does not say what the reset step clears or what the new cleanup at session end does.
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.