Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: non-Lark users can still hit hard CLI startup failures from bundled Feishu dependency on 2026.4.20 [1 comments, 2 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#69959•Fetched 2026-04-23 07:30:59
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
9
Author
MichealWangYZMichealWangYZ
Participants
MichealWangYZMichealWangYZsteipetesteipete
Timeline (top)
subscribed ×3closed ×1commented ×1

openclaw --version succeeds, but subsequent CLI flows can hit:

Error: Cannot find module '@larksuiteoapi/node-sdk'
Require stack:
- /home/yizhou-wang/.nvm/versions/node/v24.15.0/lib/node_modules/openclaw/dist/extensions/feishu/client-yWGpoGkZ.js

Error Message

Error: Cannot find module '@larksuiteoapi/node-sdk' Require stack:

  • /home/yizhou-wang/.nvm/versions/node/v24.15.0/lib/node_modules/openclaw/dist/extensions/feishu/client-yWGpoGkZ.js

Root Cause

This has a broad blast radius:

  • non-Lark users get broken by a channel they do not use
  • Linux/npm global installs become unreliable
  • the practical workaround becomes pinning older versions or manually patching dependencies

Fix Action

Fix / Workaround

  • non-Lark users get broken by a channel they do not use
  • Linux/npm global installs become unreliable
  • the practical workaround becomes pinning older versions or manually patching dependencies

Code Example

Error: Cannot find module '@larksuiteoapi/node-sdk'
Require stack:
- /home/yizhou-wang/.nvm/versions/node/v24.15.0/lib/node_modules/openclaw/dist/extensions/feishu/client-yWGpoGkZ.js

---

npm install -g openclaw@2026.4.20

---

Cannot find module '@larksuiteoapi/node-sdk'
RAW_BUFFERClick to expand / collapse

Description

On a fresh Linux/npm global install of [email protected], the CLI can still fail on startup with a hard module-resolution error for the bundled Feishu/Lark integration even when the operator does not use Lark/Feishu at all.

This is distinct from the older reports about Feishu onboarding itself: the core usability problem is that an optional regional channel integration is still capable of breaking unrelated CLI flows for non-Lark users.

Summary

openclaw --version succeeds, but subsequent CLI flows can hit:

Error: Cannot find module '@larksuiteoapi/node-sdk'
Require stack:
- /home/yizhou-wang/.nvm/versions/node/v24.15.0/lib/node_modules/openclaw/dist/extensions/feishu/client-yWGpoGkZ.js

Environment

  • OpenClaw: 2026.4.20 (115f05d)
  • Install method: npm install -g openclaw
  • OS: Ubuntu Linux
  • Node.js: v24.15.0
  • Install location: /home/yizhou-wang/.nvm/versions/node/v24.15.0/lib/node_modules/openclaw

Steps to reproduce

  1. Install OpenClaw globally via npm: 
    npm install -g [email protected]
  2. Run normal CLI flows as a user who does not use Lark/Feishu.
  3. Observe a startup/load failure from the bundled Feishu extension: 
    Cannot find module '@larksuiteoapi/node-sdk'

Expected behavior

If Feishu/Lark support is optional, then one of these should happen:

  • the dependency is staged correctly in npm global installs, or
  • the Feishu extension is lazy-loaded only when configured, or
  • OpenClaw degrades gracefully and warns that the optional channel is unavailable

What should not happen is a hard failure for unrelated CLI usage on non-Lark installs.

Actual behavior

A bundled optional integration still participates early enough in startup/module loading to break the CLI for operators who never intended to use it.

Why this matters

This has a broad blast radius:

  • non-Lark users get broken by a channel they do not use
  • Linux/npm global installs become unreliable
  • the practical workaround becomes pinning older versions or manually patching dependencies

Related issues

This appears related to, but not fully addressed by:

  • #23611
  • #39733
  • #61787
  • #62749

The remaining product-level issue is that optional bundled channel integrations should not be able to hard-crash general CLI startup for unrelated users.

extent analysis

TL;DR

The most likely fix is to ensure the Feishu extension is lazy-loaded or its dependency is correctly staged in npm global installs to prevent hard failures for non-Lark users.

Guidance

  • Verify if the @larksuiteoapi/node-sdk dependency is correctly installed and accessible in the global npm install location.
  • Check if there's an option to configure or disable the Feishu extension for non-Lark users to prevent it from loading on startup.
  • Investigate if the issue is specific to the 2026.4.20 version of openclaw or if it persists across different versions.
  • Consider patching the dependency or pinning an older version as a temporary workaround until a proper fix is available.

Example

No code snippet is provided as the issue seems to be related to the packaging and dependency management of the openclaw package rather than a specific code error.

Notes

The issue seems to be related to how optional channel integrations are handled in openclaw, and a proper fix might require changes to the package's architecture or dependency management. The provided related issues suggest that this is an ongoing problem that has not been fully addressed.

Recommendation

Apply a workaround, such as patching the dependency or pinning an older version, until a proper fix is available that ensures optional channel integrations do not cause hard failures for unrelated users.

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

If Feishu/Lark support is optional, then one of these should happen:

  • the dependency is staged correctly in npm global installs, or
  • the Feishu extension is lazy-loaded only when configured, or
  • OpenClaw degrades gracefully and warns that the optional channel is unavailable

What should not happen is a hard failure for unrelated CLI usage on non-Lark installs.

#api#ssr#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.

Back to top recommendations

TRENDING