"install" command does not work for opencode in windows 11

[Icaruk]

codebase-memory-mcp install

codebase-memory-mcp install 0.6.0

Error: Argument or option not valid - "eq".
Write"TASKKILL /?" for use.
Detected agents: Claude-Code VS-Code

Claude Code:
  skills: 0 installed
  mcp: C:/Users/Icaruk/.claude/.mcp.json
  mcp: C:/Users/Icaruk/.claude.json
  hooks: PreToolUse (code discovery gate)
  hooks: SessionStart (MCP usage reminder on startup/resume/clear/compact)
VS Code:
  mcp: C:/Users/Icaruk/AppData/Roaming/Code/User/mcp.json

PATH already includes C:/Users/Icaruk/.local/bin

Install complete. Restart your shell or run:
  source C:/Users/Icaruk/.profile

opencode -v

1.3.17

pwsh -v

7.6.0

(gcm opencode).Source

C:\Users\Icaruk\AppData\Local\mise\installs\npm-opencode-ai\1.3.17\opencode.ps1

---

claude code is not installed.
Opencode is installed using mise, maybe that makes opencode not detectable?

[DeusData]

Hey, thx for reporting 🙏 Will tackle this asap after the 15th. Hope you can wait until then

[ipatalas]

I am experiencing exactly the same. Just tried installing codebase-memory-mcp and it doesn't see my opencode.
My opencode is installed via scoop package manager. I don't know how the detection work but I have opencode files in the following directories:

%USERPROFILE%\.config\opencode
%USERPROFILE%\.local\share\opencode\

However it's not added to my Apps & Features so if detection works by checking the registry then I guess that's the reason.
I use Windows 11 25H2 and Opencode 1.4.6.
Happy to help debugging if you can't reproduce.

[DeusData]

Two distinct problems in your report:

1. Error: Argument or option not valid - "eq" (TASKKILL). That came from the install step killing stale MCP processes via a shell taskkill /FI "IMAGENAME eq …" string that got re-split on Windows. On current main this runs through _spawnvp with a proper argv array (no shell re-parsing), so the "eq" error should be gone. Please confirm on v0.7.0.

2. opencode not detected (installed via mise). Root cause: find_in_path only probed the bare name opencode, but on Windows the executable is a opencode.cmd/.ps1/.exe shim — so it was invisible. Fixed: find_in_path now also tries .exe/.cmd/.bat/.ps1 per PATH entry (commit just pushed).

Could you retest install on v0.7.0? If opencode still isn't detected, please share (gcm opencode).Source (you already did — …\mise\…\opencode.ps1) and whether that dir is on %PATH%. Keeping open pending your retest. 🙏

[DeusData]

Thanks for the report. Root cause: find_in_path (used to discover CLIs like opencode during install) only probed the bare executable name. On Windows, executables carry an extension and CLIs are commonly installed as .cmd/.ps1/.exe shims (via mise, npm, etc.), so the bare-name probe never matched — opencode was present on PATH but the installer couldn't find it.

Fixed in commit 0485d3f: on Windows, find_in_path now probes the common PATHEXT variants (.exe, .cmd, .bat, .ps1) for each PATH entry before moving on.

Verified compiling and passing on Windows in CI (the build-windows and test-windows jobs are green with this change). This ships in the next release — after updating, install should discover opencode on Windows 11. Thanks again!

[C3ntraX]

@DeusData is this released in 0.7.0 ?

I have the same issue:

I tried to install it, after the quick install without ui failed too

[C3ntraX]

Okay, some more Info:
I uninstalled, cleaned everything and installed the non ui version again (0.8.1) - same errror:

Then I used the install command - same error:

But somehow, the agent was added to the "msp.json"

And it worked somehow?

[DeusData]

Thanks for the thorough follow-up and screenshots — and for retesting on 0.8.1. Will investigate the Windows install error path; the fact that the mcp.json entry lands correctly despite the error is a useful clue.