openclaw - 💡(How to fix) Fix Plugin/core version drift after upgrade causes silent channel failure

Summary

Upgrading OpenClaw core does not automatically realign installed plugin packages. If a plugin like @openclaw/discord remains on an older version than core, the channel can silently fall into a disabled/broken state with no clear incompatibility warning.

Environment

• OpenClaw version observed: 2026.5.7
• Host OS: Ubuntu 24.04
• Install style: native install / upgrade flow

Reproduction

Pin a plugin to an older version, then upgrade core:

cd ~/.openclaw/npm
npm install @openclaw/discord@<old-version>
sudo npm install -g @openclaw/openclaw@latest
systemctl --user restart openclaw-gateway.service

Now inspect channel state:

openclaw channels list --all --plain
# Discord: installed, not configured, disabled

Check versions:

node -e "
const p = require('/home/adam/.openclaw/npm/node_modules/@openclaw/discord/package.json');
console.log('plugin:', p.version);
"
openclaw --version

Then repair:

cd ~/.openclaw/npm
npm install @openclaw/discord@latest
openclaw doctor --fix
systemctl --user restart openclaw-gateway.service
openclaw channels list --all --plain
# Discord default (...): installed, configured, enabled

Expected

When core upgrades, plugin compatibility should remain aligned or the operator should get a clear, actionable error saying the installed plugin version is incompatible.

Actual

Core/plugin drift causes silent failure. The channel appears disabled or non-functional even though config remains valid and unchanged. There is no clear warning such as "plugin version incompatible with core version".

Why this matters

This creates a confusing post-upgrade failure mode: the bot stops working, validation still passes, and the operator has to manually discover version drift inside ~/.openclaw/npm/node_modules.

Suggested fix

Any of these would help:

• Auto-upgrade @openclaw/* plugins when core upgrades.
• Check plugin versions against core on startup and emit a warning/error when they drift.
• Refuse startup with an actionable message if a plugin is incompatible with the current core version.

Notes

In our environment, openclaw doctor --fix was also needed to repair the plugin dependency link after upgrading the package.

Primary source doc:

• docs/upstream-bugs/plugin-core-version-drift-after-upgrade.md