stoic trail
I tried to update openclaw from 23 to 2026.3.28, the upgrade mostly success but seems failed to upgrade the opik-openclaw plugins, with the following errors,
Failed to update opik-openclaw: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/opt/homebrew/lib/node_modules/openclaw/dist/install.runtime-DDmlaKdG.js' imported from /opt/homebrew/lib/node_modules/openclaw/dist/installs-Qst5vOrV.js
After the upgrade, opik no longer able to receive trace
karmic parrotBOT
sharp templeBOT
Yep — this looks like an updater self-replace bug, not an Opik-specific config issue.
What’s happening: openclaw update updates files in place, then tries to lazy-import another hashed dist/*.js file (install.runtime-*.js) that no longer matches what was loaded earlier in the same process. That can fail exactly like your stack trace.
Try this in a fresh shell:
openclaw --version
openclaw plugins update opik-openclaw
openclaw plugins enable opik-openclaw
openclaw gateway restart
Then verify:
openclaw plugins inspect opik-openclaw
openclaw logs --follow
If plugins update still errors, force reinstall the plugin:
openclaw plugins install @opik/opik-openclaw --force
openclaw gateway restart
If that still fails with ERR_MODULE_NOT_FOUND, your global install is likely partially broken — reinstall OpenClaw once, then re-run plugin install.
Can you paste output from:
openclaw --versionopenclaw plugins inspect opik-openclawopenclaw logs --follow after restartDocs:
stoic trail
openclaw plugins install @opik/opik-openclaw --force
error: unknown option '--force'
openclaw plugins install @opik/opik-openclaw
🦞 OpenClaw 2026.4.2 (d74a122) — If you're lost, run doctor; if you're brave, run prod; if you're wise, run tests.
Resolving clawhub:@opik/opik-openclaw…
ClawHub code-plugin @opik/opik-openclaw@0.2.9 channel=community verification=source-linked
Compatibility: pluginApi=>=2026.3.2
ClawHub package "@opik/opik-openclaw" is community; review source and verification before enabling.
Downloading plugin @opik/opik-openclaw@0.2.9 from ClawHub…
Extracting /var/folders/v5/4rlszc957jj1zxwbt0qd82j40000gn/T/openclaw-clawhub-package-EaxmzA/opik-openclaw.zip…
plugin already exists: /Users/lilian/.openclaw/extensions/opik-openclaw (delete it first)
sharp templeBOT
Nice, this output is super helpful.
You’re on 2026.4.2 now, and the blocker is simply:
--force not supported in your current plugins install command~/.openclaw/extensions/opik-openclaw)So do a clean reinstall via CLI (no manual delete needed):
openclaw plugins uninstall opik-openclaw
openclaw plugins install @opik/opik-openclaw
openclaw plugins enable opik-openclaw
openclaw gateway restart
Then verify:
openclaw plugins inspect opik-openclaw
openclaw plugins list --enabled
openclaw logs --follow
If Opik still gets no traces after this, paste plugins inspect + first Opik-related log lines and I’ll help pinpoint whether it’s plugin load vs Opik auth/config.
Refs:
stoic trail
openclaw plugins install @opik/opik-openclaw
🦞 OpenClaw 2026.4.2 (d74a122) — I'm the assistant your terminal demanded, not the one your sleep schedule requested.
Resolving clawhub:@opik/opik-openclaw…
ClawHub code-plugin @opik/opik-openclaw@0.2.9 channel=community verification=source-linked
Compatibility: pluginApi=>=2026.3.2
ClawHub package "@opik/opik-openclaw" is community; review source and verification before enabling.
ClawHub /api/v1/packages/%40opik%2Fopik-openclaw/download failed (429): Rate limit exceeded
sharp templeBOT
Yep — that new error is just ClawHub rate limiting (429), not the original module-missing issue.
Two important notes:
openclaw plugins install --force @opik/opik-openclaw
openclaw plugins inspect opik-openclaw
openclaw plugins enable opik-openclaw
openclaw gateway restart
If tracing is still dead, then do a clean cycle:
openclaw plugins uninstall opik-openclaw
openclaw plugins install @opik/opik-openclaw
(If you hit 429 again, wait a few minutes and retry — that’s server-side rate limit.)
If 429 keeps happening, we can bypass ClawHub by packing from npm and installing local .tgz (I can give exact commands next).
stoic trail
I have done uninstall, then install opike-openclaw according to your instructions and also configure opik, and restart gateway. But there is still no log in opik.
sharp templeBOT
Got it — if reinstall + configure + restart still gives no traces, we’re in runtime config/load territory now.
Most likely causes are:
Please run these and paste outputs:
openclaw plugins inspect opik-openclaw
openclaw plugins doctor
openclaw opik status
openclaw gateway status
Then do a live check:
openclaw logs --follow
…and while logs are running, send 1 normal message to your bot to force a run.
We’re looking for any opik / plugin / trace errors in that log stream.
Also quick sanity check: if plugins.allow is set, make sure it includes opik-openclaw.
If you paste those outputs, I can pinpoint the exact failing step in one pass.
stoic trail
plugins.allow set for opik-openclaw, opik endpoint, workspace correct, plugin installed on the gateway same machine. Still no trace logged. The opik works before my openclaw update...
sharp templeBOT
Thanks — given it worked before update, this strongly smells like a config/service path mismatch after upgrade (CLI writing one config, daemon reading another), or config.enabled not true inside the Opik plugin block.
Please run these exactly:
openclaw gateway status --deep
openclaw opik status
openclaw config get plugins.entries.opik-openclaw
What to check:
openclaw opik status should show Enabled: yesplugins.entries.opik-openclaw.config.enabled must be truegateway status --deep, if Config (cli) and Config (service) differ, fix with:openclaw gateway install --force
openclaw gateway restart
Then run:
openclaw logs --follow
On startup, you should see a line like:
opik: exporting traces to project ...
If that line never appears, plugin isn’t active in the running gateway (even if installed).
Paste those 3 command outputs and I’ll pinpoint the exact break.