Set Up OpenClaw Discord Access
Connect a Discord bot to OpenClaw and prove the access path you intend to use first, either a paired DM or a reply in one server channel. A bot that appears in the server still needs a separate test of the Gateway connection and the intended conversation.
Choose the first conversation before inviting the bot
OpenClaw supports Discord DMs and guild channels, the channels inside a Discord server. Use a DM first when one operator needs private access. Use a single server channel first when a group needs to see the exchange. Write down the expected sender, destination, and reply so the installer and tester agree on what counts as a working setup.
Create the application in the Discord Developer Portal, open its Bot settings, and obtain the token for the OpenClaw configuration. For a server test, use the app's install flow to invite the bot to the test server and give it access to view and send messages in the chosen channel. Confirm it appears in the intended server. Defer permissions for actions outside the reply test.
Use different trace IDs for a direct message and a guild interaction. Test the actual channel and permissions intended for release.
Discord - OpenClawVerify the running Discord connection
Enable Discord in the OpenClaw Gateway's Discord configuration and set the bot token there. Use the setup instructions for your installed version to apply the change to the Gateway that serves the agent. Keep the token out of shared terminal output and keep the Discord application identity beside the instance name in your setup notes.
Run openclaw channels status --probe against that Gateway and inspect the Discord entry. If it is missing, check that Discord is configured on this instance. If it reports running: false with lifecycle: blocked and a plugin error, follow the documented repair flow. Run openclaw doctor, repair or update the plugin, restart the Gateway, and probe again. Once the channel is running, move on to a conversation test.
If only one path works, compare its received-event and policy checkpoints before changing credentials used by both paths.
Channels - OpenClawTest against a named sender and channel
In this illustrative setup, Priya is the operator, Field Lab is the test server, and agent-test is the only channel intended for shared replies. Priya opens a DM to the bot and asks it to reply with PRIVATE-7. If the default pairing policy returns an approval request, she verifies the sender, approves it through OpenClaw, and resends the prompt. The private test passes when the reply arrives in that DM.
For the server test, record the intended server and channel IDs, check the guild access policy, and have Priya mention the bot in agent-test with a request to reply with SHARED-7. If both paths are required, record them as two acceptance results. If the DM passes and the server test fails, keep the working connection and focus on the server-side path.
Discord - OpenClawTrace a server-only failure
If a paired DM works but the bot ignores the server, start with the exact channel and sender that failed. Check that Discord lets the bot view and send in that channel, then check OpenClaw's guild allowlist and mention gating. Try an explicit mention from an intended user. If mentions work and ordinary messages are required, verify the applicable Message Content Intent settings in the Developer Portal and the OpenClaw setup guide before changing the rollout.
If an operator can get replies and a teammate cannot, compare their access in the same channel with the same prompt. Change the setting that explains the difference and repeat both tests. This keeps a narrow rollout useful while you identify which additional users or message behaviors the team actually needs.
Discord - OpenClaw