Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

LocalFileJournal gains an explicit restore-in-progress protocol

LocalFileJournal now tracks whether a restore was interrupted, partial, or complete

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaSessionswhat it touches
KindInternal Changesin v2.1.265,
Under the hood No documentation found

LocalFileJournal now tracks whether a restore was interrupted, partial, or complete

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.

Read from
Names in the bundleLocalFileJournal

See this entry in the whole of v2.1.265 →

Feedback