{"version":"2.1.305","anchor":"git-env-git-config-only-cleared-conditionally-headless-liv","canonical_anchor":"git-env-git-config-only-cleared-conditionally-headless-liv","heading":"GIT_CONFIG is now cleared only in some cases in one git runner","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/git-env-git-config-only-cleared-conditionally-headless-liv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### `GIT_CONFIG` is now cleared only in some cases in one git runner\n\nOne git runner now clears `GIT_CONFIG` only under certain conditions instead of always, and session setup gains new options\n\n**Unclear.** Only one of the conditions under which `GIT_CONFIG` is still cleared is known: that an access token is present.\n\n**What**\n\nIn 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.\n\nSession setup also gains options for resuming in the cloud, for security warnings, and for sections that are appended to a session while it runs.\n\n**Why**\n\nThese 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.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}