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.
What
Two behaviours changed:
- 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.
- 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.
Why
Both 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
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…