{"version":"2.1.323","anchor":"workflow-tool-call-refused-when-the-same-turn-read-ahead-sto","canonical_anchor":"workflow-tool-call-refused-when-the-same-turn-read-ahead-sto","heading":"Deleting worktree branches now refuses unsafe names and targets","tier":"notice","area":"Worktrees","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/workflow-tool-call-refused-when-the-same-turn-read-ahead-sto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Deleting worktree branches now refuses unsafe names and targets\n\nClaude Code now refuses to delete a worktree branch with an odd name or a target that could make git write outside the repository\n\n**What**\n\nA worktree is a separate copy of your git repository in its own folder, on its own branch. Several things around worktrees changed:\n\n- Deleting a worktree branch now refuses a saved branch name with characters a worktree branch never has.\n\n- The branch is kept when deleting it could make git write outside the repository.\n\n- When a worktree is kept, a failure to move into its folder is now reported.\n\n- Creating a worktree can skip resetting an existing one to a fresh starting point, and says when it did.\n\n- The tmux launcher now passes `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` as an environment setting at the start of the command.\n\nBefore, 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\".\n\n**Why**\n\nA crafted branch name or branch target can no longer trick git into writing files outside your repository when a worktree is removed.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}