WSL path bridge incorrectly triggered for remote bot profiles
Cluster 102868. Data as of
Nothing open on GitHub. Fix merged in #113440 on 16 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113440. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113440. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes concern a bug where wsl.exe is spawned on Windows systems when opening bot profiles on remote, SSH, or cloud registry backends, even when WSL is absent or unnecessary. The changes disable or gate the WSL path bridge specifically for these non-local profile types.
Open issues0
Open PRs0
Fixes on record
-
#113440 fix(bot-mode): opening a bot on a remote connection no longer spawns wsl.exe on Windows (#102868, salvage #102882)
files:
apps/desktop/electron/main.ts
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#102868Desktop: Bots profile on remote (SSH) backend spawns wsl.exe on WSL-less Windows
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #113440
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 16 Sep 2026