OpenCode plugin installation silently fails

[DenisBalan]

Description

opencode version 1.15.10

when trying to install plugin it says "Package has no TUI target to load in this app."

guessing its related to latest opencode plugin model updates

Steps to reproduce

1. install memsearch latest
2. open opencode latest
3. install plugin
4. receive error

Error output / logs

"Package has no TUI target to load in this app"

memsearch version

memsearch, version 0.4.4

Operating system

Linux

Python version

Python 3.12.3

[zc277584121]

Thanks for the report. I checked this against OpenCode 1.15.10 with a clean temporary config directory. Installing from the CLI succeeds for me:

opencode plugin @zilliz/memsearch-opencode --global --force

The installer reports a detected server target and writes the plugin entry to opencode.jsonc:

{
  "plugin": ["@zilliz/memsearch-opencode"]
}

I also found the exact message Package has no TUI target to load in this app in OpenCode 1.15.10. It appears to come from the TUI plugin-install flow after package installation, when OpenCode tries to hot-load a TUI target into the current app. The memsearch plugin is a runtime/server plugin, not a TUI UI extension, so having no TUI target is expected. The confusing part is that the TUI message can look like a failed install even though the runtime plugin may have been added to config successfully.

Could you confirm two details?

1. Did you install from inside the OpenCode TUI plugin command/palette, or with the CLI command above?
2. After the message appears, does your OpenCode config contain @zilliz/memsearch-opencode, and does restarting OpenCode load the memory tools?

If the CLI install + restart works, this is probably a documentation/UX issue around OpenCode's TUI hot-load message. If it still does not load after restart, please share the resulting OpenCode config file and any --print-logs output so we can trace the runtime plugin loading path.

[DenisBalan]

thx for checking

1. installed from UI gives that error, while installing from configuration file is fine (ie no error)
2. yes it worked
   i installed with uv memsearch and configured with opencode.jsonc

seems its working but ux could be quite improved