Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.305,
Internal ChangesSection of the release
Unclear Only one of the conditions under which GIT_CONFIG is still cleared is known: that an access token is present.
What
In one of the git runners Claude Code uses, the GIT_CONFIG environment variable (a setting in your shell that points git at a config file) used to be cleared every time. It is now cleared only under certain conditions, one of which is that an access token is present.
Session setup also gains options for resuming in the cloud, for security warnings, and for sections that are appended to a session while it runs.
Why
These are small changes to how git and sessions are set up. Where GIT_CONFIG is not cleared, git may now follow a config file you pointed it at.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtOnly one of the conditions under which `GIT_CONFIG` is still cleared is known: that an access token is present.
Anthropic's release notes agreeSelf-hosted runner: Fixed repository access failing since 2.1.296 when a git credential helper or askpass program reads its settings through…
