{"version":"2.1.283","anchor":"eval-confined-subprocess-env-blanks-git-proxy-command","canonical_anchor":"eval-confined-subprocess-env-blanks-git-proxy-command","heading":"Git in confined evaluation runs no longer inherits a proxy command","tier":"internal","area":"Git","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/eval-confined-subprocess-env-blanks-git-proxy-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Git in confined evaluation runs no longer inherits a proxy command\n\nConfined evaluation runs now set `GIT_PROXY_COMMAND` to empty, so git cannot run a proxy program passed down from outside\n\n**Unclear.** It is not settled whether `GIT_PROXY_COMMAND` was already cleared elsewhere, or what the extra git config values now contain.\n\n**What**\n\nWhen Claude Code runs in a confined evaluation mode, it builds a restricted set of environment variables for the programs it starts. Environment variables are named values handed to a program when it starts. That set now:\n\n- Sets `GIT_PROXY_COMMAND` to an empty value, next to `GIT_CONFIG_NOSYSTEM=1`.\n\n- Works out its list of extra git config values when it runs instead of using a fixed list.\n\n**Why**\n\n`GIT_PROXY_COMMAND` names a program git runs to make network connections. Clearing it stops git inside a confined run from starting a proxy program inherited from the surrounding environment.\n\n- Area: Git\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}