Bug: ProxyCommand spawns visible console window on Windows (CREATE_NO_WINDOW flag missing)

Google Antigravity
1

Adding to this thread with a related but distinct issue that has the same root cause.

Even after applying the workaround (setting remote.SSH.path to Git for Windows’ ssh.exe),
a console window still pops up on every connection — but this time it’s the ProxyCommand
helper (e.g. connect.exe, ncat.exe, plink.exe), not ssh.exe itself.

Reproduction:

  1. Configure ~/.ssh/config with any ProxyCommand that uses a console-subsystem helper:
    Host myhost ProxyCommand "C:\Program Files\Git\mingw64\bin\connect.exe" -S 127.0.0.1:78.. %h %p

  2. Connect via Remote-SSH.

  3. A blank console window appears for connect.exe and stays until the SSH session ends.
    Closing it kills the connection.

ncat
ncat1472×821 11.7 KB

Confirmed it is NOT the helper’s fault: I tried swapping connect.exe for ncat.exe
(from Nmap) — same popup. Any console-subsystem program does this on Windows unless the
parent process passes CREATE_NO_WINDOW (or DETACHED_PROCESS) when spawning ssh, which
then propagates to grandchild processes like ProxyCommand.

This is a known, already-fixed VSCode bug:
When using ProxyCommand in Windows when creating the tunnel a new window appears · Issue #230 · microsoft/vscode-remote-release · GitHub (filed May 2019, closed).
Upstream VSCode and forks like Cursor handle this correctly — no popup with the exact same
ssh config. Antigravity is the only fork where this regressed.

Environment:

  • OS: Windows 11
  • Antigravity: 1.23.2
  • ssh.exe: Git for Windows OpenSSH_9.9p2 (also reproduces with system OpenSSH)
  • ProxyCommand tested: connect.exe, ncat.exe — both pop windows

Request: Please apply CREATE_NO_WINDOW (or equivalent) when spawning the SSH child
process on Windows, matching upstream VSCode behavior. This is a single-flag fix and would
resolve both this issue and the original ssh.exe popup reported above.

Thanks!