LSP server binary resolution fails on Windows
Cluster 86445 · agent/lsp. Data as of
Nothing open on GitHub. Fix merged in #115716 on 19 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #115716. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115716. That is separate from the fix event. - Still open
- Nothing open on GitHub.
On Windows, LSP server resolution incorrectly picks an extension-less POSIX shim instead of the proper .cmd wrapper, causing WinError 193. Related fixes attempt to adjust probe order to prefer Windows-compatible suffixes.
Open issues0
Open PRs0
Fixes on record
-
#115716 fix(lsp): Windows resolves the runnable .cmd wrapper instead of npm's POSIX shim, no more WinError 193 (#86445, salvage #73088)
files:
agent/lsp/install.py,agent/lsp/servers.py,contributors/emails/[redacted:email],tests/agent/lsp/test_windows_binary_resolution.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#86456 fix(lsp): probe Windows wrapper suffixes before the extension-less shim (#86445) · superseded by another PR →
#63896,#86445
Closed issues · 1
- Closed#86445Windows: LSP server resolution picks the POSIX shim and fails with WinError 193
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.67: 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
- Subsystem
- agent/lsp
- Merged PRs
- #115716
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026