Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Deleting worktree branches now refuses unsafe names and targets

Claude Code now refuses to delete a worktree branch with an odd name or a target that could make git write outside the repository

You'll notice Improvements
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WorktreesArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
What

A worktree is a separate copy of your git repository in its own folder, on its own branch. Several things around worktrees changed:

  • Deleting a worktree branch now refuses a saved branch name with characters a worktree branch never has.
  • The branch is kept when deleting it could make git write outside the repository.
  • When a worktree is kept, a failure to move into its folder is now reported.
  • Creating a worktree can skip resetting an existing one to a fresh starting point, and says when it did.
  • The tmux launcher now passes CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG as an environment setting at the start of the command.

Before, the branch was deleted with no checks on its name or target. Separately, in this release the description of the Workflow tool now says "a message from the system" where it used to say "system-reminder".

Why

A crafted branch name or branch target can no longer trick git into writing files outside your repository when a worktree is removed.

See this entry in the whole of v2.1.323 →

Feedback