{"version":"2.1.271","anchor":"exiting-a-mid-session-worktree-now-notes-commits-kept-server","canonical_anchor":"exiting-a-mid-session-worktree-now-notes-commits-kept-server","heading":"Exiting a mid-session worktree now notes commits kept server-side","tier":"notice","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/exiting-a-mid-session-worktree-now-notes-commits-kept-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Exiting a mid-session worktree now notes commits kept server-side\n\nRemoving a worktree mid-session now tells you its commits are still kept on the server\n\n**What**\n\nA worktree is a separate working copy of a git repository that Claude Code can use during a session. If you remove a worktree partway through a session and it had commits made in it, the message you now see includes a note that those commits remain stored server-side, along with a shortened id of the last commit (the 'head changeset').\n\n**Why**\n\nThis reassures you that deleting the worktree doesn't lose the work done in it, since the commits are still retained on the server rather than only existing in the now-removed local copy.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}