What
A worktree is a separate working copy of a git repository. When you leave one and keep it, the message now adds " on branch X" only when the worktree has a branch, so no empty branch name is shown.
There is also new code that would first ask a worktree created by a hook whether it moved or changed, with a "checking" state while it waits. In this build that code can never run.
Why
The keep message is accurate for worktrees without a branch. The hook check has no effect yet.
Names in the bundle/worktree
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Commands touched a line naming /worktree after this was published.
| `/batch <instruction>` | **[Skill](/docs/en/skills#bundled-skills).** Orchestrate large-scale changes across a codebase in parallel. Researches the codebase, decomposes the work into 5 to 30 independent units, and presents a plan. Once a…commands see the edit
Confirmed since
Anthropic's documentation has since written up /worktree, on Let Claude coordinate ongoing work with Projects.
* **Worktrees**: a [worktree](/docs/en/worktrees) gives each local session its own working copy of a repository so parallel sessions on your machine don't overwrite each other. Cloud threads don't need them: each clones its repositories in…claude-projects see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /worktree, on Let Claude coordinate ongoing work with Projects.