Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Crashed background sessions can restart even after they finished successfully

A background session that crashes from its own error after its saved state reads success can now be restarted, up to a limit

You'll notice Improvements
JSON All of v2.1.311
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Background AgentsArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release
What

A background session is a Claude Code session running without a terminal attached, watched over by a supervisor that can restart it. Before, if a session's saved state already showed it had finished, the supervisor simply stopped it.

Now, if a background session dies from its own unhandled error while its saved state reads success, the supervisor restarts it. It is not restarted when:

  • someone is attached to it
  • it has a scheduled task in progress
  • it is pinned

Restarts are limited. Past the limit the session stops, and a notice says it was not restarted because it crashed again after a number of restarts. The conversation is saved.

The code falls back to allowing these restarts when the server sends no setting.

Why

A background session that crashes can now come back on its own instead of staying stopped, while the limit keeps a session that keeps crashing from restarting forever.

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.311: 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.311. 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_bg_settled_crash_restart

See this entry in the whole of v2.1.311 →

Feedback