openclaw - 💡(How to fix) Fix Discord stale slash commands remain visible when channels.discord.commands.native=false [1 participants]

Description

When channels.discord.commands.native is set to false, Discord-native slash commands can remain visible/stale in the Discord UI instead of being fully cleared, which creates a confusing broken-command state.

In practice, this looks like:

• OpenClaw config says native Discord commands are disabled
• gateway hot-reload/restart succeeds
• Discord still appears to offer previously registered slash commands
• invoking them leads to broken behavior rather than a clean disappearance from the UI

This feels distinct from the broader “native slash commands return Done / empty response” regression family because here the expectation is that disabling native commands should remove the commands, not leave stale ghosts behind.

Environment

• OpenClaw: 2026.4.8
• OS: Linux 6.8.0-106-generic (x64)
• Node: 24.14.1
• Channel: Discord

Relevant config:

{
  "channels": {
    "discord": {
      "enabled": true,
      "slashCommand": {
        "ephemeral": false
      },
      "commands": {
        "native": false
      }
    }
  }
}

Steps to Reproduce

1. Run OpenClaw with Discord enabled and native commands previously available/registered.
2. Set channels.discord.commands.native to false.
3. Let OpenClaw hot-reload or restart the Discord channel.
4. Observe Discord command availability in the client UI.
5. Try invoking a previously visible slash command.

Expected Behavior

When channels.discord.commands.native=false:

• previously registered native commands should be cleared from Discord cleanly
• users should no longer see those commands in the Discord slash command picker
• there should not be a stale “broken command” UX after disabling native commands

Actual Behavior

• the gateway reload path appears healthy
• Discord reconnect succeeds
• but stale/previously known commands may still remain visible in the client, creating the impression that slash commands are still enabled when they are not

Relevant Logs

Hot reload / reconnect looked normal:

config change detected; evaluating reload (channels.discord.slashCommand)
restarting discord channel
config hot reload applied (channels.discord.slashCommand)
[default] starting provider (@Simplificus)
discord client initialized as ...; awaiting gateway readiness

Gateway health was otherwise fine, and local status tooling worked normally.

Notes

The docs explicitly say native commands should be cleared when disabled:

commands.native=false explicitly clears previously registered Discord native commands.

So if stale commands remain visible after disable + reload/restart, that seems like a bug in command undeploy/cleanup or Discord-side reconciliation behavior.

This may be related to the Carbon reconcile migration, but I’m filing it separately because the user-facing failure mode is specifically about disabled native commands not disappearing cleanly.