Claude Code v2.1.274 · 16 Sep 2026
Git env allowlist changed: config-override vars removed, namespace/worktree vars added
The GIT_* environment variables Claude Code sanitizes before running git changed: config-override vars dropped, namespace/worktree vars added
Under the hood Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
1 Signal: worth watching, 1 to 5
Git Security Area: what it touches
Improvements Kind: in v2.1.274, 16 Sep 26
Improvements Section of the release
Unclear It isn't clear why the config-override variables, previously called out for safety reasons, were removed from this list.
What
The set of GIT_* environment variables that Claude Code scrubs before running git commands changed:
Why
This changes exactly which environment-based ways of redirecting a git command's behavior Claude Code sanitizes against before running it, dropping the config-override variables from the list and adding namespace and work-tree ones instead.
How sure we are
Something disagrees Something we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt It isn't clear why the config-override variables, previously called out for safety reasons, were removed from this list.
See this entry in the whole of v2.1.274 →
16 Sep 2026 · 324 entries, this one is #134.
Use it now23 You'll notice109 Nothing to try yet25 Under the hood167
Open the release →
Names in this entry
env GIT_CONFIG_COUNT Stray git environment variables in your shell can no longer misdirect worktree operations.
env GIT_CONFIG_GLOBAL Git calls in the sync path now respect your custom global and system config paths.
env GIT_CONFIG_SYSTEM Git calls in the sync path now respect your custom global and system config paths.
env GIT_CONFIG Claude inspects a synced checkout's git config first and refuses to run git there if it looks unsafe.
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 133 of 324
New version-mismatch update prompt
You'll notice Elsewhere
In v2.1.274 Improvements release-page order
Next → · 135 of 324
Certificate errors now classified for cert-chain failures
Under the hood Elsewhere