Git over SSH fails in sandbox

“The nc hop sends none, and BSD nc has no way to supply a SOCKS5 or HTTP proxy password non-interactively, so the connection is refused.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/418/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 3 a week at the late-September peak. A workaround is known.

Git over SSH fails in macOS sandbox without proxy credentials. Injected GIT_SSH_COMMAND uses an nc ProxyCommand that cannot send the SOCKS5 credentials held in ALL_PROXY, so push, fetch, pull and ls-remote fail.

Is this your bug?

File my report

Where: Bash sandbox
Error text: Received disconnect from UNKNOWN port 65535:1: This proxy requires authentication, and this client did not offer an authentication method, so the connection was refused.
fatal: Could not read from remote repository.Pasted in 4 reports
Versions: 2.1.237 to 2.1.289
Platforms: macOS
How bad: Breaks a normal workflow.

Part of: Sandbox breaks git operations3 bugs

Sandbox leaves .git/config.lock4 people
Sandbox placeholder files in .git2 people

Not quite your bug?

Excluded commands stay sandboxed5 people

Original reports4, newest first

Oct 4, 2026Sandboxed git push over SSH fails: local credential proxy requires auth that injected GIT_SSH_COMMAND's nc ProxyCommand can't provide#99382
Oct 1, 2026macOS sandbox: git over SSH still fails in 2.1.284 — injected nc ProxyCommand sends no proxy credentials (fix proposal)#98752
Oct 1, 2026git over SSH always fails when sandboxed: injected GIT_SSH_COMMAND ProxyCommand omits proxy credentials#98705
Sep 30, 2026macOS sandbox git over SSH fails due to unauthenticated SOCKS5 proxy#98350