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

Transcript writing stops after a fatal write error instead of retrying

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

You'll notice Improvements
JSON All of v2.1.248
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.248,
ImprovementsSection of the release
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 →

Feedback