{"version":"2.1.291","anchor":"transcript-loader-no-longer-yields-to-the-event-loop","canonical_anchor":"transcript-loader-no-longer-yields-to-the-event-loop","heading":"Loading a saved conversation now runs in one uninterrupted pass","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291\/e\/transcript-loader-no-longer-yields-to-the-event-loop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291","markdown":"### Loading a saved conversation now runs in one uninterrupted pass\n\nReading a session's transcript no longer pauses to let the interface respond, so resuming a very large session may briefly freeze the screen\n\n**What**\n\nWhen you resume a session (a saved conversation with Claude Code), Claude Code reads its transcript, the file that records every message in that conversation. That reading step now runs from start to finish in one go.\n\nPreviously it paused every so often to let the rest of the program catch up. Those pauses kept the screen responsive while a long transcript loaded. The parsing itself works the same way as before.\n\nThe lower-level step that walks through the file line by line works the same way now. It is a single straight pass with no pauses.\n\n**Why**\n\nOn a very large transcript, resuming may now hold up the interface until loading finishes, although the load itself should be quicker overall. If the screen stops responding briefly while a long session resumes, this is the likely reason.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}