# NousResearch/hermes-agent · WSL path bridge incorrectly triggered for remote bot profiles

## Open now

- 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.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #113440. Verify it addresses your case.
- **Recommended:** read PR #113440 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-113440`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #102868: Desktop: Bots profile on remote (SSH) backend spawns wsl.exe on WSL-less Windows

## Prior & competing PRs

- **#113440: fix(bot-mode): opening a bot on a remote connection no longer spawns wsl.exe on Windows (#102868, salvage #102882)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `apps/desktop/electron/main.ts`
- **#102882: fix(desktop): disable WSL path bridge for registry SSH/remote/cloud profiles**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `1f091cb4e481`, `#113440`
- **#102888: fix(desktop): register WSL-bridge state for v2-registry bots (#102868)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `1f091cb4e481`, `#113440`

## Fix status

- Merged to main in PR #113440 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-16`.