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

Crashed sessions write a structured diagnostic line to the transcript

You'll notice
Useful2 Signal2
Error Handling

A crashed non-interactive session writes a structured diagnostic line into the transcript.

What

When a non-interactive session throws, the transcript now gets a line naming the error, its API status and its cause alongside the raw messages, and in some modes the user sees a short "Session crashed" message instead of the raw error text.

Details
  • The line is prefixed [session_crash] and starts with error_name=.
  • Which sessions get the short form rather than the raw error is decided by a session check in the crash path.
Evidence

[session_crash] error_name=

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 →