-
Notifications
You must be signed in to change notification settings - Fork 396
Description
Type: Feature Request
I have a frequent use case where the current behavior appears strange to me.
When I connect to a new container from WSL, that works fine. Often I now want to connect to the same container in a new window.
My expectation is that I should be able to do "New Window" or similar from the menu. This doesn't work because you end up in Vs Code Windows.
If you connect to WSL and then try to connect to the container, you have two choices: "connect in current window" or "connect in new window".
Both will only take you to the existing workspace.
The only way to achieve my goal is to temporarily change folder in the existing window. Now Vs Code will have cached that I have two workspaces.
So the next time when I try to connect from WSL I can choose between these, and now I can finally have two windows of Vs Code connected to the same container.
But this seems really strange and awkward. Can't it be made simpler?
Extension version: 0.431.1
VS Code version: Code 1.106.1 (cb1933bbc38d329b3595673a600fab5c7368f0a7, 2025-11-16T10:20:23.745Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 6.6.87.1-microsoft-standard-WSL2
Remote OS version: Linux x64 6.6.87.1-microsoft-standard-WSL2