Installation in OpenCode: how to test if it works

[marcelloh]

I did add this:
{ "plugin": ["@zilliz/memsearch-opencode"] }
and when I start opencode i see some bin/bash message but then opencode kicks in and it is gone.
With a trick I managed to capture it:

/bin/bash: ~.cache\opencode\packages@zilliz\memsearch-opencode@latest\node_modules@zilliz\memsearch-opencode\scripts\derive-collection.sh: No such file or directory

Do I need to do more than just changing the opencode config?

[zc277584121]

Thanks for the report! A couple of quick findings before I dig deeper:

1. I downloaded the published @zilliz/memsearch-opencode@0.1.1 tarball from npm and confirmed scripts/derive-collection.sh is included in the package, so this isn't a missing-file issue.

2. The path in your error message uses backslashes throughout — ~\.cache\opencode\packages\@zilliz\memsearch-opencode@latest\node_modules\... — which strongly suggests you're on Windows. If so, the likely root cause is that the plugin invokes the script via execSync(\bash "${script}" ...`)`, and bash on Windows (Git Bash / MSYS) interprets the backslashes in the path as escape characters, so the file can't be found.

Could you confirm:

• Are you running on Windows? If yes, which shell environment (Git Bash / MSYS2 / WSL / Cygwin)?
• Is bash on your PATH, and which one (where bash)?

If you're on Linux/macOS instead, please share the output of ls ~/.cache/opencode/packages/@zilliz/memsearch-opencode@latest/node_modules/@zilliz/memsearch-opencode/scripts/ so we can see what's actually installed.

[marcelloh]

Yes, it is windows 11
no shell

[zc277584121]

Thanks for confirming — that matches what the error path showed.

Unfortunately Windows support for this plugin is going to be tricky. The current @zilliz/memsearch-opencode shells out to external bash and python3 scripts for collection-name derivation, transcript parsing, and the auto-capture daemon, which assumes a POSIX environment (Git Bash / WSL / macOS / Linux). On a plain Windows install with no shell, those calls just can't work as they are today.

A proper fix would mean rewriting those scripts inline in the TypeScript plugin so there are no external shell/Python dependencies. That's on our radar but it's a larger piece of work and won't land in the next release.

In the meantime, if you want to try it out on the same machine, the pragmatic workaround is to install WSL2 and run OpenCode from inside the WSL shell — everything should Just Work there. Alternatively, Git Bash (from Git for Windows) can work, but you may still hit path-escaping issues we haven't fully validated.

I'll leave this issue open to track native-Windows support. Thanks again for the detailed report.