Repository navigation
I cannot connect with WSL #30230
Description
I’m using the OpenCode Windows desktop app and I’m trying to work with OpenCode running inside WSL.
At the moment, I can’t find any option in the Windows app to change the server address, and I also don’t see any built-in option to connect directly to a WSL instance.
This is confusing because the recommended Windows setup appears to be using OpenCode with WSL, and the documentation says the desktop app should be able to connect to a server started inside WSL through http://localhost:4096 or the WSL IP address.
Steps to reproduce
- Open the OpenCode Windows desktop app.
- Try to connect the app to an OpenCode server running inside WSL.
- Look for a way to change the server address or select a WSL target.
Actual behavior
There is no visible option to change the server, and there is no clear direct connection flow for WSL.
Expected behavior
The Windows app should either:
- provide a clear way to change the server URL, or
- include a direct “Connect to WSL” option, or
- document the connection flow more clearly inside the app.
Why this matters
The current experience makes it hard to use the recommended WSL-based workflow on Windows, even though the docs explicitly describe running the server in WSL and connecting the desktop app to it.
Environment
- OS: Windows
- WSL version: 2.6.3.0
- OpenCode app version: 1.15.13
- Distro: Ubuntu
Activity
github-actions commentedon Jun 1, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is specifically about missing UI to configure the server address/URL (not the path mapping problems described in #28799), it may still be worth keeping as a separate report. Please check #28799 and let maintainers know if your issue differs.
p-hermida-emais commentedon Jun 1, 2026
I’m not sure this is an exact duplicate.
The older issues seem to be about WSL/Desktop connectivity once that flow is already available, but in my case on the current version I cannot find any visible way to change the server endpoint or explicitly connect the Desktop app to WSL, even though the docs still describe that workflow via http://localhost:4096.
Since recent versions appear to have changed Desktop behavior and introduced WSL-related backend changes, this may be a different regression or a newer UI/connection-flow issue rather than the same underlying bug.
So the symptom here is not just “WSL connection fails”, but “the current app no longer exposes a clear way to use the documented WSL server flow”.
github-actions commentedon Aug 1, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.