Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Background sessions are not restarted when your sign-in setup has changed

Claude Code no longer restarts or upgrades an outdated background session when its sign-in settings differ from your current ones

You'll notice Improvements
JSON All of v2.1.323
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_buoy Not 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.

Read once, for one account on one subscription tier, against v2.1.323. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_tethered_buoy

See this entry in the whole of v2.1.323 →

Feedback