WSL cannot be used from Desktop App (with WSL server) #28799
Description
Description
Despite the fact that the desktop app can somewhat muddle its way through the WSL boundary from the host machine, using the recommended workflow of starting a server from within WSL does not work at all. This is because paths are not mapped from the host to the WSL structure. That is, OpenCode is constantly trying to open paths beginning with \\wsl.localhost despite already being inside a WSL server. Needless to say, all these operations fail. Even if the model eventually realises what is going on, and manages to find the correct local path, it seems too stupid to actually persist the path mapping it discovered in subsequent operations.
The problem ultimately seems to be that the working directory can only be set using the "open project" button, and that always displays a file system from the host's perspective; when working with a WSL server, it should display contents of the WSL server filesystem instead.
Plugins
No response
OpenCode version
1.15.7
Steps to reproduce
- Start Desktop App + WSL Server as documented.
- Open a project in WSL space
- Try to do anything at all (e.g. prompt: "what do you see?")
Screenshot and/or share link
Operating System
Windows 11
Terminal
Desktop app
Activity
github-actions commentedon May 22, 2026
This issue might be a duplicate of existing issues. Please check:
\\wsl.localhostbeing used inside a WSL server session\\wsl.localhost\— same\\wsl.localhostpath errorIf your issue covers something not addressed in those, please clarify what is different.
github-actions commentedon Jul 22, 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.