Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
After upgrading OpenClaw globally via sudo npm install -g openclaw@latest, the Discord channel fails to connect on named gateway profiles (e.g. --profile mneme, --profile peitho) with:
[discord] [default] channel exited: Cannot find package 'openclaw' imported from /home//.openclaw-/plugin-runtime-deps/openclaw-2026.4.22-4eca5026e977/dist/extensions/discord/provider-DYru-eTz.js
The provider subprocess resolves the openclaw package relative to the profile's plugin-runtime-deps/dist/ directory, but the package only exists at the global npm path (/usr/lib/node_modules/openclaw). The discord provider enters a restart loop (1/10 through 10/10) and never connects.
Steps to reproduce
1.Run two named gateway profiles as systemd user services (--profile mneme, --profile peitho) on Ubuntu Linux
2.Run sudo npm install -g openclaw@latest to upgrade
3.Stop and restart both services
4.Observe Discord channel failing with the error above on both profiles
Expected behavior
Discord provider starts successfully and connects after upgrade. Plugin-runtime-deps resolve the openclaw package through the global install path without manual intervention.
Actual behavior
Discord enters a 10-attempt restart loop and never connects. Both profiles affected identically.
OpenClaw version
2026.4.22 (00bd2cf)
Operating system
2026.4.22 (00bd2cf)
Install method
sudo npm install -g openclaw
Model
Not applicable — failure occurs before any model request is made. Discord provider subprocess fails at package resolution during channel startup.
Provider / routing chain
Not applicable — failure is in the Discord channel provider init path, not the model/provider chain. Gateway profile: ollama/qwen2.5:14b (Mneme, port 18793) and ollama/qwen2.5:32b (Peitho, port 18795) via local Ollama on Ubuntu.
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
After upgrading OpenClaw globally via sudo npm install -g openclaw@latest, the Discord channel fails to connect on named gateway profiles (e.g. --profile mneme, --profile peitho) with:
[discord] [default] channel exited: Cannot find package 'openclaw' imported from /home//.openclaw-/plugin-runtime-deps/openclaw-2026.4.22-4eca5026e977/dist/extensions/discord/provider-DYru-eTz.js
The provider subprocess resolves the openclaw package relative to the profile's plugin-runtime-deps/dist/ directory, but the package only exists at the global npm path (/usr/lib/node_modules/openclaw). The discord provider enters a restart loop (1/10 through 10/10) and never connects.
Steps to reproduce
1.Run two named gateway profiles as systemd user services (--profile mneme, --profile peitho) on Ubuntu Linux
2.Run sudo npm install -g openclaw@latest to upgrade
3.Stop and restart both services
4.Observe Discord channel failing with the error above on both profiles
Expected behavior
Discord provider starts successfully and connects after upgrade. Plugin-runtime-deps resolve the openclaw package through the global install path without manual intervention.
Actual behavior
Discord enters a 10-attempt restart loop and never connects. Both profiles affected identically.
OpenClaw version
2026.4.22 (00bd2cf)
Operating system
2026.4.22 (00bd2cf)
Install method
sudo npm install -g openclaw
Model
Not applicable — failure occurs before any model request is made. Discord provider subprocess fails at package resolution during channel startup.
Provider / routing chain
Not applicable — failure is in the Discord channel provider init path, not the model/provider chain. Gateway profile: ollama/qwen2.5:14b (Mneme, port 18793) and ollama/qwen2.5:32b (Peitho, port 18795) via local Ollama on Ubuntu.
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response