Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

New environment variables for spare sessions and held messages

Two new environment variables, one controlling whether a claimed spare process keeps its boot session id, the other about stopping held messages

Group of 2 Use it now Notable No documentation found New Features
JSON All of v2.1.318
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
New FeaturesKind: in v2.1.318,
What probably matters to youSection of the release

What

Two new environment variables have been added to the list of runtime tuning variables Claude Code accepts. An environment variable is a named setting passed to a program when it starts. Neither name appeared in the build before this release.

  • CLAUDE_CODE_SPARE_KEEPS_BOOT_SESSION_ID affects spare processes. A spare process is a copy of Claude Code started ahead of time so it is ready when needed. When a spare process is claimed without a sessionId and this variable is not set, the claim now looks up a session id and applies it, recording the reason spare_claim. A session is one continuous conversation, and its id is the label that identifies it.
  • CLAUDE_CODE_DISABLE_STOP_OF_HELD_MESSAGES relates to held messages. The members do not say more about what it does.

Why

In practice, a prewarmed spare process now takes on a looked-up session id when it is claimed, unless CLAUDE_CODE_SPARE_KEEPS_BOOT_SESSION_ID is set. Setting that variable keeps the id the process started with. Both variables look like internal switches, not everyday settings.

Read from
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: CLAUDE_CODE_SPARE_KEEPS_BOOT_SESSION_ID

See this entry in the whole of v2.1.318 →

Feedback