Support for running OpenCode from WSL2 on Windows

[ImMaury]

Hi! I'm currently testing the plugin on Windows with OpenCode installed in WSL2. I was wondering if there's a way to configure the plugin to run OpenCode from WSL2 instead of searching for a Windows binary?

I have OpenCode set up and working in my WSL2 environment, and I'd prefer to use that installation rather than maintaining a separate Windows installation.

[mtymek]

I don't have a windows machine to test it (and I will have limited time to play with on on VM in the next few weeks...), so perhaps you could help me with this by doing some tests?

1. My plugin won't be able to start opencode in wsl - you'll need to start it manually:

opencode serve --hostname 0.0.0.0 --port 14096 --cors app://obsidian.md

• I'm assuming that your vault is under Windows filesystem, so you need to update your plugin settings - set your "Project directory" to /mnt/c/YOUR_VAULT_DIR

Then let me know if OpenCode shows up in the UI :)
If it does, then we can automate the setup. If it doesn't, then let me know what you see in Obsidian's dev console.

[ImMaury]

Yeah OpenCode shows up in the UI but I can see two issues:

• I can't set the Project directory in the settings, it says "Project directory does not exist"
• Agents can't run commands in OpenCode (ENOENT no such file or directory, posix_spawn '/bin/bash')

[mtymek]

I'm checking some options but I can't do much without proper test setup - I'll likely have some time for it in Feb. So, best to use OpenCode from Windows.

Or, perhaps you'd want to give a shot at fixing this and submitting a PR?

[devinlzai]

Enable custom command
The openCode path is implemented through a wsl command connection.
The absolute path for installation using the internal openCode.
Note that the hostname needs to be 0.0.0.0
The above is 127.0.0.1
The ports need to be consistent.
eg:
wsl /home/xxxx/.opencode/bin/opencode serve --port 14096 --hostname 0.0.0.0 --cors app://obsidian.md

[ImMaury]

@devinlzai Thanks! I tested this more.

The command works when I run it manually from Windows cmd.exe, for example:

wsl -- /usr/bin/env SHELL=/usr/bin/bash PATH=/home/<user>/.nvm/versions/node/v24.15.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TMPDIR=/tmp TEMP=/tmp TMP=/tmp /home/<user>/.nvm/versions/node/v24.15.0/bin/opencode serve --port 14096 --hostname 0.0.0.0 --cors app://obsidian.md

But running the same command from inside Obsidian via the plugin's custom command fails for me.

I think the custom command itself is valid. The failure seems to come from how the plugin spawns it. With projectDirectory manually set in .obsidian/plugins/opencode-obsidian/data.json to:

/mnt/c/Users/<user>/vault

the plugin calls the custom command with that value as cwd. Since the plugin is running inside Windows Obsidian, Windows cannot use /mnt/c/... as a process working directory, so process creation fails with ENOENT.

The plugin then reports this as:

Executable not found: <custom command>

but I think the missing path is the cwd, not necessarily the wsl executable.

The broader issue seems to be Windows-vs-WSL project directory handling:

• Obsidian runs on Windows and sees the vault as C:\Users\<user>\vault
• OpenCode runs inside WSL and needs /mnt/c/Users/<user>/vault
• if projectDirectory is empty, the plugin sends/uses the Windows path and OpenCode can end up with malformed paths like /mnt/c/Users/<user>/vault/C:/Users/<user>/vault
• if I set projectDirectory to /mnt/c/Users/<user>/vault through the plugin UI, it is rejected because Windows says the path does not exist
• if I manually edit data.json and set projectDirectory to /mnt/c/Users/<user>/vault, the WSL-side path is correct, but the plugin cannot reliably launch the custom command because it tries to use that WSL path as the Windows cwd

So custom command support solves the executable path part, but not the Windows-vs-WSL project directory part.

I think full WSL support may need separate values for:

• Windows cwd used when spawning the custom command
• OpenCode project directory sent to the server
• optional path mapping from C:\... to /mnt/c/...

[yang-neu]

Hi,
I tried useing the following custom command, since keeping a terminal window open is required to keep the WSL service running in the background:
wt.exe --size 60,3 --pos 10,10 -- wsl.exe -- bash -lc "/home/<YOUR NAME>/.opencode/bin/opencode serve --port 14096 --hostname 127.0.0.1 --cors app://obsidian.md"
However, because it takes a moment to spin up the server for the first time, you will need to click "Retry" once you see the following message in the terminal window:
Warning: OPENCODE_SERVER_PASSWORD is not set; server is unsecured. opencode server listening on http://127.0.0.1:14096