{"version":"2.1.304","anchor":"git-ssh-over-sandbox-proxy-on-macos","canonical_anchor":"git-ssh-over-sandbox-proxy-on-macos","heading":"Git over SSH in the macOS sandbox can go through the sandbox proxy with a credential","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/git-ssh-over-sandbox-proxy-on-macos","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Git over SSH in the macOS sandbox can go through the sandbox proxy with a credential\n\nOn macOS, sandboxed git over SSH now goes through the sandbox proxy with a credential when one is available\n\n**Unclear.** What supplies the proxy credential, and so which macOS setups use the new route, is not stated.\n\n**What**\n\nThe sandbox is a restricted environment in which Claude Code can run shell commands. Its network traffic goes through a proxy, a go-between that passes connections along. On macOS, when a proxy credential is available, the sandbox now sets `SRT_SSH_PROXY_COMMAND` and a `GIT_SSH_COMMAND` that runs it. Git then reaches SSH remotes through the proxy, passing along an encoded credential.\n\nWhen there is no credential, git over SSH still uses the earlier `nc -X 5` SOCKS proxy command.\n\n**Why**\n\nThis changes how `git` commands that use SSH connect when they run inside the sandbox on macOS. It matters if you push to or pull from SSH remotes in sandboxed shells.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}