{"version":"2.1.323","anchor":"prompt-tail-selection-and-bash-parse-timeout","canonical_anchor":"prompt-tail-selection-and-bash-parse-timeout","heading":"Changes to how a branched session picks earlier messages and how slow shell commands are read","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/prompt-tail-selection-and-bash-parse-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Changes to how a branched session picks earlier messages and how slow shell commands are read\n\nA branched session now builds its starting messages from the last qualifying message, and a timed-out shell-command check now reports a timeout\n\n**Unclear.** What either change means in practice for a user is not stated, including whether a timed-out shell-command check now leads to a different permission prompt.\n\n**What**\n\nTwo behaviours changed:\n\n- Branched sessions: when Claude Code branches off a copy of the conversation for a user without a terminal, it now picks the earlier messages to carry over starting from the last message that qualifies, not from the very end of the conversation.\n\n- Shell command checks: when Claude Code reads a shell command to understand it and that reading runs out of time, it now reports the timeout as its own result instead of returning nothing.\n\n**Why**\n\nBoth changes affect edge cases: what a branched copy of the conversation starts with, and how a shell command that takes too long to read is handled when Claude Code decides whether to ask your permission to run it.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}