Skip to content

Instantly share code, notes, and snippets.

@mateu

mateu/gist:6335e2a7f5575ca48722ea7b2fc19aac

Created May 3, 2026 20:09
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save mateu/6335e2a7f5575ca48722ea7b2fc19aac to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save mateu/6335e2a7f5575ca48722ea7b2fc19aac to your computer and use it in GitHub Desktop.
Download ZIP
fix discord for v2026.5.2 of openclaw
Raw
gistfile1.txt
I checked memory + session logs. I found a clear Discord fix record, but it’s labeled **Forge**, not clawd. The clawd 2026.5.2 work I found was the git/tag rebuild/restart; I don’t see a separate clawd-specific Discord repair note. So either we reused the same fix on clawd, or the host label got fuzzy in the chat.
The Discord fix we documented was:
1. **Installed the official Discord plugin**
```bash
openclaw plugins install @openclaw/discord --pin
```
ClawHub didn’t have an installable version, so direct npm/plugin install worked.
2. **Restarted gateway**
3. Discord still failed because config had:
```text
channels.discord.token = SecretRef env:default:DISCORD_BOT_TOKEN
```
Even though `DISCORD_BOT_TOKEN` existed in `.env` / `gateway.systemd.env`, the plugin saw the unresolved SecretRef and errored before falling back to env.
4. **Removed the explicit token config**
```bash
openclaw config unset channels.discord.token
```
5. Kept the token in:
```text
~/.openclaw/gateway.systemd.env
```
6. Restarted gateway again.
After that status showed:
```text
Discord ON / OK
token source: env
Health: Discord OK
```
Short version: **install `@openclaw/discord`, remove `channels.discord.token`, rely on `DISCORD_BOT_TOKEN` env fallback, restart.**
Source I found: session trace `c6441e2d...`, around the 2026-05-03 04:54 UTC “What did we do to get discord working again?” entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment