Description
When using the OpenCode desktop app on Windows with WSL mode enabled, MCP servers configured as 'local' type appear disconnected in the UI, even though they work correctly when using the CLI inside WSL.
Steps to Reproduce
- Install OpenCode desktop on Windows
- Enable WSL mode in the desktop settings
- Configure an MCP server with a local command that references a Linux/WSL executable
- Observe that the MCP server shows as disconnected in the desktop status popover
- Run the same opencode configuration from the CLI inside WSL — the MCP server connects successfully
Expected Behavior
MCP servers should connect successfully when WSL mode is enabled in the desktop app.
Actual Behavior
MCP servers fail to connect because the sidecar process runs natively on Windows and cannot execute Linux/WSL binaries referenced in MCP commands.
Environment
- OS: Windows (with WSL2)
- OpenCode Desktop
- WSL mode: Enabled
Description
When using the OpenCode desktop app on Windows with WSL mode enabled, MCP servers configured as 'local' type appear disconnected in the UI, even though they work correctly when using the CLI inside WSL.
Steps to Reproduce
Expected Behavior
MCP servers should connect successfully when WSL mode is enabled in the desktop app.
Actual Behavior
MCP servers fail to connect because the sidecar process runs natively on Windows and cannot execute Linux/WSL binaries referenced in MCP commands.
Environment