{"version":"2.1.285","anchor":"worktree-git-fetches-use-a-shared-environment-helper","canonical_anchor":"worktree-git-fetches-use-a-shared-environment-helper","heading":"Git commands when creating a worktree now use stricter settings","tier":"notice","area":"Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/worktree-git-fetches-use-a-shared-environment-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Git commands when creating a worktree now use stricter settings\n\nCreating a worktree now runs git with a hardened set of settings, including limits on network protocols and no interactive SSH prompts\n\n**Unclear.** The full set of git commands covered by these settings is not clear.\n\n**What**\n\nA worktree is an extra working copy of a git repository. When Claude Code creates one, the git commands it runs now get their settings from a shared setup step instead of a fixed list. That setup includes stricter git settings:\n\n- `GIT_ALLOW_PROTOCOL`, which limits the network protocols git may use, now only accepts names made of letters, digits and `-`.\n\n- SSH runs in batch mode, so it will not stop to ask for input.\n\n**Why**\n\nThis tightens security around the git commands Claude Code runs for you.\n\n- Area: Worktrees\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}