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 ·

Resuming after an interruption now skips stale turns and covers more API errors

On resume, Claude Code now ignores interrupted turns older than an age limit and treats several API errors, not just rate limits, as the cause

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

When you resume a session whose last turn was interrupted, Claude Code decides whether that turn can be picked up again. This check changed in two ways:

  • Claude Code now has a maximum age. An interrupted turn older than that is treated as stale and is not resumed.
  • Before, Claude Code noted a turn as ending on an error only when it hit a rate limit (a cap on how many requests you can make). It now also covers a missing request token, a model that was not found, and a server error.

The separate handling for a silent reply after a tool that ends the turn is still controlled by a server switch that falls back to on when the server sends nothing.

Why

Auto-resume after an interruption now reacts to more kinds of API failure, and it no longer brings back a turn that is too old to be useful.

Read from
Feature flag
tengu_vast_journal 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

See this entry in the whole of v2.1.311 →

Feedback