[Bug]: Open in code editor discards the hostname the client paired through and links to an unresolvable <hostname>.local #10906

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Run a T3 Code server on a machine that has sshd but no Tailscale, reachable by a real DNS name. Mine is an exe.dev VM with machine hostname myvm, reachable as myvm.exe.xyz.
2. From a client on another network, pair by that name, e.g. https://myvm.exe.xyz.
3. Open any thread and click Open in VS Code.

Expected behavior

VS Code opens the project over Remote-SSH on myvm.exe.xyz. The client is already talking to the server by that name, and SSH to it works from the same machine.

Actual behavior

VS Code launches with vscode://vscode-remote/ssh-remote+myvm.local/... and fails:

Could not establish connection to "myvm.local": Could not resolve hostname.

myvm.local is the mDNS fallback the server advertises. It only resolves on the server's own LAN, which a cloud VM does not share with any client. Nothing in the UI shows which host will be used before clicking.

Impact

Major degradation or frequent failure

Version or commit

main @ 6c58362 (desktop 0.0.40, nightly v0.0.41-nightly.20260909.1439)

Environment

Server: Linux VM on exe.dev, hostname myvm, sshd listening, no Tailscale. Client: macOS 26.5, <desktop app / Chrome — fill in>, paired via https://myvm.exe.xyz.

Logs or stack traces

VS Code Remote-SSH output:


Error: OfflineError (Could not resolve hostname)

Screenshots, recordings, or supporting files

No response

Workaround

Add an alias in ~/.ssh/config on each client machine so the guessed name resolves through ssh config instead of DNS:

Host myvm.local
  HostName myvm.exe.xyz
  User <ssh user>