#discord integration stopped working after switching from anthropic to codex

1 messages · Page 1 of 1 (latest)

steel gust
#

openclaw no longer responds back on discord / very inconsistant

inner muralBOT
#

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

near yachtBOT
#

First thing: what version?

openclaw --version

Then please run this ladder and paste the redacted output/log bits — don’t paste Discord bot tokens:

openclaw status --all
openclaw gateway status
openclaw channels status --probe
openclaw pairing list discord
openclaw doctor

While reproducing one Discord message, also run:

# 
openclaw logs --follow

Look especially for lines like drop guild message, mention required, pairing request, allowlist, message content intent, or model/auth errors.

Since you mentioned switching from Anthropic to Codex, two likely causes:

  1. Discord guild/channel replies may be “tool-only” now. In Discord guild channels, normal final replies can stay private unless the model calls the message tool. Some models/runtimes are less reliable at doing that, which looks like “it processed but didn’t reply.” Quick test:
openclaw config set messages.groupChat.visibleReplies automatic --strict-json
openclaw gateway restart
  1. Codex route confusion. For Codex subscription OAuth, the usual model prefix is openai-codex/...; native Codex app-server is a different route using openai/... plus agentRuntime.id: "codex". See: https://docs.openclaw.ai/providers/openai