OpenCode Desktop 1.18.15 does not load opencode-nowledge-mem plugin tools or idle capture

[iamapay]

Bug

opencode-nowledge-mem is installed and registered, but OpenCode Desktop exposes no nowledge_mem_* tools and does not capture sessions after becoming idle.

The separate remote MCP connection works, nmem --json status is healthy, and manual historical sync works. This isolates the problem from API connectivity and authentication.

Reproduction

On Windows with OpenCode Desktop 1.18.15, configure a working remote Nowledge Mem client. Install opencode-nowledge-mem globally or add "plugin": ["opencode-nowledge-mem"] to the global OpenCode config. Fully restart OpenCode, create a short session, and wait for idle capture.

Expected

OpenCode exposes the plugin's nowledge_mem_* tools and uploads an opencode-... thread after idle.

Actual

No plugin tools appear. Sessions remain in OpenCode's local database. nmem threads sync --from opencode --all-projects reports them as ready; adding --apply uploads them successfully. No relevant plugin error appears in opencode.log.

Environment

Windows; OpenCode Desktop 1.18.15; opencode-nowledge-mem 0.3.5; nmem CLI 0.10.55; Nowledge Mem server 0.10.54; remote mode over Tailscale.

The npm package was force-refreshed, the plugin was reinstalled from a clean configuration, nmem.exe is in the user PATH, and OpenCode was fully restarted between tests. The behavior remained unchanged.

[wey-gu]

Thanks, this is a useful split: remote MCP/status works and manual nmem threads sync --from opencode --all-projects --apply works, but OpenCode Desktop does not register the plugin tools/hooks.

We will treat this as an OpenCode Desktop plugin discovery / hook registration issue rather than a Mem server or CLI sync issue.

For reproduction, could you share the non-secret parts of:

• where OpenCode Desktop installed or loaded opencode-nowledge-mem from;
• the OpenCode Desktop plugin/config file that enables it;
• any OpenCode Desktop plugin diagnostics/log lines around startup;
• whether the same plugin works in OpenCode CLI on the same machine, if you have tried that.

Please redact API keys, remote URLs, and private paths if needed. I will keep the issue open while we reproduce the Desktop host path.

[iamapay]

Thanks. Here are the requested details, with user-specific paths redacted.

Windows OpenCode Desktop installation

OpenCode Desktop is installed at:

%LOCALAPPDATA%\Programs\@opencode-aidesktop\OpenCode.exe

Version: 1.18.15

The Nowledge Mem plugin package is present at:

%USERPROFILE%\.cache\opencode\packages\opencode-nowledge-mem\node_modules\opencode-nowledge-mem\

Its package.json reports:

• Version: 0.3.5
• Entry point: src/index.ts
• Peer dependency: @opencode-ai/plugin ^1.3.7

The installed @opencode-ai/plugin dependency is version 1.18.15.

OpenCode configuration

Global configuration file:

%USERPROFILE%\.config\opencode\opencode.json

Relevant non-secret section:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    "opencode-nowledge-mem"
  ]
}

There is also an opencode.jsonc in the same directory containing only the schema declaration:

{
  "$schema": "https://opencode.ai/config.json"
}

The remote MCP configuration is also in opencode.json, but I have omitted it because it contains the private endpoint and API key.

Startup diagnostics

OpenCode Desktop logs to:

%USERPROFILE%\.local\share\opencode\log\opencode.log

The relevant startup sequence shows the configuration being loaded and the host bootstrapping:

level=INFO message=loading path="%USERPROFILE%\.config\opencode\config.json"
level=INFO message=loading path="%USERPROFILE%\.config\opencode\opencode.json"
level=INFO message="global event connected"
level=INFO message=bootstrapping directory="%USERPROFILE%"
level=INFO message=loading path="%USERPROFILE%\.config\opencode\opencode.jsonc"
level=INFO message=init

The same sequence then repeats initialization for the active project directories.

I could not find any line indicating that opencode-nowledge-mem was loaded, nor any plugin initialization, import, hook-registration, or capture error. Searches for [nowledge-mem], automatic OpenCode thread sync failed, and the plugin package name returned no relevant runtime diagnostics.

The npm package was force-refreshed successfully at version 0.3.5, with no reported vulnerabilities. Removing and reinstalling it, then fully restarting every OpenCode Desktop process, did not change the behavior.

OpenCode CLI comparison

I have not tested OpenCode CLI on this Windows machine because the opencode command is not installed or exposed on PATH; only OpenCode Desktop is installed.

Linux comparison

The same Nowledge Mem plugin works correctly with OpenCode Desktop on my Linux machine. On Linux, the nowledge_mem_* tools are registered and conversation capture works without this issue.

This therefore appears specific to the Windows OpenCode Desktop plugin discovery/loading path rather than the plugin package, Mem server, remote authentication, or nmem synchronization.

Additional startup observation

When opencode-nowledge-mem is enabled, OpenCode Desktop plays several error-style notification sounds during startup on both Windows and Linux. There is no visible error message or corresponding plugin error in opencode.log.

Linux still loads the plugin and captures sessions successfully despite these sounds, while Windows does not register the plugin tools or hooks. The sounds may therefore be an OpenCode Desktop startup or lifecycle notification rather than the root cause, but they could help identify where plugin discovery or initialization occurs.

[wey-gu]

Thanks, this narrows it down very well. Given:

• the package is present in %USERPROFILE%\\.cache\\opencode\\packages\\opencode-nowledge-mem\\node_modules\\opencode-nowledge-mem\\;
• OpenCode Desktop logs config loading but no plugin init/import/hook lines;
• the same package works on Linux Desktop;
• manual nmem threads sync --from opencode --all-projects --apply works;

we are treating this as a Windows Desktop package-entry loading gap, not a Mem server/auth/session-parser problem.

One packaging risk we found is that the npm package entry pointed directly at src/index.ts. That can work in hosts that load plugin packages through Bun/TypeScript-aware resolution, but it is fragile for Windows Desktop hosts that follow Node-style package entry resolution. We are changing the package so the npm main entry points at precompiled ESM JavaScript while keeping the TypeScript source in the package.

Once the next plugin package is published, please fully quit OpenCode Desktop, clear %USERPROFILE%\\.cache\\opencode, restart OpenCode Desktop, and let it reinstall opencode-nowledge-mem. If the tools still do not appear after that, the next data point we need is any Desktop error text shown during startup or a fresh startup log after the cache is rebuilt.