microsoft / microsoft/vscode-remote-release

Command WSL: Connect to WSL in New Window not found when connected via Remote - SSH

Open
#11,437 4 comments 2 reactions 1 assignee View on GitHub

@aeschli is already working on this.

Since Jan 18, 2026.

bug wsl
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Type: Bug

Description:
When VS Code is connected to a remote host using the Remote - SSH extension, the command “WSL: Connect to WSL in New Window” is not available and attempting to run it from the Command Palette results in an error message stating that the command cannot be found.

Expected behavior:
The command WSL: Connect to WSL in New Window should be available (or at least handled gracefully) even when VS Code is currently connected via Remote - SSH, allowing the user to open a new window connected to WSL.

Actual behavior:
Running the command from the Command Palette results in the following error message:

Command 'remote-wsl.connectInNewWindow' not found. (see attached picture)

Steps to reproduce:

  1. Open VS Code on Windows.

  2. Connect to any remote system using the Remote - SSH extension.

  3. Open the Command Palette (Ctrl+Shift+P).

  4. Run WSL: Connect to WSL in New Window.

  5. Observe the error message that the command is not found.

Environment:

OS (runs VS Code): Windows 11 25H2 (build 26200.7623)
VS Code: 1.108.1
WSL extension: 0.104.3
Remote - SSH extension: 0.122.0

Notes:
This looks like a command registration / activation issue: the WSL extension’s commands appear to be unavailable when VS Code is already operating in a Remote - SSH context, instead of opening a new local window connected to WSL or showing a clearer message.

Extension version: 0.104.3
VS Code version: Code 1.108.1 (585eba7c0c34fd6b30faac7c62a42050bfbc0086, 2026-01-14T14:55:44.241Z)
OS version: Windows_NT x64 10.0.26200
Modes:
Remote OS version: Linux x64 6.6.87.2-microsoft-standard-WSL2

System Info
Item Value
CPUs AMD Ryzen 7 9700X 8-Core Processor (16 x 3800)
GPU Status 2d_canvas: enabled
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 47.16GB (26.70GB free)
Process Argv --crash-reporter-id 91e18c2e-6c46-49bd-897e-2f7c94bf1dbf --crash-reporter-id 91e18c2e-6c46-49bd-897e-2f7c94bf1dbf
Screen Reader no
VM 31%
Item Value
Remote SSH: wsl
OS Linux x64 6.6.87.2-microsoft-standard-WSL2
CPUs AMD Ryzen 7 9700X 8-Core Processor (4 x 0)
Memory (System) 3.83GB (2.57GB free)
VM 0%
A/B Experiments
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31436602
aj953862:31281341
6abeh943:31336334
editstats-enabled:31346257
cloudbuttont:31379625
3efgi100_wstrepl:31403338
use-responses-api:31390855
6j29d282:31407606
ec5jj548:31422691
cmp-ext-treat:31426748
cp_cls_t_966_ss:31446430
c0683394:31419495
ge8j1254_inline_auto_hint_haiku:31427726
nes-autoexp-10:31446583
a5gib710:31434435
38bie571_auto:31426784
rename_enabled:31436409
7a04d226_do_not_restore_last_panel_session:31438103
anthropic_thinking_t:31432745
g4jhe704_grok:31446852
cp_cls_c_1081:31443829
copilot-nes-callisto-trt:31434412
statuswidget:31442215
nes-slash-models-on:31441832
nes-set-to-on:31441941
a43f0575b:31442825
ts_provider_enabled:31446104
nes-conv-1-3:31447850

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.