bug: Terminal being created on every connection using Windsurf and Antigravity

[Sharpz7]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Closing the terminal closes the SSH connection

Relevant Log Output

Expected Behavior

No response

Steps to Reproduce

1. Connect to any workspace using Windsurf

Environment

• Host OS: Windows
• Coder version: v2.22.1

Additional Context

No response

[ethanndickson]

A user also reported this occurring with Antigravity (which makes sense given they share some source code IIRC)

[EhabY]

This seems to be an issue for Windows and the Remote SSH extension. The Coder CLI is built as a console application, so Windows creates a console window whenever it's executed, even when SSH spawns it as a ProxyCommand. The fix here must be from the CLI itself or from the remote SSH extension.

The Remote SSH extension can run the ProxyCommand with the following flag CREATE_NO_WINDOW to fix this issue.

If we want to fix it through the CLI then we can build it as a GUI application (I know, confusing), see https://dev.to/yyagi/cli-for-windows-with-go-4k2g

[ethanndickson]

For what it’s worth, this doesn’t happen on stock VS Code with the Microsoft Remote SSH extension 🤔

[EhabY]

For what it’s worth, this doesn’t happen on stock VS Code with the Microsoft Remote SSH extension 🤔

Indeed, I think the way that the VS Code Remote SSH executes the command does so without a window (or detaches from the window). I just tested VS Codium with the Open Remote SSH extension (https://github.com/jeanp413/open-remote-ssh), and it does not launch a console window. (It executes the SSH command within NodeJS so maybe that's why)

So currently the affected IDEs: Windsurf (anysphere.remote-ssh), Antigravity (google.antigravity-remote-openssh)

[EhabY]

This is an upstream issue but could be mitigated by the following CLI fix: coder/coder#24046

Closing this for now