Repository navigation
fails to install for opencode on windows (other os's unknown) #1167
Description
Version
codebae-memory-mcp 0.9
Platform
Windows (x64)
Install channel
npm
Binary variant
standard
What happened, and what did you expect?
The install script finds claude, gemini, codex, etc but not opencode. I have both opencode cli and app installed. Tried this on two computers and the bug has been around for more than just this version. Not sure if this is windows specific or if it affects other oses too.
Reproduction
- Run codebase-memory install
Logs
Diagnostics trajectory (memory / performance / leak issues)
Project scale (if relevant)
No response
Confirmations
- I searched existing issues and this is not a duplicate.
- My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.
Activity
DeusData commentedon Jul 19, 2026
Thanks for the Windows reproduction across two machines. I have placed this in
0.9.1-rcas a high-priority installer/integration bug and linked it under #395. We will verify detection for both the OpenCode CLI and desktop app rather than inferring installation from unrelated configuration state.DeusData commentedon Aug 14, 2026
Thanks @spam0115 — two machines, both the OpenCode CLI and the app installed, and your note that this predates 0.9 all matched what later reports showed. Your report was right and our
PATHEXTfix was not the whole story.Nothing here has been waiting on you. Honest status: the Windows detection path still has at least one live failure mode, and the fix needs to distinguish the actual install source and shim shape instead of assuming an extension probe finds it.
Tonight's v0.10.5 is being cut for the issues that make cbm unusable, and an installer that silently skips the agent you work in qualifies. Sorry it has taken this long for something you reported cleanly the first time.
DeusData commentedon Oct 1, 2026
Thank you @spam0115, and sorry this took so long. Your detail that Claude, Gemini and Codex were found but OpenCode wasn't pointed straight at the cause. Those three are detected from their folders, while in 0.9.0 OpenCode was only detected from its config file or from
opencodeon PATH.Two changes cover it:
%USERPROFILE%\.local\share\opencode. Both the OpenCode CLI and the Desktop app create that folder, so detection no longer depends on PATH. Config still goes to%USERPROFILE%\.config\opencode\opencode.json, the file OpenCode reads.We'll close this once both have landed. Thanks again for the clear report!
Merge pull request #2468 from DeusData/fix/issue-1167-1180-client-detect
fix(cli): client detection for OpenCode, Hermes, Claude (DeusData#1167,
DeusData commentedon Oct 19, 2026
Thank you for the two-machine OpenCode report. The last update identified the data-folder detection and long-PATH fixes separately. I have no new end-to-end Windows confirmation to add, so I am not treating either change alone as proof that your setup is resolved.