{"version":"2.1.260","anchor":"worktree-resume-distinguishing-whether-binding-could-actual","canonical_anchor":"worktree-resume-distinguishing-whether-binding-could-actual","heading":"Worktree resume: distinguishing whether binding could actually be cleared","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/worktree-resume-distinguishing-whether-binding-could-actual","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Worktree resume: distinguishing whether binding could actually be cleared\n\nResume now explains clearly when a worktree binding can't be cleared because transcripts are off.\n\nWhen 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.\n\n- Area: Worktrees\n- Names: `--fork-session`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}