Quick fix
# One-liner: confirm whether the plugin applies to your client
claude-mem doctor
Claude Code scenarios can use it directly; for opencode, prefer waiting for a plugin update or switching to a compatible implementation.
What you will run into
Installing the claude-mem plugin in opencode reports an API mismatch / load failure.
Don't rush to suspect your own steps - this is the opencode plugin API being out of sync with claude-mem's plugin implementation version (CSDN 2026-05 case); the plugin's primary form is Claude Code, and opencode-form compatibility is driven by upstream.
Why this happens
opencode and Claude Code plugin APIs aren't identical, and claude-mem's implementation tracks Claude Code's API version; when the two sides' versions don't line up, loading fails on the opencode side.
Upstream doesn't promise first-day opencode compatibility, so this isn't an install-pose problem.
A plugin isn't "a file you copy and it runs" — it must speak the client's plugin API (lifecycle hooks, tool registration, context interfaces).
APIs are versioned: client upgrades add interfaces or change signatures, and an implementation written against an older API fails to load.
claude-mem's implementation tracks Claude Code's API version, and opencode's API is not identical to Claude Code's — when the two sides' versions don't line up, opencode fails at load time with an API mismatch.
This is a client-plugin contract incompatibility, not an install-pose problem.
Two deterministic conclusions follow: first, don't judge the plugin version with claude-mem --version (that's the npm CLI's version) — read the plugin directory ~/.claude/plugins/cache/thedotmack/claude-mem/<ver> (dual version numbers);
second, the opencode fix path can only be "wait for upstream" or "switch to a compatible implementation", because the contract is in someone else's hands.
Step by step
1. Confirm the client scenario — Required
Claude Code (primary plugin form): install and use normally; the full install/uninstall chain is measured in this marketplace (install exit=0 -> uninstall zero leftovers).
2. opencode scenario — Required
- Wait for a plugin update before trying the opencode form again;
- Or switch to a compatible implementation (e.g. an officially supported memory solution).
3. Version check — Required
Judge troubleshooting/upgrades by the plugin directory ~/.claude/plugins/cache/thedotmack/claude-mem/<ver>, not claude-mem --version (npm CLI 12.4.7 != plugin 13.16.1 - dual version numbers).
How to confirm it works
claude-mem doctor && claude-mem status
The Claude Code scenario's worker ready = success (measured after install: Worker port: 37700, Installation Complete, exit=0).
Other environments
| Environment | Notes |
|---|---|
| Claude Code (primary form) | Works; measured passing in this marketplace |
| opencode | API mismatch; wait for upstream update or switch to a compatible implementation |
| Version judgement | Use the plugin directory version; CLI version != plugin version |
Symptom
Installing the claude-mem plugin in opencode reports API mismatch / load failure.
Cause
The opencode plugin API is out of sync with claude-mem's plugin implementation version (CSDN 2026-05 case).
Solution
- Switch to a compatible implementation, or prefer using it in the Claude Code scenario (the plugin's primary form).
- Wait for a plugin update before trying the opencode form again.
Verification Evidence
- CSDN 2026-05 case.
- opencode form not measured in this marketplace (no login state), honestly noted.
Local verification record(2026-08-28)
- local repro log; local repro log.
- Not measured: real session capture/memory writes (needs a logged-in session), adopt/cleanup runs, opencode form.
Applicable tools (1)
This problem is linked from the tool pages below — reachable from either side.
claude-memSource & evidence
← Sessions & Memory domain | Problem Catalog Experience | Facing another issue? Go to the Helpdesk