{"version":"2.1.285","anchor":"git-subprocess-env-git-allow-protocol-now-a-shared-value-p","canonical_anchor":"git-subprocess-env-git-allow-protocol-now-a-shared-value-p","heading":"Git's security settings changed for git commands Claude Code runs","tier":"notice","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/git-subprocess-env-git-allow-protocol-now-a-shared-value-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Git's security settings changed for git commands Claude Code runs\n\nGit commands run by Claude Code now take their allowed network protocols from a shared value and set `GIT_NO_LAZY_FETCH` and `GIT_TERMINAL_PROMPT`\n\n**Unclear.** The new value of `GIT_ALLOW_PROTOCOL` is not known.\n\n**What**\n\nThe settings Claude Code passes to some git commands it runs have changed:\n\n- `GIT_ALLOW_PROTOCOL`, which limits the network protocols git may use, is no longer fixed to \"none\" and now comes from a shared value.\n\n- One group of settings, including `GIT_LITERAL_PATHSPECS`, is replaced by `GIT_ALLOW_PROTOCOL`, `GIT_NO_LAZY_FETCH` and `GIT_TERMINAL_PROMPT`.\n\n**Why**\n\nThis changes the safety limits placed on git when Claude Code runs it.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}