GIT_CONFIG
A Claude Code environment variable, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
Claude inspects a synced checkout's git config first and refuses to run git there if it looks unsafe.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.242.
In the changelogs
10Releases whose published page names GIT_CONFIG.
-
v2.1.305
GIT_CONFIGis now cleared only in some cases in one git runnerOne git runner now clears
GIT_CONFIGonly under certain conditions instead of always, and session setup gains new optionsfound in this entry's text
-
v2.1.296
Git commands run by Claude Code no longer inherit GIT_CONFIG
Claude Code clears any
GIT_CONFIGvariable before running git, and now comparesANTHROPIC_CUSTOM_HEADERSwith a value from another sourcefound in this entry's text
-
v2.1.290
Shorter reasons when a shell command needs your approval
The reasons Claude Code gives for asking you to approve a shell command are shorter, with some explanations in brackets removed
found in this entry's text
-
v2.1.290
Claude Code removes more git environment variables before running git
Before running git, Claude Code now clears a wider fixed set of git environment variables, not just GIT_CONFIG and GIT_ATTR_SOURCE
found in this entry's text
-
v2.1.282
Cloud session uploads refuse when git attribute settings can't be followed
Uploading your files to a cloud session now stops with steps to fix it when git attribute settings live somewhere the upload can't read
found 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.271
Bash-tool git command parsing hardened for path/permission extraction
Bash-tool permission logic parses git commands more carefully before approving them
found in this entry's text
-
v2.1.248
Directory sync only runs the git it found when the process started
Directory sync pins git to the PATH from startup, so later PATH changes can't swap it.
found in this entry's text
-
v2.1.247
Repo git hooks are opt-in, tag pushes opt in, and
GIT_CONFIGis blockedRepo git hooks stay suppressed by default, tag pushes excepted, and GIT_CONFIG is now cleared.
named in this entry, found in this entry's text
-
v2.1.242
Claude checks a checkout's git configuration before running git in it
Claude inspects a synced checkout's git config first and refuses to run git there if it looks unsafe.
found in this entry's text
First cited
2The earliest release whose published evidence quoted GIT_CONFIG was v2.1.290, 5 Oct 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
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
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.