Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.105 Home All releases olderv2.1.104 v2.1.107newer
Claude Code v2.1.105

Enter Existing Worktrees

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.105 →