Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.247 ·

Attaching to an unresponsive background session says so

Attaching to a live but silent background session now says "Session isn't responding" instead of a vague error.

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

Attaching to a background session that is alive but silent now reports that specific condition instead of failing with an unexplained error. A new ENORESPONSE case, a distinct attach failure meaning the session did not answer, surfaces as "Session isn't responding", and the fleet view of running jobs branches on it: a finished job that is not responding shows that fixed message, while a live one goes through the restart prompt.

Details
  • Both the ENORESPONSE condition and the "Session isn't responding" text are new in this build.
  • Attach failures for reasons other than no response are unchanged and still report their own error.
  • The restart prompt text is unchanged: press Enter again to restart it (the conversation is saved).
  • The same area gained a hand-written parser for kitty-protocol keyboard escape sequences, an extended terminal key encoding, matching specific key codes.
Evidence

press Enter again to restart it (the conversation is saved), Session isn't responding

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.247 →

Feedback