#update seems to have broken discord

1 messages ยท Page 1 of 1 (latest)

left glade
#

updated to thr 5.2 update and now getting this (discord channel now unresponsive, worked fine before):
Config warnings:

  • plugins.entries.whatsapp: plugin not found: whatsapp (stale config entry ignored; remove it from plugins config)
  • plugins.entries.discord: plugin not found: discord (stale config entry ignored; remove it from plugins config)

๐Ÿฆž OpenClaw 2026.5.2 (8b2a6e5) โ€” Your AI assistant, now without the $3,499 headset.

โ”‚
โ—‡ Config warnings โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚ โ”‚
โ”‚ - plugins.entries.whatsapp: plugin not found: whatsapp (stale config entry ignored; โ”‚
โ”‚ remove it from plugins config) โ”‚
โ”‚ - plugins.entries.discord: plugin not found: discord (stale config entry ignored; remove โ”‚
โ”‚ it from plugins config) โ”‚
โ”‚ โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
Restarted LaunchAgent: gui/502/ai.openclaw.gateway

fervent zealot
#

same here... been trying to debug... i finally got it loaded but full of errors, can't find token etc even through it worked before

20:10:51.273-07:00 [discord] channel startup failed: channels.discord.accounts.default.token: unresolved SecretRef "env:default:DISCORD_BOT_TOKEN". Resolve this command against an active gateway runtime snapshot before reading it.

but the env is there...

proper jungle
#

I have the same issue, if you look in the logs its on a gateway restart loop, when it times out after 15s it restart the gateway.

left glade
#

you can try this:

openclaw plugins install npm:@openclaw/discord@2026.5.2 --force
openclaw doctor --fix
openclaw gateway restart --force

#

hope they send out a patch soon

proper jungle
#

This cant be good: Plugin "discord" has 1 suspicious code pattern(s). Run "openclaw security audit --deep" for details.

golden flax
#

discord broken fr

left glade
#

discord works but now having issue with sub-agents that use codex as default. lots of errors and warnings. i think i may roll it back

golden flax
#

whats the last good version?

proper jungle
#

Another user said 4.23 was their last stable version.

fervent zealot
#

4.27 works for me too, but 4.29 does not (tons of different issues there including different discord issue). trying the plugin install now (i tried a simplier version of that before and got errors, but the one @left glade shared installed ok anyway). running doctor now...

#

nope same error: 20:40:01.736-07:00 [discord] channel startup failed: channels.discord.accounts.default.token: unresolved SecretRef "env:default:DISCORD_BOT_TOKEN". Resolve this command against an active gateway runtime snapshot before reading it.

i give up, going back to 4.27

proper jungle
#

I tried to revert and getting an error when using openclaw update --tag 2026.4.27

left glade
#

yeah the update is cooked. rolling back didnt work for me. then i had issues rolling forward.

proper jungle
#

Yep, very broken, enough for tonight. Will see if they fix it in the morning

remote salmon
left glade
#

my config was alr edited by 5.2

#

you can still force it, just wasnt as easy

steady meteor
#

If you need to rollback (which I did to 4.26) you'll need to restore the backed up config to one that was last updated by the version you are restoring to.

weary lynx
#

if you're having issues after the 2026.5.2 update, there's a quick fix.
The update has a packaging bug where two dependencies (grammy and discord-api-types) don't get bundled correctly. Run this in your terminal:
npm install --prefix /opt/homebrew/lib/node_modules/openclaw grammy discord-api-types
Then restart the gateway:
openclaw gateway restart
That should sort it. Working fine on my end once we applied the fix. ๐Ÿ™Œ

stoic nest
#

Got Codex to fix it, missing npm Discord plugin after the upgrade was the issue.
Same story with the Codex plugin.
I donโ€™t know how they managed to get these past few releases out without testing basic functionalities.

left glade
valid orchid
#

Same here DM channel works

valid orchid
proper jungle
#

It had the wrong base url for other models as well, I have minimax as backup with I use all my codex usage and that base URL was also messed up.

stoic nest
merry pecan
#

After the whole weekend fighting to get Discord to work with 20206.4.29 and 2026.5.2, regression to 2026.4.23 restored it immediately. If anyone hears of a solution with the newer versions, or is able to confirm an upcoming release is definitely stable with Discord when it drops, I'd love to know about it. In the meantime, have lodged the issue in github.

wild urchin
#

How do we update openclaw to a specific version rather than the most current version it offers for the update? I also ran the update to May 2 and have had nothing but problems today. Agents repeating the same information agents not responding in discord, etc..

merry pecan
#

Sounds very similar to my experience. Here's what I did:

npm ls -g --depth=0 openclaw || true
npm i -g openclaw@2026.4.23 (or whatever version you want to go back to)
openclaw gateway restart

You might get a config error at gateway restart after the rollback, which I bypassed with: openclaw config unset meta.lastTouchedVersion

inland pine
#

Yep discord broke. This is why I have openclaw nightly backup to github

dull garnet
sage nova
#

4.27 is sane so far; but pairing and device approvals are all borked since 4.29+ for me on ubuntu 24 lts; cli could not approve anything; rollback to 4.27 and pairing works again; the issue is that the cli operator doesn't have proper scopes by default, and when i try to patch them, it doesn't take; so no way to really pair control-ui browser

left glade
#

the new version fixes this. they went modular meaning whatever plugins you had before you need to reinstall

#

openclaw plugins install @openclaw/discord --force
openclaw plugins registry --refresh
openclaw plugins inspect discord
openclaw gateway restart --force
etc

#

if you lost brave search or codex or whatsapp just put the name of plugin

#

i had to re-install brave search:

#

openclaw plugins install @openclaw/brave-plugin --force
openclaw plugins registry --refresh
openclaw plugins inspect brave

fervent zealot
#

new version (I assume 5.3) fixes this as in, no longer need to even to the manual plugins (re-) install?

left glade
#

i just hope this means that every update requires all these installs