openclaw - 💡(How to fix) Fix lmstudio plugin fails to load: Cannot find module './providers/faux.js' [1 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#70875Fetched 2026-04-24 10:38:25
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

The built-in lmstudio extension fails to load on gateway startup with:

[plugins] lmstudio failed to load from /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/index.js:
Error: Cannot find module './providers/faux.js'
Require stack:
- /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/node_modules/@mariozechner/pi-ai/dist/index.js

Error Message

[plugins] lmstudio failed to load from /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/index.js: Error: Cannot find module './providers/faux.js' Require stack:

  • /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/node_modules/@mariozechner/pi-ai/dist/index.js

Root Cause

The built-in lmstudio extension fails to load on gateway startup with:

[plugins] lmstudio failed to load from /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/index.js:
Error: Cannot find module './providers/faux.js'
Require stack:
- /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/node_modules/@mariozechner/pi-ai/dist/index.js

Fix Action

Workaround

Rename the extension folder:

mv /usr/lib/node_modules/openclaw/dist/extensions/lmstudio \
   /usr/lib/node_modules/openclaw/dist/extensions/lmstudio.disabled
systemctl restart openclaw-gateway

Note: plugins.deny in openclaw.json does not prevent auto-discovered extensions from attempting to load.

Code Example

[plugins] lmstudio failed to load from /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/index.js:
Error: Cannot find module './providers/faux.js'
Require stack:
- /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/node_modules/@mariozechner/pi-ai/dist/index.js

---

mv /usr/lib/node_modules/openclaw/dist/extensions/lmstudio \
   /usr/lib/node_modules/openclaw/dist/extensions/lmstudio.disabled
systemctl restart openclaw-gateway
RAW_BUFFERClick to expand / collapse

Description

The built-in lmstudio extension fails to load on gateway startup with:

[plugins] lmstudio failed to load from /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/index.js:
Error: Cannot find module './providers/faux.js'
Require stack:
- /usr/lib/node_modules/openclaw/dist/extensions/lmstudio/node_modules/@mariozechner/pi-ai/dist/index.js

Impact

  • On versions prior to the fix, this caused a crash loop — gateway would start, hit the plugin error, and exit with SIGKILL, triggering systemd restart, leading to Start request repeated too quickly.
  • On current version (2026.4.22), the plugin fails gracefully (logs error but gateway stays up), however it still pollutes logs on every startup.

Steps to Reproduce

  1. Install OpenClaw 2026.4.22 (00bd2cf)
  2. Start gateway: openclaw gateway start
  3. Observe logs: journalctl -u openclaw-gateway

Expected Behavior

The lmstudio plugin should either:

  • Ship with all required dependencies (providers/faux.js)
  • Be excluded from the default extension bundle if not production-ready
  • Fail gracefully without polluting logs (mark as optional/disabled by default)

Workaround

Rename the extension folder:

mv /usr/lib/node_modules/openclaw/dist/extensions/lmstudio \
   /usr/lib/node_modules/openclaw/dist/extensions/lmstudio.disabled
systemctl restart openclaw-gateway

Note: plugins.deny in openclaw.json does not prevent auto-discovered extensions from attempting to load.

Environment

  • OpenClaw: 2026.4.22 (00bd2cf)
  • Node.js: v22.22.1
  • OS: Ubuntu 24.04 (x64)
  • Install method: npm global

extent analysis

TL;DR

The lmstudio extension can be temporarily worked around by renaming its folder to prevent auto-loading.

Guidance

  • Verify the issue by checking the logs with journalctl -u openclaw-gateway after starting the gateway.
  • To mitigate the issue, rename the lmstudio extension folder as described in the provided workaround.
  • Consider excluding the lmstudio plugin from the default extension bundle if it's not production-ready.
  • Note that using plugins.deny in openclaw.json does not prevent auto-discovered extensions from attempting to load.

Example

mv /usr/lib/node_modules/openclaw/dist/extensions/lmstudio \
   /usr/lib/node_modules/openclaw/dist/extensions/lmstudio.disabled
systemctl restart openclaw-gateway

Notes

This workaround may not be a permanent solution and may need to be reapplied after updates. The root cause of the issue seems to be a missing dependency (providers/faux.js) in the lmstudio extension.

Recommendation

Apply the workaround by renaming the lmstudio extension folder, as it allows the gateway to start without the plugin error and prevents log pollution.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING