{"version":"2.1.291","anchor":"transcript-loader-reverts-to-a-synchronous-scan-and-drops-th","canonical_anchor":"transcript-loader-reverts-to-a-synchronous-scan-and-drops-th","heading":"Session transcripts load in a single pass again, without pausing or retrying","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291\/e\/transcript-loader-reverts-to-a-synchronous-scan-and-drops-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291","markdown":"### Session transcripts load in a single pass again, without pausing or retrying\n\nReading a session file no longer pauses for the interface or restarts after rewrites, so very large resumes may stall the screen\n\n**What**\n\nWhen you resume a session, Claude Code reads its transcript file, the record of the whole conversation. Two things about that read have changed.\n\n- Pausing: the read used to stop now and then so the interface stayed responsive. It now reads the file in chunks in one continuous pass.\n\n- Retrying: the read used to start over when the file had been rewritten during loading, up to a limit, and then report an error. That retry loop and its error are gone.\n\nIf a transcript cannot be read, Claude Code now logs a \"transcript unreadable\" message.\n\n**Why**\n\nResuming a very large session may make the screen stop responding until loading finishes. A file that changes while it is being read is no longer retried.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}