{"version":"2.1.305","anchor":"session-index-rebuild-handles-unmatched-or-foreign-lines-dif","canonical_anchor":"session-index-rebuild-handles-unmatched-or-foreign-lines-dif","heading":"Session index handles unexpected transcript lines differently","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/session-index-rebuild-handles-unmatched-or-foreign-lines-dif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Session index handles unexpected transcript lines differently\n\nWhen rebuilding its index from a transcript, Claude Code now reacts to malformed user or assistant lines and unreadable files\n\n**Unclear.** What starting a successor index changes for someone resuming a session is not clear.\n\n**What**\n\nClaude Code builds an index from a session's transcript, the saved record of the conversation. While reading the transcript, it used to simply note every line. Now:\n\n- A line marked as from the user or the assistant that is not in the expected form makes the index start a successor.\n\n- A transcript file that cannot be opened also makes the index move to a successor.\n\n**Why**\n\nThis may make resuming a session more robust when its transcript has been rewritten or damaged.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}