Description

Plugin-registered slash commands (e.g. /lcm, /lossless from lossless-claw) are silently excluded from Slack, even though:

1. Slack declares capabilities.nativeCommands: true
2. The user explicitly sets channels.slack.commands.native: true in config

The same commands work correctly on Telegram and Discord.

Root cause

getPluginCommandSpecs() in src/plugins/command-registry-state.ts gates on nativeCommandsAutoEnabled, which Slack intentionally sets to false:

if (providerName && getChannelPlugin(providerName)?.commands?.nativeCommandsAutoEnabled !== true) {
  return [];
}

This is a double-gate: the Slack provider already checks resolveNativeCommandsEnabled() (which respects user config) before calling getPluginCommandSpecs("slack"). But getPluginCommandSpecs ignores the user's config and only checks the bundled plugin's nativeCommandsAutoEnabled flag.

Additionally, the Slack extension's slash.ts does not call getPluginCommandSpecs at all — so even if the gate were fixed, plugin commands would not be included in the native command list.

Expected behavior

When a channel plugin declares capabilities.nativeCommands: true and the user enables native commands via config, plugin-registered commands should be included in the native command list for that channel.

Steps to reproduce

1. Install a plugin that registers commands (e.g. lossless-claw with /lcm and /lossless)
2. Configure Slack with commands.native: true
3. Try /lcm or /lossless in Slack → nothing happens
4. Try the same in Telegram → works correctly

Environment

• OpenClaw version: 2026.4.9
• Channel: Slack (socket mode)
• Plugin: lossless-claw