Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
What
LocalFileJournal, the mechanism Claude Code uses to persist session data to disk, now has a restoreState() check that reports whether a restore is "missing", "partial", or "complete", by looking for marker records at the start ({type:"restoring"}) and end ({type:"restored"}) of a restore. A companion writeRestored() function wraps a batch of records between these markers and writes them either as an atomic delete-and-append (on the newer v5 storage backend) or as a plain file write otherwise.
Why
This gives the journal a reliable way to tell whether a previous restore actually finished, which matters for recovering cleanly if Claude Code was interrupted partway through restoring session data.
