Worktree Support for Non-Git VCS / Claude Code v2.1.85

The --worktree flag now provides a clear error and migration path for non-git repositories: "Configure a WorktreeCreate hook in settings.json to use --worktree with other VCS systems."

Evidence

Worktree hook suggestion (search for "Configure a WorktreeCreate hook")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed --worktree exiting with an error in non-git repositories before the WorktreeCreate hook could run

See this entry in the whole of v2.1.85 →

The build it came inv2.1.85

26 Mar 2026 · 20 entries, this one is #13.

Either side of it

v2.1.84Older
v2.1.86Newer

Open the release →

Names in this entry

cli--worktree
Start Claude in an isolated git worktree at <repo>/.claude/worktrees/<name>. If you don't give a name, Claude Code generates one. Pass #<number>, a GitHub pull request URL, or a GitLab merge request URL to fetch that PR or MR from origin and branch the worktree from it. Branching from a GitLab merge request requires Claude Code v2.1.233 or later
hookWorktreeCreate
When a worktree is being created via --worktree, isolation: "worktree", or for a background session. Replaces default git behavior
settingsettings.json
Resumed sessions now carry your settings files along, with plugin registrations stripped out.

Anthropic's note

Upstream's own release notes for v2.1.85 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed --worktree exiting with an error in non-git repositories before the WorktreeCreate hook could run

Is this right?