Bug type
Regression (worked before, now fails)
Summary
After updating a host npm install to OpenClaw 2026.5.4 (325df3e), the built-in Matrix channel no longer starts. The gateway itself stays healthy and the Control UI can connect, but Matrix accounts crash-loop because the published package cannot resolve matrix-js-sdk from the OpenClaw install root.
Steps to reproduce
- Run OpenClaw as a host npm install on macOS with Matrix channel configured and working.
- Run
openclaw update.
- Restart or let the managed gateway restart.
- Check gateway logs.
- Matrix messages are no longer received.
Expected behavior
Matrix channel starts after update and logs in normally.
Actual behavior
Both configured Matrix accounts repeatedly exit before login:
plugin CLI register failed (matrix): Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'matrix-js-sdk' imported from /Users/jacob/.local/lib/node_modules/openclaw/dist/logging-4Lig_RGM.js
[memo] channel exited: Cannot find package 'matrix-js-sdk' imported from /Users/jacob/.local/lib/node_modules/openclaw/dist/logging-4Lig_RGM.js
[openclaw] channel exited: Cannot find package 'matrix-js-sdk' imported from /Users/jacob/.local/lib/node_modules/openclaw/dist/logging-4Lig_RGM.js
The gateway remains otherwise healthy:
curl -fsS http://127.0.0.1:18789/healthz
{"ok":true,"status":"live"}
openclaw gateway status --deep
Connectivity probe: ok
Environment
- OpenClaw:
2026.5.4 (325df3e)
- OS: macOS
- Node:
v24.14.0
- Install method: host npm install managed by OpenClaw installer/update
- Install path:
/Users/jacob/.local/lib/node_modules/openclaw
- Gateway command:
/Users/jacob/.local/opt/node/v24.14.0/bin/node /Users/jacob/.local/lib/node_modules/openclaw/dist/index.js gateway --port 18789
- Matrix homeserver: self-hosted Matrix server
Diagnostic evidence
Immediately after update, these cannot resolve from the OpenClaw package root:
MISSING matrix-js-sdk/lib/logger.js Cannot find module 'matrix-js-sdk/lib/logger.js'
MISSING @matrix-org/matrix-sdk-crypto-nodejs Cannot find module '@matrix-org/matrix-sdk-crypto-nodejs'
MISSING @matrix-org/matrix-sdk-crypto-wasm Cannot find module '@matrix-org/matrix-sdk-crypto-wasm'
The local workaround is to reinstall the missing runtime deps into the OpenClaw package root and restart:
cd /Users/jacob/.local/lib/node_modules/openclaw
NPM_CONFIG_CACHE=/tmp/npm-cache-openclaw-repair npm install --omit=dev --package-lock=false --silent
NPM_CONFIG_CACHE=/tmp/npm-cache-openclaw-repair npm install --no-save --package-lock=false --silent matrix-js-sdk@41.4.0 @matrix-org/matrix-sdk-crypto-nodejs@0.4.0 @matrix-org/matrix-sdk-crypto-wasm@18.2.0
openclaw gateway restart
After the workaround, the Matrix accounts log in again and encrypted rooms become ready:
matrix: logged in as @openclaw:<private-homeserver>
matrix: logged in as @memo:<private-homeserver>
matrix: device is verified by its owner and ready for encrypted rooms
Related issues
This appears related to previous Matrix packaging/update dependency regressions, but it is not the same exact failure:
This report is specifically about OpenClaw 2026.5.4 host npm install failing to resolve matrix-js-sdk from the main OpenClaw package after openclaw update.
Bug type
Regression (worked before, now fails)
Summary
After updating a host npm install to
OpenClaw 2026.5.4 (325df3e), the built-in Matrix channel no longer starts. The gateway itself stays healthy and the Control UI can connect, but Matrix accounts crash-loop because the published package cannot resolvematrix-js-sdkfrom the OpenClaw install root.Steps to reproduce
openclaw update.Expected behavior
Matrix channel starts after update and logs in normally.
Actual behavior
Both configured Matrix accounts repeatedly exit before login:
The gateway remains otherwise healthy:
Environment
2026.5.4 (325df3e)v24.14.0/Users/jacob/.local/lib/node_modules/openclaw/Users/jacob/.local/opt/node/v24.14.0/bin/node /Users/jacob/.local/lib/node_modules/openclaw/dist/index.js gateway --port 18789Diagnostic evidence
Immediately after update, these cannot resolve from the OpenClaw package root:
The local workaround is to reinstall the missing runtime deps into the OpenClaw package root and restart:
cd /Users/jacob/.local/lib/node_modules/openclaw NPM_CONFIG_CACHE=/tmp/npm-cache-openclaw-repair npm install --omit=dev --package-lock=false --silent NPM_CONFIG_CACHE=/tmp/npm-cache-openclaw-repair npm install --no-save --package-lock=false --silent matrix-js-sdk@41.4.0 @matrix-org/matrix-sdk-crypto-nodejs@0.4.0 @matrix-org/matrix-sdk-crypto-wasm@18.2.0 openclaw gateway restartAfter the workaround, the Matrix accounts log in again and encrypted rooms become ready:
Related issues
This appears related to previous Matrix packaging/update dependency regressions, but it is not the same exact failure:
openclaw updateremoved Matrix extension dependencies.@vector-im/matrix-bot-sdkplus duplicate local plugin conflict.openclawfrom bundled Matrix files.This report is specifically about
OpenClaw 2026.5.4host npm install failing to resolvematrix-js-sdkfrom the main OpenClaw package afteropenclaw update.