Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: 2026.4.27 runtime-deps missing chokidar and sqlite-vec on Linux — openclaw memory status --deep fails [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74883•Fetched 2026-05-01 05:40:23
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
2
Author
mikelin0083mikelin0083
Participants
clawsweeper[bot]clawsweeper[bot]CrabsticksaladCrabsticksaladmikelin0083mikelin0083
Timeline (top)
cross-referenced ×3commented ×2closed ×1labeled ×1

After upgrading to 4.27, openclaw memory status --deep fails immediately with missing runtime deps. The 4.27 release notes claim chokidar v5 hot reload is restored (fixes #27404, #33585, #41606), but the runtime-deps directory ships without chokidar and sqlite-vec.

Error Message

First error (chokidar missing): Failed to start CLI: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' Second error (after manually installing chokidar):

Root Cause

After upgrading to 4.27, openclaw memory status --deep fails immediately with missing runtime deps. The 4.27 release notes claim chokidar v5 hot reload is restored (fixes #27404, #33585, #41606), but the runtime-deps directory ships without chokidar and sqlite-vec.

Fix Action

Workaround

Manually install into the 4.27 runtime-deps directory:

cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.27-ca367608fb89
npm install chokidar@^5.0.0 sqlite-vec

After this, openclaw memory status --deep passes fully (Vector ready, FTS ready, Embeddings ready).

Code Example

cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.27-ca367608fb89
npm install chokidar@^5.0.0 sqlite-vec

---
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to 4.27, openclaw memory status --deep fails immediately with missing runtime deps. The 4.27 release notes claim chokidar v5 hot reload is restored (fixes #27404, #33585, #41606), but the runtime-deps directory ships without chokidar and sqlite-vec.

Errors

First error (chokidar missing): Failed to start CLI: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'chokidar' imported from ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.27-ca367608fb89/dist/manager-jzSMQjEt.js

Second error (after manually installing chokidar): sqlite-vec unavailable Vector: unavailable

Steps to reproduce

  1. openclaw update from 4.22 to 4.27
  2. openclaw memory status --deep
  3. Observe ERR_MODULE_NOT_FOUND for chokidar

Workaround

Manually install into the 4.27 runtime-deps directory:

cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.27-ca367608fb89
npm install chokidar@^5.0.0 sqlite-vec

After this, openclaw memory status --deep passes fully (Vector ready, FTS ready, Embeddings ready).

Note

This is a recurring pattern: similar issues were reported in #61686 (4.5) and #58701 (3.31). The bundled runtime-deps for memory-core appear to not be reliably included in the packaged release.

Expected behavior

After upgrading to 4.27, openclaw memory status --deep should pass without manual intervention. chokidar and sqlite-vec should be present in the runtime-deps directory as declared in package.json dependencies.

Actual behavior

runtime-deps directory is missing chokidar and sqlite-vec. CLI fails to start with ERR_MODULE_NOT_FOUND. Manual npm install into the runtime-deps directory is required to restore memory functionality.

OpenClaw version

2026.4.27 (cbc2ba0)

Operating system

Ubuntu 24.x (VMware Virtual Platform)

Install method

No response

Model

openai-codex/gpt-5.5

Provider / routing chain

N/A — this is a CLI/plugin packaging issue, not a model routing issue.

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Manually installing chokidar and sqlite-vec in the runtime-deps directory resolves the issue with openclaw memory status --deep failing after upgrading to version 4.27.

Guidance

  • Verify that the runtime-deps directory is missing chokidar and sqlite-vec by checking the directory contents.
  • Manually install chokidar and sqlite-vec using npm install chokidar@^5.0.0 sqlite-vec in the runtime-deps directory.
  • After manual installation, re-run openclaw memory status --deep to verify that the issue is resolved.
  • Consider reporting this issue to the OpenClaw developers, as it is a recurring pattern (similar issues were reported in #61686 and #58701).

Example

cd ~/.openclaw/plugin-runtime-deps/openclaw-2026.4.27-ca367608fb89
npm install chokidar@^5.0.0 sqlite-vec

Notes

This issue may be related to the packaging process of OpenClaw, where the runtime-deps directory is not being populated correctly. The manual installation of chokidar and sqlite-vec is a temporary workaround until the issue is fixed in a future release.

Recommendation

Apply the workaround by manually installing chokidar and sqlite-vec in the runtime-deps directory, as this resolves the issue with openclaw memory status --deep failing after upgrading to version 4.27.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

After upgrading to 4.27, openclaw memory status --deep should pass without manual intervention. chokidar and sqlite-vec should be present in the runtime-deps directory as declared in package.json dependencies.

#conversation history#tool integration#LLM response#prompt template#agent execution

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING