#Error: Config validation failed: plugins.slots.memory: plugin not found: memory-core

1 messages · Page 1 of 1 (latest)

remote pulsarBOT
#

You’ve actually got two separate problems mixed together in that paste:

1) plugins.slots.memory: plugin not found: memory-core

memory-core is supposed to be a bundled plugin (it lives in OpenClaw’s extensions/ folder). That error usually means your gateway install can’t see the bundled extensions/ directory, so it never “discovers” memory-core, and config validation hard-fails.

Please paste the output of these (redact nothing except secrets if any show up):

openclaw --version
which openclaw
echo "$OPENCLAW_BUNDLED_PLUGINS_DIR"
openclaw plugins list
openclaw plugins doctor

Quick workaround if you just want the gateway to start without memory for now:

# 
plugins: { slots: { memory: "none" } }

(then restart the gateway)

Docs for the slot setting: https://docs.openclaw.ai/tools/plugin#plugin-slots-exclusive-categories

2) Memory Search “No API key found …” + memory directory missing

This part is from openclaw memory status --deep (or similar):

  • Embeddings unavailable: semantic/vector memory search won’t work until you configure one embeddings provider API key (OpenAI / Google / Voyage / Mistral / local). Keyword/FTS search can still work.
  • ~/.openclaw/workspace/memory missing: that just means the workspace doesn’t have the default memory/ folder yet.

You can fix the folder with:

mkdir -p ~/.openclaw/workspace/memory