{"version":"2.1.265","anchor":"localfilejournal-gains-an-explicit-restore-in-progress-proto","canonical_anchor":"localfilejournal-gains-an-explicit-restore-in-progress-proto","heading":"LocalFileJournal gains an explicit restore-in-progress protocol","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/localfilejournal-gains-an-explicit-restore-in-progress-proto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### LocalFileJournal gains an explicit restore-in-progress protocol\n\nLocalFileJournal now tracks whether a restore was interrupted, partial, or complete\n\n**What**\n\nLocalFileJournal, 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.\n\n**Why**\n\nThis 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.\n\n- Area: Sessions\n- Names: `LocalFileJournal`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}