You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: "Open in VS Code" on an SSH environment drops the SSH username, so the editor logs in as the local OS user #14102
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
On Windows, in the T3 Code desktop app, add a remote environment over SSH (Settings → Connections) using a username that differs from the local Windows username, e.g. host 192.168.1.172 with username admin-user (or admin-user@192.168.1.172). The host is not in ~/.ssh/config.
The environment connects fine, since T3's own SSH tunnel uses admin-user@192.168.1.172.
Open a project on that environment and choose "Open in → VS Code" in the chat header.
Expected behavior
VS Code Remote-SSH connects as admin-user@192.168.1.172, the same user T3 Code uses for the environment.
Actual behavior
The deep link is vscode://vscode-remote/ssh-remote+192.168.1.172/<path>, with no user in it. Remote-SSH falls back to the local Windows username (linus@192.168.1.172), which does not exist on the remote machine. The password prompt then loops with "Permission denied, please try again". VS Code's prompt only asks for a password and gives no way to change the user.
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
Windows 11, T3 Code desktop, VS Code with Remote-SSH. The remote host runs Linux.
Activity