Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

claude attach explains cleaned-up background sessions instead of failing generically

You'll notice
Useful3 Signal2
Sessions

Reopening a cleaned-up background session now points you at claude rm and claude respawn.

claude attachclaude rmclaude respawn
What

Trying to reopen a background session whose transcript has already been deleted now gives a specific message pointing you at claude rm and claude respawn, instead of the old generic wake failure. A separate message, "Can't open — this session is running in another terminal", covers the case where another interactive session holds it.

Details
  • Respawn refuses such rows with errorCode: "dead_epoch_transcript_gone".
  • Both the attach CLI and the fleet view branch on that code, print the message and exit 1.
  • Telemetry records cli_bg_attach and fleet_view_open with reason dead_epoch_transcript_gone.
  • Unconditional in this build.
Evidence

dead_epoch_transcript_gone

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →