#After upgrading to 5.4, Discord channels seem to be unconfigured

1 messages · Page 1 of 1 (latest)

bronze portal
#

After upgrading to 5.4, Discord channels seem to be unconfigured, not working, and there are no related startup logs. Has anyone else encountered this?

burnt currentBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

spiral flame
#

I've had countless issues with Discord after anything 5.x, including today's 5.4. I've had to roll back to 4.25 to get them working again, and I've spent hours trying. If Discord is your primary channel, I suggest holding off until they issue a proven patch for these issues.

clear current
#

no discord for me as well after trying to update to 5.4. Back to 4.23. I've tried so many versions and I can't seem to get pass 4.23 without breaking it.

fickle garden
#

thanks for posting, discord integration been a nightmare for me also, gonna hold off then as discord is my main platform

patent jasper
#

yeah i just updated yesterday and man, everything broke

#

i think i semi-fixed it, but i have no idea how

#

i just like reinstalled the discord plugin with npm and enabled it in the config

#

specifically this:

  "plugins": {
    "entries": {
      ...
      "discord": {
        "enabled": true
      }
    },
    "allow": [
      ...
      "discord"
    ],
    "bundledDiscovery": "compat"
  },
#

npm install --prefix ~/.openclaw/npm @openclaw/discord@latest --force

#

something like that

granite sundial
#

the recent versions of discord plugin will simply not start at all if they don’t see the secret token. I’ve been having a heck of time getting the secret token to be visible — on Mac my gateway install force isn’t adding the .env vars into the launchd env.

limber thorn
#

If Discord bots stop coming online after an OpenClaw update, check:

openclaw status --deep
openclaw doctor --non-interactive

What fixed it for me was reinstalling/enabling the Discord plugin and making the Discord accounts explicit in config.

Install/reinstall the plugin:

Windows:

npm install --prefix C:\Users\<YOU>\.openclaw\npm @openclaw/discord@latest --save-exact --force

Mac/Linux:

npm install --prefix ~/.openclaw/npm @openclaw/discord@latest --save-exact --force

Then make sure config has Discord plugin enabled:

{
  "plugins": {
    "entries": {
      "discord": {
        "enabled": true
      }
    },
    "bundledDiscovery": "compat"
  }
}

If you use multiple Discord bots/accounts, make sure each bot is under:

channels.discord.accounts

If your main/default bot is still configured only at top level, copy/migrate it into:

channels.discord.accounts.default

Example shape:

{
  "channels": {
    "discord": {
      "enabled": true,
      "defaultAccount": "default",
      "accounts": {
        "default": {
          "enabled": true,
          "token": "***",
          "groupPolicy": "allowlist",
          "allowFrom": ["<your discord user id>"],
          "allowBots": "mentions",
          "guilds": {
            "<guild id>": {
              "channels": {
                "<channel id>": {
                  "enabled": true,
                  "requireMention": false,
                  "users": ["<your discord user id>"]
                }
              }
            }
          }
        }
      }
    }
  },
  "messages": {
    "groupChat": {
      "visibleReplies": "message_tool"
    }
  }
}

Restart and verify:

openclaw gateway restart
openclaw status --deep
openclaw doctor --non-interactive

Healthy status should look roughly like:

Discord  ON  OK  token config×N · accounts N/N

Notes:

  • Don’t paste bot tokens into Discord/support chats.
  • Don’t set plugins.allow: ["discord"] unless you intentionally want to allowlist only Discord.
  • If doctor mentions groupAllowFrom but config rejects it, use allowFrom instead.
#

My bot fixed my discord after the 5.4 update and this is what he said he did.

gusty abyss
#

solution is to prompt openclaw: set visibleReplies to automatic

lapis knot
#

That's what fixed mine as well, the visibleReplies setting

unborn mortar
#

Openclaw 5.4 (5.x) fix if your bot isn't responding on Discord channels, whatsapp or telegram group chats:

messages.groupChat.visibleReplies is now set to message_tool_only by default which silently kills setups that rely on group channels. The change is intentional as group messages are seen as less secure and more noisy. This workaround will restore previous behaviour for setups that prefer immediate response.

openclaw config set messages.groupChat.visibleReplies automatic
granite sundial
bronze portal