Claude Code v2.1.105 ·
Enter Existing Worktrees
EntryKind: in v2.1.105,
New FeaturesSection of the release
What
The EnterWorktree tool now accepts a path parameter to switch into an existing linked worktree instead of always creating a new one.
Usage
/worktree # create a new worktree (existing behavior)
# or, via the model:
EnterWorktree(path: "/path/to/existing-worktree")
Details
- The
path must be a registered worktree of the current repo (shown by git worktree list) - Mutually exclusive with the
name parameter — specify one or the other - A safety check prevents removing worktrees that were entered (not created) by
EnterWorktree - The exit flow returns you to the original working directory
- New UI messages: "Entering worktree", "Cleaning up worktree (no pending changes)…", "This session entered an existing worktree"
Evidence
Worktree path parameter (search for "Path to an existing worktree") and enter-existing safety check (search for "enteredExisting")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded path parameter to the EnterWorktree tool to switch into an existing worktree of the current repository
See this entry in the whole of v2.1.105 →
