{"version":"2.1.304","anchor":"worktree-names-get-numbered-slugs-branch-commit-info-on-rem","canonical_anchor":"worktree-names-get-numbered-slugs-branch-commit-info-on-rem","heading":"Worktrees can get numbered names, and removal checks more carefully for commits","tier":"notice","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/worktree-names-get-numbered-slugs-branch-commit-info-on-rem","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Worktrees can get numbered names, and removal checks more carefully for commits\n\nClaude Code can now give a new worktree a numbered name, and when removing one it checks more carefully for commits\n\n**Unclear.** When Claude Code picks a numbered name instead of the requested one is not stated.\n\n**What**\n\nA worktree is a second working copy of a git project in its own folder, so work can happen there without touching your main copy. Claude Code changes how it handles them:\n\n- Creating a worktree can now pick a numbered name instead of using the requested name directly. If no usable name is found, it stops with an error saying the name \"could not be used for a new worktree\".\n\n- Removing a worktree now looks at what the worktree is pointing at (its own branch, another branch, or no branch) to count its commits, instead of counting only from its latest commit. This deeper check is controlled by a server-side setting.\n\n- A new option controls keeping worktrees inside a given folder.\n\n**Why**\n\nThis reduces worktree name clashes and the chance of removing a worktree that holds commits you still need.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}