When a resumed session's pinned worktree can't be verified and transcript saving is off, Claude Code now says so explicitly: "The worktree binding could not be cleared because transcript saving is off," and suggests using --fork-session or starting a new conversation instead of silently clearing or keeping the binding.
Names in the bundle--fork-session
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Hooks reference touched a line naming --fork-session after this was published.
| `fork` | A new session forked from an existing one: `--fork-session` with `--resume` or `--continue`, the `/fork` background copy, `/branch`, or a conversation you [move to the background](/docs/en/agent-view#from-inside-a-session) |hooks see the edit
Confirmed since
Anthropic's documentation has since written up --fork-session, on Error reference.
When you fork a session, for example with [`--fork-session`](/docs/en/cli-reference#cli-flags) or [`/branch`](/docs/en/sessions#branch-a-session), Claude Code copies the original session's backups into the fork. When Claude Code can't copy…errors see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --fork-session, on Error reference.