feat(desktop): Add option to run OpenCode backend via WSL on Windows #5635
Description
Summary
Windows users who prefer WSL for their development environment currently cannot use the Desktop app effectively. The Desktop app only spawns a native Windows sidecar binary, but many developers have their projects and tooling inside WSL.
Current Behavior
The Tauri desktop app spawns OpenCode as a native Windows binary via the sidecar mechanism:
packages/tauri/src-tauri/src/lib.rs:64-91-spawn_sidecar()always uses native binarypackages/tauri/scripts/utils.ts:3-24- Only defines native platform targets
Proposed Solutions
Option A: Settings Toggle (Recommended)
Add a settings UI that allows users to choose their backend:
- Native (default) - Use bundled sidecar binary
- WSL - Run
wsl -e opencode serve --port=PORT - Custom command - Power users specify their own command
The setting would persist in app config and be read at startup.
Implementation:
- Enable the currently disabled Settings button in
layout.tsx:536-546 - Add settings modal with backend configuration
- Modify
spawn_sidecar()to check config and use appropriate spawn method - For WSL: use
Command::new("wsl").args(["-e", "opencode", "serve", ...])instead of sidecar
Option B: Auto-Detection
Detect if the opened project folder is inside WSL (path starts with \\wsl$\ or /mnt/) and automatically use WSL backend for those projects.
Pros: Zero configuration
Cons: May not match user intent, harder to implement reliably
Option C: Environment Variable Override
Support OPENCODE_BACKEND=wsl environment variable that changes spawn behavior.
Pros: Simple implementation
Cons: Not user-friendly, requires launching from terminal
Additional Context
Related WSL issues (different problems):
- /editor: non-successful editor exits should keep the text in the textarea #693 - TUI rendering in WSL
- fix: Copilot Premium Requests #595 - Paste issues in WSL terminal
This issue is specifically about the Desktop app being able to launch the OpenCode server via WSL rather than native Windows.
Use Case
- User has projects inside WSL filesystem
- User installs OpenCode Desktop on Windows
- User wants Desktop UI but with OpenCode running inside WSL (for proper file access, tooling, etc.)
Activity
github-actions commentedon Dec 16, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if your specific WSL use case differs from these requests.
Brendonovich commentedon Dec 17, 2025
Desktop's windows build currently bundles
opencode-windows-x64to run the server. Would doing this WSL integration properly require running theopencode-linux-x64build, or would just running the Windows binary within the WSL shell work?AaronFeledy commentedon Feb 4, 2026
It would need to run the linux binary in WSL. VSCode handles this by downloading its linux binary into WSL when you enable WSL integration in the windows app.
Brendonovich commentedon Feb 4, 2026
Good to know, so we'll likely need to download
opencode-linux-x64and then launch that inside WSLBrendonovich commentedon Feb 11, 2026
#12914 provides a toggle that will download + launch the OC server in WSL once the app is restarted, will be out in the next release.
jairbj commentedon Mar 1, 2026
It looks like it was disabled in 1.2.7.
wbdb commentedon Mar 20, 2026
That would be a great function, especially since it is also known from the Codex Windows app.
Step 1: Check whether
opencodeis already available in WSLPATH. If needed, also verify the installation directory.curl -fsSL https://opencode.ai/install | bashStep 2: If the environment variable is not already set, start opencode with a random password:
OPENCODE_SERVER_PASSWORD='my random pw' opencode serve --hostname 0.0.0.0Step 3: Connect to the OpenCode instance running in WSL from the Windows desktop app - the documentation doesn't say much about how to do this exactly (Password) - https://opencode.ai/docs/de/windows-wsl/
I'm currently using the detour via a .bat file:
Ausoj commentedon Apr 4, 2026
The workaround @wbdb provided does not seem to work for me.
Trying to do it like that always resulted in opencode getting back mangled directory paths and not being able to properly map sessions between wsl and windows paths.
Still hoping for a fix for this issue as right now opencode desktop for windows is unusable when wanting to work in wsl
tackleberrybey commentedon Apr 10, 2026
any update on this?
this should have been the default behaviour of the desktop app since a lot of devs on windows use wsl2 nowadays
github-actions commentedon Jul 3, 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.
PureKrome commentedon Jul 3, 2026
reopen