Discord Commands after the October Fixes

v2026.10.6 lists Discord command repairs (plus Windows setup and iPhone Talk). Use this page if slash commands vanished, doubled, or started erroring after a 10.x upgrade. First-time bot token and intents still live on Connect OpenClaw to Discord.

Confirm you are on 10.6 or later before you rotate the bot token. Command registration bugs look like permission bugs.

After you upgrade

  1. Restart the Gateway so the Discord plugin loads the patched command code.
  2. In Discord, check whether the bot still has the application-commands scope. Re-invite with the same permissions if the command tree is empty.
  3. Wait a few minutes; Discord command sync is not always instant.
  4. Test in a private server, not production, if you run several OpenClaw bots.

If commands still fail

  • Guild vs global registration: a leftover global command from an older install can shadow the new one. Remove stale commands in the Discord developer portal.
  • Privileged intents: message-content still required for channel chat; commands failing independently usually means the command payload, not intents.
  • Logs: openclaw logs --follow while you invoke the slash command. Channel-level help: channel troubleshooting.

Related