{"version":"2.1.283","anchor":"sandboxed-bash-commands-get-an-empty-git-credential-helper-f","canonical_anchor":"sandboxed-bash-commands-get-an-empty-git-credential-helper-f","heading":"Sandboxed git commands no longer use your stored credentials for the sandbox proxy","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/sandboxed-bash-commands-get-an-empty-git-credential-helper-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Sandboxed git commands no longer use your stored credentials for the sandbox proxy\n\nIn the sandbox, git is now told to use no credential helper for the local sandbox proxy when that proxy requires a token\n\n**Unclear.** Another condition that can stop this setting from being passed has not been identified.\n\n**What**\n\nClaude Code can run shell commands in a sandbox, a fenced-off environment that limits what they can reach. Network traffic from the sandbox goes through a local proxy, a go-between program on your own machine. When a command runs in the sandbox and that proxy requires a token, Claude Code now gives git a setting that clears its credential helpers for the proxy address. A credential helper is the program git asks for stored usernames and passwords.\n\nThe proxy address uses port 3128 on Linux and WSL, and the proxy's own port elsewhere. Before, sandboxed commands got no extra git settings.\n\n**Why**\n\nThis is likely meant to stop git from sending your saved credentials to the sandbox proxy, or asking you for credentials when it talks to that proxy.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}