#Bug: Discord bot connects but never receives messages

1 messages · Page 1 of 1 (latest)

worn mason
#
  • Genspark Claw v0.1.668 (macOS, Apple Silicon M1)
  • Discord bot logs show "logged in" and "WebSocket connection opened"
  • But gatewayConnected stays false at fetch-bot-identity:done
  • Bot never receives MESSAGE_CREATE or INTERACTION_CREATE events
  • Slash commands appear in Discord UI but don't trigger responses
  • REST API works fine (can send messages to channels)
  • Direct WebSocket test (python websocket-client) gets READY event instantly
  • All Privileged Gateway Intents enabled
  • Problem only occurs with desktop app's embedded gateway; LaunchAgent gateway worked once (gatewayConnected=true)
  • Tried: remove/re-add channel, restart app, multiple gateway restarts

OpenClaw version: 2026.3.13 (61d171a)
App version: 0.1.668

burnt escarpBOT
#

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

soft nightBOT
#

This looks much more like a 2026.3.13 Discord gateway/Carbon READY race than a Discord permissions/intents problem.

Why: REST send works + your direct WS test gets READY instantly, so the token/intents/network path is basically proven. fetch-bot-identity:done gatewayConnected=false is before OpenClaw’s final gateway readiness wait; if it never flips true afterward, the embedded gateway is stuck before READY, so no MESSAGE_CREATE / INTERACTION_CREATE listeners will matter.

I’d do this first:

npm install -g openclaw@latest
openclaw gateway restart
openclaw channels status --probe
openclaw logs --follow

Docs: https://docs.openclaw.ai/channels/discord and https://docs.openclaw.ai/channels/troubleshooting

If the desktop app’s embedded gateway still fails but the LaunchAgent gateway works, use the LaunchAgent/service gateway as the workaround for now. There have been several Discord gateway fixes after 2026.3.13, including READY/startup recovery and stale socket handling, so updating is the highest-signal next step.

#

If it still repros on a current build, please file a GitHub issue with:

  • OpenClaw version + app version
  • whether embedded gateway vs LaunchAgent
  • logs around discord startup, Gateway websocket opened, READY, runtime-not-ready, startup-not-ready
  • output of openclaw channels status --probe

Issue tracker: https://github.com/openclaw/openclaw/issues