Summary

The messages.statusReactions.emojis config key is silently ignored on Discord. The feature itself works (reactions fire), but custom emoji overrides have no effect — DEFAULT_EMOJIS are always used.

Version

openclaw v2026.2.21-2

Steps to Reproduce

1. Set custom emojis in config:

"messages": {
  "statusReactions": {
    "enabled": true,
    "emojis": {
      "thinking": "🧠",
      "coding": "💻",
      "tool": "🔧"
    }
  }
}

2. Trigger a response in a Discord channel
3. Observe the reactions use default emojis (🤔, 👨‍💻, 🔥) instead of the configured values

Root Cause

In the Discord message handler (pi-embedded-CAmQsy9D.js), createStatusReactionController is called without passing the emojis parameter:

const statusReactions = createStatusReactionController({
  enabled: statusReactionsEnabled,
  adapter: { ... },
  initialEmoji: ackReaction,
  onError: ...
  // ← emojis: cfg.messages?.statusReactions?.emojis is MISSING
});

The Telegram handler presumably passes emojis correctly — only the Discord handler is affected.

Expected Behaviour

Custom emojis from messages.statusReactions.emojis should override DEFAULT_EMOJIS on Discord, the same way they do on other platforms.

Workaround

None. The default emojis (🤔, 👨‍💻, ⚡, 🔥, 👍, 😱, 🥱, 😨) are always used on Discord regardless of config.