Skip to content

[Bug]: Browser plugin broken after 4.26→4.27 upgrade — ERR_MODULE_NOT_FOUND for old plugin-runtime-deps path (persists after doctor --repair) #75045

@WaldemarEnns

Description

@WaldemarEnns

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

  1. Running OpenClaw 2026.4.26 with browser plugin enabled
  2. Upgrade to 2026.4.27 (via npm/package manager)
  3. Run openclaw doctor --repair as recommended
  4. Restart gateway
  5. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions