You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
What
Claude Code can run sessions in the background in a separate process. When that process is from an older version, Claude Code normally restarts it on the new version. Now Claude Code first compares the sign-in environment variables (settings passed to a program when it starts) the background process was started with against the current ones. On Linux and WSL it reads these from the running process.
If they differ:
the outdated background session is not restarted
a background session Claude Code has taken over is not upgraded automatically
Claude Code records that the restart was held back
This is controlled by a remotely managed switch.
Why
An upgrade restart could otherwise move a background session onto a different account or profile without you noticing.
Read from
Feature flag
tengu_tethered_buoyNot enough to say
Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.323: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.