Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.283entry #70

Claude Code v2.1.283 ·

Git TLS settings set through environment variables now apply to Claude Code's own git commands

Certificate and TLS settings passed through GIT_CONFIG_KEY_n and GIT_CONFIG_VALUE_n now reach git commands Claude Code runs itself

Use it now Improvements
JSON All of v2.1.283
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
GitArea: what it touches
ImprovementsKind: in v2.1.283,
What probably matters to youSection of the release

Unclear Which of Claude Code's internal git commands besides the reset receive these settings is not fully known.

What

Git can take config settings from environment variables: GIT_CONFIG_COUNT, GIT_CONFIG_KEY_n and GIT_CONFIG_VALUE_n. When you set TLS settings this way, Claude Code now passes them on to the git commands it runs itself, such as a reset --hard. TLS is the encryption used for secure connections. Only http settings like these are passed on:

  • sslcainfo and sslcapath, the certificate authority bundle
  • sslverify
  • sslversion, sslcipherlist and sslbackend
  • schannelcheckrevoke and schannelusesslcainfo
  • pinnedpubkey, certificate pinning
  • proxysslcainfo

Before, those internal git commands ran without these settings.

Why

If you are behind a corporate proxy with a custom certificate bundle set through environment variables, Claude Code's own git operations could fail certificate checks. They now use the same settings as your own git commands.

Read from
Names in the bundleGIT_CONFIG_COUNTGIT_CONFIG_KEY_nGIT_CONFIG_VALUE_n
What the documentation says
Documented inclaude-code/self-hosted-environments-configuration
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up GIT_CONFIG_VALUE_n, on Customize sessions in self-hosted environments. | `GIT_CONFIG_COUNT`, `GIT_CONFIG_KEY_n`, `GIT_CONFIG_VALUE_n` | Git settings the runner fixes for the git your hook runs. [Git configuration inside lifecycle hooks](#git-configuration-inside-lifecycle-hooks) describes them. Requires Claud… self-hosted-environments-configuration see the edit
Confirmed since Anthropic's documentation has since written up GIT_CONFIG_KEY_n, on Customize sessions in self-hosted environments. | `GIT_CONFIG_COUNT`, `GIT_CONFIG_KEY_n`, `GIT_CONFIG_VALUE_n` | Git settings the runner fixes for the git your hook runs. [Git configuration inside lifecycle hooks](#git-configuration-inside-lifecycle-hooks) describes them. Requires Claud… self-hosted-environments-configuration see the edit
Confirmed since Anthropic's documentation has since written up GIT_CONFIG_COUNT, on Customize sessions in self-hosted environments. | `GIT_CONFIG_COUNT`, `GIT_CONFIG_KEY_n`, `GIT_CONFIG_VALUE_n` | Git settings the runner fixes for the git your hook runs. [Git configuration inside lifecycle hooks](#git-configuration-inside-lifecycle-hooks) describes them. Requires Claud… self-hosted-environments-configuration see the edit
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 doubtWhich of Claude Code's internal git commands besides the reset receive these settings is not fully known.
Anthropic's documentation agreesAnthropic's documentation has since written up GIT_CONFIG_COUNT, on Customize sessions in self-hosted environments.
Anthropic's release notes agreeFixed worktree checkouts failing certificate verification (for example on Git LFS downloads) when the CA certificate is passed to git as…

See this entry in the whole of v2.1.283 →

Feedback