[FEATURE] Fix in built LSPs for Windows
Resolved 💬 3 comments Opened Feb 9, 2026 by privacyguy123 Closed Feb 13, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
/plugin installed official Claude Code LSPs fail on Native Windows install with "-ENOENT" trying to call "uv_spawn" on the wrong file.
Proposed Solution
Literally append ".cmd" to each LSP command if Windows environment detected - confirmed fixed on my side. I see no way to supply and "override" command to the official plugins, I had tried writing my own ".lsp.json" in there and it's ignored. I don't see where they read their cmdline from at all ... perhaps it is bundled into the Claude.exe .js file.
Alternative Solutions
Git clone official plugins, append ".cmd" to all commands, install from this new source.
Priority
High - Significant impact on productivity
Feature Category
Other
Use Case Example
- Be on Windows
- Install official LSP plugin
- Witness "error loading LSP plugin xyz"
- Check claude --debug log for "-ENOENT" described above
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗