{"version":"2.1.318","anchor":"transcript-loader-detects-key-order-and-records-more-scan-di","canonical_anchor":"transcript-loader-detects-key-order-and-records-more-scan-di","heading":"Session resume records more details about how transcripts are read","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/transcript-loader-detects-key-order-and-records-more-scan-di","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Session resume records more details about how transcripts are read\n\nWhen loading a saved session, Claude Code now checks the key order of each line and records many more counts about the scan\n\n**What**\n\nA transcript is the saved record of a session that Claude Code reads back when you resume it. While reading a transcript, Claude Code now checks the order in which three identifying fields appear on each line, and counts the lines and boundaries that use a different order.\n\nThe summary of each scan also gains many new counts, such as how many lines there were, how many were listed, how many parent entries could not be found, and where certain parts of the scan began. When Claude Code falls back from its usual way of restoring kept parts of a long session, it now records why.\n\n**Why**\n\nThese are mainly diagnostics for working out why resuming a session can be slow.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}