{"version":"2.1.319","anchor":"resume-transcript-read-ahead-gets-a-time-budget-and-resumes","canonical_anchor":"resume-transcript-read-ahead-gets-a-time-budget-and-resumes","heading":"Resuming a long session no longer reads ahead without a time limit","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/resume-transcript-read-ahead-gets-a-time-budget-and-resumes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Resuming a long session no longer reads ahead without a time limit\n\nWhen resuming, Claude Code now limits how long it spends reading ahead in the transcript and refuses unsafe appends to it\n\n**What**\n\nWhen you resume a session, Claude Code reads ahead in its transcript, the saved record of the conversation. That read-ahead now:\n\n- has a time limit, and can have that limit lifted\n\n- can start partway through the file\n\n- retries reads that hang\n\n- is skipped on later resumes once a session has been marked as having run out of time\n\nAdding to an existing transcript is also safer. Claude Code now refuses to write if the file changed underneath it or ends in the middle of a line.\n\nBefore, the read-ahead had no time limit, only a check for reads that hung.\n\n**Why**\n\nVery large sessions should not stall when you resume them, and a transcript written by another program at the same time is less likely to be corrupted.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}