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

Transcript re-stamp on exit tries the storage layer first

On exit, the final transcript update goes through the storage layer first, falling back to a direct write.

Under the hood Internal Changes
JSON All of v2.1.238
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.238,
Internal ChangesSection of the release
What

On shutdown, the final transcript update is attempted asynchronously through the storage layer under a timeout, and falls back to the old synchronous write when that lapses or the layer is not in use.

Details
  • The async path only runs when the newer storage backend is pinned on; otherwise the synchronous re-stamp is used directly.
  • Timeouts are logged rather than silently swallowed.
  • Exit lines belonging to another session are tracked so they are not appended twice.
  • A new transcript record type, artifact-autoreact-ledger, is registered as always persisted with last-write-wins.
Evidence

Exit re-stamp through the storage backend did not finish within

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

Feedback