Enter Existing Worktrees#
What's wrong with this entry?
The EnterWorktree tool now accepts a path parameter to switch into an existing linked worktree instead of always creating a new one.
/worktree # create a new worktree (existing behavior)
# or, via the model:
EnterWorktree(path: "/path/to/existing-worktree")- The
pathmust be a registered worktree of the current repo (shown bygit worktree list) - Mutually exclusive with the
nameparameter — 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"
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.