Agents view fails to connect to SSH hosts using ProxyJump, while main editor's SSH works

[foresee-io]

• VS Code Version: 1.120.0
• OS Version: Darwin arm64 25.4.0

Steps to Reproduce:

1. Define an SSH host in ~/.ssh/config that uses ProxyJump.
2. Connect to the host via the standard editor SSH entry — works.
3. Try connecting to the same host from the new Agents view — fails with EHOSTUNREACH.

Expected:
Agents view should honor ~/.ssh/config (including ProxyJump) and connect successfully.

Actual:
Agents view cannot reach the host and immediately returns EHOSTUNREACH.

SSH config example:

host claude
    proxyJump jumpserver
    user var-x
    hostname var-c
    port 22
    identityfile var-b

host jumpserver
    user var-y
    hostname var-z
    port 22
    identityfile var-a

[skywalk72]

i have the same problem

[kristofferpeterhansel]

ProxyCommand seem to provoke the same sort of symptom.

[wdhongtw]

Have similar problem here.

In my case, I have some ProxyCommand in system global setting /etc/ssh/ssh_config,
and the Agent View fail to establish the SSH connection, while the main VS Code editor works normally.

The connection mechanism of Agent View should be aligned with Remote SSH in VS Code editor.

Version: 1.133.0 (Universal)
Commit: a5b500951314efd502d07465bd138dfbd714a960

Workaround

As a workaround, I need to first establish a SSH connection with port forwarding.

ssh -N -L 2222:localhost:22 some-host

And create another record in the SSH config to connection through this forwarded port. Like

Host some-host-local-proxy
  HostName 127.0.0.1
  Port 2222

Then connect to some-host-local-proxy in Agent View.

[wdhongtw]

Hi joshspicer , sorry for pinging. Do we have some idea or plan for this issue? 🙂‍↕️

[kondv]

I reproduced this with a real key-authenticated single-hop ProxyJump setup and opened #334849. Agent Host resolved the target with ssh -G but discarded ProxyJump, so unpatched current main dialed the unreachable HostName directly and failed with ENOTFOUND; the patched build passes native OpenSSH's -W tunnel to ssh2, reaches the jump and target, launches the real Agent Host, and completes its forwarded WebSocket connection. A direct-host control still connects without starting a jump helper, and this PR intentionally does not add ProxyCommand, multi-hop, or interactive jump-host authentication.

— kondv's Copilot 🤖