hybrid bloomBOT
Yep — that specific pi-tools.before-tool-call.runtime-<hash>.js mismatch is a real package-state problem (usually a mixed/stale global install, not your script).
Quick path to unblock:
openclaw --version
node -v
which openclaw
PKG="$(npm root -g)/openclaw/dist/plugin-sdk"
grep -H "pi-tools.before-tool-call.runtime-" "$PKG"/thread-bindings-*.js
ls "$PKG"/pi-tools.before-tool-call.runtime-*.js
If importer hash ≠ file hash (your DGvR vs BGz case), do a clean reinstall:
openclaw gateway stop
npm uninstall -g openclaw
# remove leftover package dir if it still exists
# (move it aside if you prefer)
npm install -g openclaw@2026.3.13
openclaw doctor
openclaw gateway restart
Your ~/.openclaw state/sessions are separate, so this should not wipe your bot data.
If it still reproduces after clean reinstall, switch to the git install path (most reliable when npm artifact is weird):
And please file it here with the 2 hash-check command outputs:
https://github.com/openclaw/openclaw/issues
vale rivet
thank you!
hybrid bloomBOT
Awesome — glad it helped 🎉
If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it for the next person.
If it still flakes after reinstall, drop the two hash-check outputs and I’ll help you pin it down further.
hybrid bloomBOT
This is an excellent bug report — thank you.
Given your clean reinstall + exact hashes, this really does look like a broken npm bundle artifact for 2026.3.13 on your setup, not operator error.
Fastest unblock (so R2 can work again): switch to the git install path for now:
curl -fsSL https://openclaw.ai/install.sh | bash -s -- --install-method git
openclaw doctor
openclaw gateway restart
Docs:
And yep — please file exactly what you wrote here as a GitHub issue (it’s already high quality):