There is three bugs with remote ssh workspaces in vscode-windows-terminal extension:
the hostname obtained from the workspace path sometimes is not the real hostname of the remote machine.
the extension is using the windows username in the ssh communication even with linux and it should be using the predefined username in ms-vscode-remote.remote-ssh configuration file.
wt.exe does not accept ";" in ssh commands (ex wt.exe ssh ricardo@192.168.1.180 "cd ~; exec ...") it must be a bug with windows terminal.
P.S. I have a fixed this bugs and will submit them tomorrow as a pull request.
There is three bugs with remote ssh workspaces in vscode-windows-terminal extension:
P.S. I have a fixed this bugs and will submit them tomorrow as a pull request.