(For context, I am running claw on a dedicated local installation on mac.
I asked my claw instance to do this:
Great. Can you implement mem0 memory now? Could we do both QMD in mem0 or is this not a thing?
Then my claw instance went offline and now giving this error in web ui dashboard: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/opt/homebrew/lib/node_modules/openclaw/dist/route-reply.runtime-BEsL(removed for security if any imporatant keys).js' imported from /opt/homebrew/lib/node_modules/openclaw/dist/dispatch-CYHz(removed for security if any imporatant keys).js
#my claw instance went offline- error message
14 messages · Page 1 of 1 (latest)
That looks like a broken/mixed OpenClaw install, not a mem0/Qdrant issue.
The clue is this part:
/opt/homebrew/lib/node_modules/openclaw/dist/... importing a hashed runtime chunk that no longer exists.
That usually means the package got partially updated or modified in place.
First, please paste:
openclaw --version
openclaw status --all
Then I’d try this repair sequence on the Mac:
openclaw update
openclaw doctor
openclaw gateway install --force
openclaw gateway restart
If it still fails, do a clean reinstall of the global package, then restart again:
npm i -g openclaw@latest
openclaw doctor
openclaw gateway install --force
openclaw gateway restart
Important bit: if you want your local claw to implement OpenClaw features like mem0 support, I would not do that against the packaged global install in /opt/homebrew/lib/node_modules/openclaw/dist. Use a git/source checkout instead, so it edits real source and rebuilds cleanly.
Docs:
- FAQ: https://docs.openclaw.ai/help/faq
- Updating: https://docs.openclaw.ai/install/updating
- Troubleshooting: https://docs.openclaw.ai/gateway/troubleshooting
Paste the --version and status --all output and I can narrow it down fast.
openclaw version: OpenClaw 2026.4.14 (323493f)
openclaw status --all reply:
Invalid config at /Users/me/.openclaw/openclaw.json:\n- plugins.entries.openclaw-mem0.config: invalid config: must NOT have additional properties
🦞 OpenClaw 2026.4.14 — Your personal assistant, minus the passive-aggressive calendar reminders.
Config invalid
File: ~/.openclaw/openclaw.json
Problem:
- plugins.entries.openclaw-mem0.config: invalid config: must NOT have additional properties
Run: openclaw doctor --fix
openclaw update reply:
user@user-MacBook-Pro ~ % openclaw update
Config invalid
File: ~/.openclaw/openclaw.json
Problem:
- plugins.entries.openclaw-mem0.config: invalid config: must NOT have additional properties
Run: openclaw doctor --fix
Nice, that narrows it down a lot.
Your first blocker is not the missing module, it’s this:
plugins.entries.openclaw-mem0.config: invalid config: must NOT have additional properties
That means the mem0 plugin config has keys in it that the plugin’s schema does not allow. OpenClaw validates plugin config strictly, so if your agent wrote ad-hoc mem0/Qdrant fields in there, startup/update can get wedged.
I’d do this in order:
openclaw doctor --fix
If that still complains about plugins.entries.openclaw-mem0.config, then back up the config and remove that plugin config block:
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.bak-$(date +%Y%m%d-%H%M%S)
openclaw config unset plugins.entries.openclaw-mem0.config
openclaw gateway restart
If config unset won’t run, open ~/.openclaw/openclaw.json manually and remove just:
plugins: {
entries: {
"openclaw-mem0": {
config: { ... }
}
}
}
or at least the invalid config: { ... } part for that plugin.
After the gateway boots again, then do:
openclaw update
openclaw doctor
If you want to see what config keys the plugin actually accepts before re-adding anything:
openclaw plugins inspect openclaw-mem0 --json
and look at its configSchema.
So, short version: the agent probably wrote unsupported mem0 config into openclaw.json. Fix/remove that first, then the module error may disappear, and if not, update/reinstall core after config is clean.
Docs:
- Doctor: https://docs.openclaw.ai/gateway/doctor
- Config CLI: https://docs.openclaw.ai/cli/config
- Plugins CLI: https://docs.openclaw.ai/cli/plugins
If you paste the plugins.entries.openclaw-mem0 block, I can tell you exactly which keys are wrong.
now that its fix and running again, how could my openclaw instance correctly install mem0?
Yep. I’d do it manually once, not by asking the agent to invent the config 😅
For the Mem0 plugin, the clean path is:
1) Install the plugin
openclaw plugins install @mem0/openclaw-mem0
2) Add a minimal valid config to ~/.openclaw/openclaw.json
Under plugins.entries:
Mem0 Cloud
"openclaw-mem0": {
"enabled": true,
"config": {
"apiKey": "${MEM0_API_KEY}",
"userId": "jacob"
}
}
Open-source / self-hosted
"openclaw-mem0": {
"enabled": true,
"config": {
"mode": "open-source",
"userId": "jacob"
}
}
Open-source with Qdrant
"openclaw-mem0": {
"enabled": true,
"config": {
"mode": "open-source",
"userId": "jacob",
"oss": {
"vectorStore": {
"provider": "qdrant",
"config": {
"host": "localhost",
"port": 6333
}
}
}
}
}
3) Validate and restart
openclaw config validate
openclaw gateway restart