{"version":"2.1.296","anchor":"unparsable-transcript-lines-are-now-counted-and-reported-on","canonical_anchor":"unparsable-transcript-lines-are-now-counted-and-reported-on","heading":"Broken lines in saved conversations are now counted when loading","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/unparsable-transcript-lines-are-now-counted-and-reported-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Broken lines in saved conversations are now counted when loading\n\nWhen loading a saved conversation, Claude Code now counts and logs lines it could not read instead of skipping them silently\n\n**What**\n\nClaude Code saves each conversation as a transcript file, one entry per line. When it loads one, it now counts any non-blank lines that cannot be read, logs a note saying how many it skipped (for example after a torn or corrupt write), and reports the count.\n\n**Why**\n\nA damaged transcript, which can make resuming a conversation go wrong, now leaves a trace instead of failing quietly.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}