{"version":"2.1.300","anchor":"workflow-journal-repairs-a-torn-tail-before-appending","canonical_anchor":"workflow-journal-repairs-a-torn-tail-before-appending","heading":"Session journal recovers from a half-written last line before adding more","tier":"notice","area":"Session Transcripts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/workflow-journal-repairs-a-torn-tail-before-appending","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Session journal recovers from a half-written last line before adding more\n\nBefore adding to its on-disk journal, Claude Code now closes off a broken last line so new entries are not merged into it\n\n**What**\n\nClaude Code keeps a journal file on disk to save session and workflow data. If a crash or interruption left the last line of that file incomplete, the next entry could be written straight onto the end of the broken one.\n\nBefore adding a new entry, Claude Code now checks whether the last line is missing its line ending, or whether the end of the file was torn on the newer storage format. If so, it first writes a line break and a marker, then adds the new entry on a clean line.\n\n**Why**\n\nA broken entry left behind by a crash stays separate from the entries that follow it, which makes the journal easier to recover.\n\n- Area: Session Transcripts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}