Source Intelligence

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

Transcript writing stops after a fatal write error instead of retrying

You'll notice
Useful3 Signal2
Sessions

A fatal transcript write error now stops writing instead of silently carrying on.

What

The transcript writer now latches a fatal write failure. Once latched, further appends throw that error straight back, the queue drain rethrows it on the next flush rather than quietly resolving all waiters, and the local garbage-collection and compaction backstop is skipped. Previously a failed drain only logged and carried on. The latch clears when flush state is reset.

Details
  • Effect for a session that hits a fatal storage condition: it stops appending rather than writing more on top of a broken file.
Evidence

Transcript write failed (, storeFence

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.248 →