{"version":"2.1.286","anchor":"session-transcript-leaf-selection-made-more-robust","canonical_anchor":"session-transcript-leaf-selection-made-more-robust","heading":"Resumed sessions choose their starting point differently","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/session-transcript-leaf-selection-made-more-robust","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Resumed sessions choose their starting point differently\n\nWhen resuming a session, Claude Code uses a new check to decide whether to continue from the newest message or the recorded last point\n\n**Unclear.** How the new check decides between the two points is not shown.\n\n**What**\n\nWhen you resume a session, Claude Code has to pick which message to continue from. It chooses between the newest message and the point it had recorded as the last one. It now makes that choice with a new check of how the two messages are related, one that can also look through batched tool turns. It also keeps track of whether the last prompt was recorded explicitly. This can change which branch of the conversation a resumed session lands on.\n\n**Why**\n\nThis may stop resumed sessions from landing on the wrong branch after tool turns that were interrupted or batched together.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}