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 ·

Remote sessions change how they keep and drop server connections

Cloud remote sessions get new rules for when to stop and leave the connection pool, and one option for live-only shell task rows is gone

Under the hood Internal Changes
JSON All of v2.1.323
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release
What

Remote sessions run Claude Code on a cloud machine and keep a connection open to a server. Claude Code changed how that connection behaves:

  • A new option can stop the connection when the server accepts nothing.
  • The rule for leaving the shared connection pool now depends on the session. For byoc sessions it is to leave after no answer or after a server error.
  • The option to show only live shell task rows is removed from the bridge configuration.
  • Behind a remotely controlled switch, the count of calls still waiting now also includes parked calls and calls that were served but never sent.

That switch is off unless it is switched on remotely. The server has returned it on for this site's account and off for an anonymous account.

Why

This changes how remote sessions pool and drop their connections, which can affect how they recover when the server does not respond.

Read from
Feature flag
tengu_peaceful_lemur 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: off · compiled default in v2.1.323: off

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.

tengu_tranquil_cocoa 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: off

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.

tengu_ccr_upload_hold_marker 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: off

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

What has happened since
Flag reading moved The flag server now returns on for tengu_peaceful_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_peaceful_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns on for tengu_peaceful_lemur, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

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_peaceful_lemur

See this entry in the whole of v2.1.323 →

Feedback