OpenClaw on Discord
Connect OpenClaw to a Discord bot by hand, start the gateway, and approve pairing.
This page connects OpenClaw, running on a computer, to a Discord bot. It follows OpenClaw setup. To message Cue from Discord without OpenClaw, use Discord, which connects through Cue CLI.
These steps are manual and have not been checked end to end on Cue OS. On current Cue computers, openclaw channels list --all shows Discord as not installed, so this setup will not work there until the Discord plugin is added. Adding it was not tested. Cue also already runs the OpenClaw gateway on port 18789 on those computers, so the start commands below use --force to replace it.
1. Add the bot to OpenClaw
After onboarding succeeds, add the Discord bot token:
openclaw config set channels.discord.enabled true --json
openclaw config set channels.discord.token "<DISCORD_BOT_TOKEN>"
openclaw config set channels.discord.groupPolicy allowlist
openclaw config set channels.discord.streaming offTreat the bot token like a password.
2. Start the gateway
mkdir -p ~/.openclaw/logs
nohup openclaw gateway --force > ~/.openclaw/logs/gateway-sandbox.log 2>&1 &
sleep 4Check the gateway:
openclaw gateway status
tail -n 60 ~/.openclaw/logs/gateway-sandbox.logWhat you want to see:
Connectivity probe: ok- a log line like
logged in to discord as ...
openclaw gateway status also reports the background service as disabled. That is expected on a computer without a background service manager.
3. Pair the bot
When you message the bot for the first time, it may answer with your Discord user ID and a pairing code. Approve that code on the computer:
openclaw pairing approve discord <PAIRING_CODE>Then message the bot again.
Discord access and model access are separate. If Discord connects but the bot does not give real replies, finish Model auth.
Next: Model auth.