A normal `openclaw update` / package-manager update to `2026.4.5` should not leave the CLI unable to load its own bundled plugin dependencies. Either: 1. the package should include/declare the required bundled runtime deps so commands work immediately after update, or 2. the update/doctor flow should be robust enough to recover without requiring manual global npm installs first.

openclaw - 💡(How to fix) Fix [Bug]: 2026.4.5 npm update/install can leave CLI broken with missing bundled plugin runtime deps [5 comments, 6 participants]

openclaw2026-04-06 04:37:34

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#61686•Fetched 2026-04-08 02:55:53

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

commented ×5cross-referenced ×1

Updating OpenClaw to 2026.4.5 via the normal npm/package-manager path left the CLI partially broken on a global install. Core commands failed immediately because bundled plugin runtime dependencies were missing from the installed dependency tree.

Error Message

Error: Cannot find module '@buape/carbon' Require stack:

.../openclaw/dist/ui-7MjYF8PY.js

Root Cause

Code Example

Error: Cannot find module '@buape/carbon'
Require stack:
- .../openclaw/dist/ui-7MjYF8PY.js

---

Error: Cannot find module '@larksuiteoapi/node-sdk'
Require stack:
- .../openclaw/dist/probe-Y2l52Hc0.js

---

npm install -g @buape/carbon
npm install -g @buape/carbon @larksuiteoapi/node-sdk grammy @grammyjs/runner @grammyjs/transformer-throttler @whiskeysockets/baileys @slack/web-api @slack/bolt discord-api-types @discordjs/voice

RAW_BUFFERClick to expand / collapse

Summary

What happened

After updating from 2026.4.2 to 2026.4.5, commands such as:

openclaw doctor
openclaw gateway status

failed with module resolution errors before normal doctor repair could run cleanly.

Initial failure:

Error: Cannot find module '@buape/carbon'
Require stack:
- .../openclaw/dist/ui-7MjYF8PY.js

After manually installing that package, the next failure surfaced:

Error: Cannot find module '@larksuiteoapi/node-sdk'
Require stack:
- .../openclaw/dist/probe-Y2l52Hc0.js

This suggests 2026.4.5 can install in a state where multiple bundled extension/plugin runtime deps are absent.

Recovery path that worked

Manual installs were needed before doctor could fully recover the install:

npm install -g @buape/carbon
npm install -g @buape/carbon @larksuiteoapi/node-sdk grammy @grammyjs/runner @grammyjs/transformer-throttler @whiskeysockets/baileys @slack/web-api @slack/bolt discord-api-types @discordjs/voice

Then running doctor succeeded and installed the remaining missing bundled plugin runtime deps.

Doctor reported missing bundled plugin deps including packages such as:

@buape/carbon (discord)
@larksuiteoapi/node-sdk (feishu)
grammy, @grammyjs/runner, @grammyjs/transformer-throttler (telegram)
@whiskeysockets/baileys (whatsapp)
@slack/web-api, @slack/bolt (slack)
discord-api-types, @discordjs/voice (discord)
plus additional bundled plugin deps

After the manual installs + openclaw doctor, the install became healthy again.

Expected behavior

A normal openclaw update / package-manager update to 2026.4.5 should not leave the CLI unable to load its own bundled plugin dependencies.

Either:

the package should include/declare the required bundled runtime deps so commands work immediately after update, or
the update/doctor flow should be robust enough to recover without requiring manual global npm installs first.

Environment

Install type reported by OpenClaw: pnpm
Actual global prefix path in use: standard npm-style global prefix
OpenClaw before update: 2026.4.2
OpenClaw after update: 2026.4.5
Node: v22.22.1
OS: Linux

I intentionally omitted personal paths / IDs / tokens, but can provide more sanitized detail if needed.

extent analysis

TL;DR

Manually installing missing bundled plugin runtime dependencies via npm may resolve the issue with OpenClaw's CLI after updating to version 2026.4.5.

Guidance

Verify that the issue persists after running openclaw doctor to ensure the doctor tool cannot recover the install on its own.
Manually install the missing dependencies using npm, as done in the recovery path, to confirm if this resolves the issue.
Check the package.json file of OpenClaw to see if the required bundled runtime dependencies are declared, which could indicate a packaging issue.
Consider reporting this as a bug to the OpenClaw maintainers, as the update process should not require manual installation of dependencies for the CLI to function.

Example

npm install -g @buape/carbon @larksuiteoapi/node-sdk grammy @grammyjs/runner @grammyjs/transformer-throttler @whiskeysockets/baileys @slack/web-api @slack/bolt discord-api-types @discordjs/voice

This command installs the missing dependencies that were required to recover the install in the reported issue.

Notes

The root cause of the issue seems to be related to missing bundled plugin runtime dependencies in the 2026.4.5 update of OpenClaw. The provided recovery path suggests that manually installing these dependencies can resolve the issue, but this should ideally be handled by the update or doctor process.

Recommendation

Apply the workaround by manually installing the missing dependencies, as this has been shown to resolve the issue in the reported case. This is recommended until the OpenClaw maintainers can address the issue and ensure that the update process includes all required dependencies.

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?

FAQ

Expected behavior

A normal openclaw update / package-manager update to 2026.4.5 should not leave the CLI unable to load its own bundled plugin dependencies.

Either:

the package should include/declare the required bundled runtime deps so commands work immediately after update, or
the update/doctor flow should be robust enough to recover without requiring manual global npm installs first.

#api #batch processing #GPU compatibility #latency issue #model loading

Still need to ship something?

×6

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

Data

Security

Network

Code

UI/UX

Text

System

Multimedia

Protocol

API

Engineering

openclaw - 💡(How to fix) Fix [Bug]: 2026.4.5 npm update/install can leave CLI broken with missing bundled plugin runtime deps [5 comments, 6 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Code Example

Summary

What happened

Recovery path that worked

Expected behavior

Environment

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

FAQ

Expected behavior

Still need to ship something?

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: 2026.4.5 npm update/install can leave CLI broken with missing bundled plugin runtime deps [5 comments, 6 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Code Example

Summary

What happened

Recovery path that worked

Expected behavior

Environment

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING