#tokenjuice plugin fails to load on gateway start

1 messages · Page 1 of 1 (latest)

dim blaze
#

OpenClaw Version: 2026.4.22 (00bd2cf)
Environment: Ubuntu 22.04, Node v24.14.1, npm-installed OpenClaw
Plugin: tokenjuice (bundled extension)

Problem:
tokenjuice plugin fails to load on gateway start with:

[plugins] tokenjuice failed to load from /path/to/openclaw/dist/extensions/tokenjuice/index.js:
Error: Cannot find module 'tokenjuice/openclaw'
Require stack:

  • /path/to/openclaw/dist/extensions/tokenjuice/runtime-api.js

Config:
plugins.allow includes "tokenjuice" and plugins.entries.tokenjuice.enabled: true

What we found:

• Extension directory exists at dist/extensions/tokenjuice/
• package.json has "tokenjuice": "0.6.1" in dependencies
• But node_modules/tokenjuice/ was NOT installed
• Running npm install manually in the extension directory fixed it

Question:
Should the bundled extension dependencies be auto-installed during OpenClaw install/update? Or is there a config step we missed?

Workaround that worked:

cd $(openclaw --prefix)/lib/node_modules/openclaw/dist/extensions/tokenjuice
npm install

main hollowBOT
rigid sableBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

main hollowBOT
somber ventureBOT
#

I checked the docs and current source. You didn’t miss a config step.

Short version:

  • tokenjuice is meant to be bundled, with no separate install step: https://docs.openclaw.ai/tools/tokenjuice
  • Its runtime deps are not eagerly installed for every bundled plugin during npm install/update, by design.
  • Instead, OpenClaw is supposed to install missing bundled runtime deps on demand when the enabled plugin loads, or repair them via openclaw doctor --fix: https://docs.openclaw.ai/gateway/doctor

So yes, node_modules/tokenjuice/ being absent in the published package can be normal.
What is not normal is the gateway then failing with Cannot find module 'tokenjuice/openclaw' for an enabled bundled plugin.

So I’d treat your npm install inside dist/extensions/tokenjuice as a workaround, not the intended workflow. On 2026.4.22, this looks like a bug/regression in the bundled runtime-deps path, not bad config.

If you can still reproduce it cleanly, please file it here with openclaw status --all plus the startup log: https://github.com/openclaw/openclaw/issues

dim blaze
#

never mind.. my openclaw did an npm install.. and said it fixed it..