#Updated from 2026.4.10 to 2026.4.26 - ERR_MODULE_NOT_FOUND chokidar

1 messages · Page 1 of 1 (latest)

white swallow
#

Hi Krill,

I just updated from 2026.4.10 to 2026.4.26. My agent lost a few days of memory and responses are quite delayed with log messages "chunks_vec not updated — sqlite-vec unavailable. Vector recall degraded."

When I try to run openclaw memory status I get the error "[openclaw] Failed to start CLI: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' imported from /home/openclaw/.openclaw/plugin-runtime-deps/openclaw-2026.4.26-67e811bb8931/dist/manager-ICKYl3BU.js"

I've run openclaw doctor a couple times now, but no dice.

lapis stirrupBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

rustic hareBOT
#

Hmm yeah, this looks like an incomplete/corrupt staged runtime-deps install, not a memory config issue.

sqlite-vec unavailable alone is degraded-but-not-fatal; OpenClaw falls back slower. But Cannot find package 'chokidar' imported from ~/.openclaw/plugin-runtime-deps/... means the 2026.4.26 staged package/deps tree is missing expected packages.

Try this first, as the same Linux user that runs the gateway:

openclaw --version
openclaw doctor --fix
openclaw gateway restart
openclaw memory status --deep --index --agent main

If chokidar still fails, check whether your CLI itself points into the broken staged tree:

# 
which openclaw
readlink -f "$(which openclaw)"

If that path resolves under:

/home/openclaw/.openclaw/plugin-runtime-deps/...

then don’t delete/move that folder yet — reinstall the CLI cleanly first:

pnpm add -g openclaw@2026.4.26
pnpm approve-builds -g
# 
openclaw gateway install --force
openclaw gateway restart

If openclaw does not resolve into plugin-runtime-deps, then move only the staged deps cache aside and let doctor rebuild it:

openclaw gateway stop
mv ~/.openclaw/plugin-runtime-deps ~/.openclaw/plugin-runtime-deps.bak.$(date +%Y%m%d-%H%M%S)
openclaw doctor --fix
openclaw gateway restart
openclaw memory status --deep --index --agent main

Don’t delete ~/.openclaw/memory or session files — the staged deps cache is separate from the actual memory DB.