Bug

The messages.statusReactions.emojis config overrides are only passed to createStatusReactionController in the Telegram handler. The Discord handler creates the controller without passing emojis or timing from config, so Discord always uses the hardcoded defaults:

// src/channels/status-reactions.ts
const DEFAULT_EMOJIS = {
  queued: "👀",
  thinking: "🤔",
  tool: "🔥",
  coding: "👨💻",
  web: "⚡",
  done: "👍",
  error: "😱",
  stallSoft: "🥱",
  stallHard: "😨"
};

Expected

Setting messages.statusReactions.emojis.thinking: "🧠" (etc.) should apply to Discord the same way it does for Telegram.

Where

In the Discord reply handler (reply-*.js), the call to createStatusReactionController only passes enabled, adapter, initialEmoji, and onError — missing emojis and timing from cfg.messages.statusReactions.

The Telegram handler correctly reads these:

const statusReactionsConfig = cfg.messages?.statusReactions;
// ...
overrides: statusReactionsConfig?.emojis

Fix

Pass emojis and timing from cfg.messages.statusReactions to the Discord createStatusReactionController call, same as Telegram.

Version

2026.2.23 (b817600)