{"version":"2.1.312","anchor":"sandbox-proxy-env-uses-127001-in-some-cases","canonical_anchor":"sandbox-proxy-env-uses-127001-in-some-cases","heading":"Sandbox proxy settings use 127.0.0.1 instead of localhost in some cases","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/sandbox-proxy-env-uses-127001-in-some-cases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Sandbox proxy settings use 127.0.0.1 instead of localhost in some cases\n\nIn the sandbox, Claude Code now points proxy variables at 127.0.0.1 instead of localhost when an authentication value is set\n\n**What**\n\nThe sandbox is a restricted environment that Claude Code can run commands in. It routes their network traffic through a proxy, a local server that the traffic passes through. Claude Code tells the commands where the proxy is by setting environment variables. When an authentication value is set, those variables now give the proxy's address as `127.0.0.1` instead of `localhost`. This applies:\n\n- Always for the HTTP proxy.\n\n- For the SOCKS proxy only when it uses the same port as the HTTP proxy.\n\nThe variables affected are `HTTP_PROXY`, `ALL_PROXY`, `GIT_SSH_COMMAND`, `DOCKER_HTTP_PROXY` and `CLOUDSDK_PROXY_ADDRESS`.\n\n**Why**\n\nSome network tools resolve `localhost` differently, which can stop them from reaching the proxy. A fixed address avoids that.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}