Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

Background sessions on an LLM gateway are not restarted after a crash

A crashed background session that runs through an LLM gateway is no longer restarted automatically, even when its saved state reads success

You'll notice Improvements
JSON All of v2.1.319
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.319,
ImprovementsSection of the release
What

The automatic restart of a background session that crashes after its saved state reads success now has one more condition. The session must not be held on an LLM gateway. An LLM gateway is a server that sits between Claude Code and the model provider and passes requests along.

Claude Code reads a mark saved for each session that says whether it uses a gateway. If it cannot read that mark, it logs a message and treats the session as if it uses a gateway, so it is not restarted.

Why

Background sessions on an LLM gateway are handled differently when Claude Code updates or recovers from a crash. If you use a gateway, expect a crashed background session to stay stopped rather than come back on its own.

Read from
Feature flag
tengu_bg_settled_crash_restart 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.319: 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.319. It isn't a statement about your account. What a flag value here can and cannot tell you

See this entry in the whole of v2.1.319 →

Feedback