You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Disable opencode cli on windws when using WSL #53952
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
First of all, thanks for your effort.
As request, It would be nice the option to disable the local server if the user is using a wsl server. In my case I have the opencode-cli.exe using 200mb of ram and little cpu. Not too much, but unnecessaryprocess in the background.
If I understand correctly, you'd like an option in OpenCode Desktop on Windows to stop starting the bundled local server (opencode-cli.exe) when you only use a WSL server, so it doesn't run in the background for nothing. I couldn't find a setting for this today: the bundled server starts no matter which server you connect to.
This can't be done as a plugin, because plugins run inside the server and the Desktop app is what starts that server. It would need a setting in Desktop itself. The maintainers will consider it.
Activity
opencode-agent commentedon Oct 8, 2026
Thanks for the suggestion, @cumal!
If I understand correctly, you'd like an option in OpenCode Desktop on Windows to stop starting the bundled local server (
opencode-cli.exe) when you only use a WSL server, so it doesn't run in the background for nothing. I couldn't find a setting for this today: the bundled server starts no matter which server you connect to.This can't be done as a plugin, because plugins run inside the server and the Desktop app is what starts that server. It would need a setting in Desktop itself. The maintainers will consider it.
Related issues:
opencode-cliservice on WindowsIt would also help to know which OpenCode Desktop version you're using (shown in the app's settings or about screen).