{"version":"2.1.300","anchor":"local-journal-flags-tornunreadable-lines","canonical_anchor":"local-journal-flags-tornunreadable-lines","heading":"Session journal now reports unreadable lines instead of skipping them quietly","tier":"notice","area":"Session Transcripts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/local-journal-flags-tornunreadable-lines","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Session journal now reports unreadable lines instead of skipping them quietly\n\nThe on-disk session journal now tells a harmless half-written last line apart from an unreadable line, and reports the latter\n\n**What**\n\nClaude Code keeps a journal of session data on disk. When loading it, Claude Code used to skip lines it could not read without saying anything. Now it tells two cases apart:\n\n- A half-written last line, left by a write that was cut off, is treated as harmless.\n\n- Any other unreadable line is flagged, and the load reports that a line could not be read.\n\n**Why**\n\nClaude Code can now notice when saved session data is damaged instead of quietly losing it, which helps it recover.\n\n- Area: Session Transcripts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}