GIT_CONFIG_GLOBAL
A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.202, including the newest one read.
Git calls in the sync path now respect your custom global and system config paths.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.227.
In the changelogs
11Releases whose published page names GIT_CONFIG_GLOBAL.
-
v2.1.290
Uploading a repository to a cloud session refuses more unusual setups
Uploading your git checkout to a cloud session now runs more checks and gives specific refusal messages for unusual setups
found in this entry's text
-
v2.1.282
Private git copy now declines to run under git setups it cannot reproduce
Claude Code's private copy of a repository's git directory now refuses to run when certain git environment variables or config sources are in play
found in this entry's text
-
v2.1.282
Git config location variables are now treated as file paths
Claude Code now treats
GIT_CONFIG_GLOBALandGIT_CONFIG_SYSTEMas environment variables that point to a single filefound in this entry's text, named in this entry
-
v2.1.281
Isolated git env drops GIT_CONFIG_SYSTEM, points GLOBAL at /dev/null
Claude Code's own git commands now use
GIT_CONFIG_GLOBAL=/dev/nullandGIT_CONFIG_NOSYSTEM=1, no longer settingGIT_CONFIG_SYSTEMfound in this entry's text
-
v2.1.281
Git config probe now reads GIT_CONFIG_GLOBAL / GIT_CONFIG_SYSTEM from the configured environment
Claude Code's git config check now uses
GIT_CONFIG_GLOBALandGIT_CONFIG_SYSTEMfrom the environment it was givenfound in this entry's text, named in this entry
-
v2.1.281
Windows MSYS-style paths and GIT_CONFIG_GLOBAL/SYSTEM handled in path checks
On Windows, path checks now treat
/c/...style paths asC:\..., and a new list namesGIT_CONFIG_GLOBALandGIT_CONFIG_SYSTEMfound in this entry's text
-
v2.1.274
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
found in this entry's text
-
v2.1.269
Agent proxy can now inject extra git include.path and prepend to PATH
The agent/tool proxy can now add extra git config includes and prepend a directory to PATH
found in this entry's text
-
v2.1.248
Backups of secret files are now treated as secrets
Editor swap and backup copies of credential files are now protected like the originals.
found in this entry's text
-
v2.1.242
Plugin file access is confined to the project and blocked from credential folders
Plugin file reads stay inside the project and cannot touch credential folders.
found in this entry's text
-
v2.1.227
Git calls in the sync lane keep custom config paths
Git calls in the sync path now respect your custom global and system config paths.
named in this entry, found in this entry's text
First cited
5The earliest release whose published evidence quoted GIT_CONFIG_GLOBAL was v2.1.227, 10 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
95One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.