Summary
After upgrading from 2026.4.26 to 2026.4.27, the browser plugin fails with ERR_MODULE_NOT_FOUND referencing the old plugin-runtime-deps path (openclaw-2026.4.26-4eca5026e977). Running openclaw doctor --repair and multiple gateway restarts do not resolve the issue.
Error
GatewayClientRequestError: INVALID_REQUEST: Error [ERR_MODULE_NOT_FOUND]:
Cannot find module '/root/.openclaw/plugin-runtime-deps/openclaw-2026.4.26-4eca5026e977/dist/types.secrets-ClP-vJ-P.js'
imported from /root/.openclaw/plugin-runtime-deps/openclaw-2026.4.26-4eca5026e977/dist/extensions/browser/register.runtime.js
Steps to reproduce
- Running OpenClaw
2026.4.26 with browser plugin enabled
- Upgrade to
2026.4.27 (via npm/package manager)
- Run
openclaw doctor --repair as recommended
- Restart gateway
- Run
openclaw browser status → error above
Expected behavior
After upgrade + doctor + restart, browser plugin loads correctly using 2026.4.27 runtime deps.
Actual behavior
Gateway process still references old openclaw-2026.4.26-4eca5026e977 runtime-deps directory (which no longer exists). The file types.secrets-ClP-vJ-P.js was renamed in 4.27 (now types.secrets-BHp0Y_k0.js).
Observations
ls ~/.openclaw/plugin-runtime-deps/ shows only openclaw-2026.4.27-4eca5026e977 — the old dir is gone
- The error persists even after multiple
systemctl --user restart cycles
openclaw doctor --repair does not clear the stale runtime path
- The gateway process appears to cache the old path in-memory and carries it across restarts
- Browser plugin
packageVersion in plugins/installs.json is 2026.4.25 — may be part of the issue
Environment
- OpenClaw:
2026.4.27 (cbc2ba0)
- OS: Linux (Ubuntu), systemd user service
- Single instance setup
Related
Summary
After upgrading from
2026.4.26to2026.4.27, the browser plugin fails withERR_MODULE_NOT_FOUNDreferencing the oldplugin-runtime-depspath (openclaw-2026.4.26-4eca5026e977). Runningopenclaw doctor --repairand multiple gateway restarts do not resolve the issue.Error
Steps to reproduce
2026.4.26with browser plugin enabled2026.4.27(via npm/package manager)openclaw doctor --repairas recommendedopenclaw browser status→ error aboveExpected behavior
After upgrade + doctor + restart, browser plugin loads correctly using
2026.4.27runtime deps.Actual behavior
Gateway process still references old
openclaw-2026.4.26-4eca5026e977runtime-deps directory (which no longer exists). The filetypes.secrets-ClP-vJ-P.jswas renamed in 4.27 (nowtypes.secrets-BHp0Y_k0.js).Observations
ls ~/.openclaw/plugin-runtime-deps/shows onlyopenclaw-2026.4.27-4eca5026e977— the old dir is gonesystemctl --user restartcyclesopenclaw doctor --repairdoes not clear the stale runtime pathpackageVersioninplugins/installs.jsonis2026.4.25— may be part of the issueEnvironment
2026.4.27(cbc2ba0)Related