Follow Discord
Sweep 30 Oct 2026 · 21:36Z Build v2.1.315 533 read Stable v2.1.308 Latest v2.1.314 Next v2.1.315 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.315 ·

Worktree locks can be written without running git

Behind a remote switch, Claude Code can lock a git worktree by writing git's lock file itself instead of running git worktree lock

Under the hood Internal Changes
JSON All of v2.1.315
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.315,
Internal ChangesSection of the release
What

A git worktree is an extra working copy of a repository, kept in its own folder. Locking a worktree tells git not to clean it up. Claude Code locks the worktrees it uses.

Claude Code now has a second way to do this. It checks the worktree's .git files and then writes git's lock file directly, instead of running the git worktree lock command. It also records when a lock entry could not be written or did not pass its checks. A remotely controlled switch decides which way is used.

Why

Writing the file directly saves starting a separate git process every time a worktree is locked.

See this entry in the whole of v2.1.315 →

Feedback