openclaw - 💡(How to fix) Fix [Bug]: statusReactions not implemented for Discord channel

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The messages.statusReactions feature (introduced in OpenClaw 2026.2.17) works on Slack and Telegram but is not implemented for Discord. When messages.statusReactions.enabled: true is configured, no status reactions (thinking, tool, done, error) appear on Discord messages.

Error Message

The messages.statusReactions feature (introduced in OpenClaw 2026.2.17) works on Slack and Telegram but is not implemented for Discord. When messages.statusReactions.enabled: true is configured, no status reactions (thinking, tool, done, error) appear on Discord messages. "error": "❌" "error": "❌" Expected: Status reactions appear on the message as the agent progresses through its lifecycle (thinking → tool → done/error), similar to Slack and Telegram behavior When an agent processes a Discord message, status reactions should appear on the triggering message showing the agent's progress (queued → thinking → tool → done/error), similar to how it works on Slack and Telegram.

Root Cause

The messages.statusReactions feature (introduced in OpenClaw 2026.2.17) works on Slack and Telegram but is not implemented for Discord. When messages.statusReactions.enabled: true is configured, no status reactions (thinking, tool, done, error) appear on Discord messages.

Fix Action

Workaround

None currently. Manual message(action="react") also doesn't appear to be exposed as an agent tool for Discord sessions.

Code Example

{
  "messages": {
    "statusReactions": {
      "enabled": true,
      "emojis": {
        "thinking": "🤔",
        "tool": "🛠️",
        "done": "✅",
        "error": "❌"
      }
    }
  }
}

---

{
  "messages": {
    "statusReactions": {
      "enabled": true,
      "emojis": {
        "thinking": "🤔",
        "tool": "🛠️",
        "done": "✅",
        "error": "❌"
      }
    }
  }
}

---

openclaw gateway restart

---
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Description

The messages.statusReactions feature (introduced in OpenClaw 2026.2.17) works on Slack and Telegram but is not implemented for Discord. When messages.statusReactions.enabled: true is configured, no status reactions (thinking, tool, done, error) appear on Discord messages.

Environment

  • OpenClaw version: 2026.5.7
  • Channel: Discord
  • Config:
{
  "messages": {
    "statusReactions": {
      "enabled": true,
      "emojis": {
        "thinking": "🤔",
        "tool": "🛠️",
        "done": "✅",
        "error": "❌"
      }
    }
  }
}

Investigation

I checked the source code in node_modules/openclaw/dist/ and found:

  1. createStatusReactionController exists in channel-feedback-60McoBqr.js and is shared across channels
  2. It's called with slackStatusAdapter in pipeline.runtime-BdXdKqqG.js (Slack)
  3. It's called with a custom Telegram adapter in bot-Ce301bOE.js (Telegram)
  4. The Discord plugin (plugin-sdk/discord.js, 5390 chars) contains zero reaction codecreateStatusReactionController is never called with a Discord adapter

Related

  • GitHub issue #21793: ackReaction auto-fire is buggy on Discord (separate but related)
  • The ackReaction feature also has known issues on Discord (random emojis instead of configured one)

Workaround

None currently. Manual message(action="react") also doesn't appear to be exposed as an agent tool for Discord sessions.

Steps to reproduce

  1. Set up OpenClaw 2026.5.7 with a Discord bot connected to a server

  2. Add the following config to ~/.openclaw/openclaw.json:

{
  "messages": {
    "statusReactions": {
      "enabled": true,
      "emojis": {
        "thinking": "🤔",
        "tool": "🛠️",
        "done": "✅",
        "error": "❌"
      }
    }
  }
}
  1. Restart the gateway:
openclaw gateway restart
  1. Send a message to the Discord bot (mention it in a channel or DM)

  2. Observe the triggering message on Discord

Expected: Status reactions appear on the message as the agent processes it (🤔 when thinking, 🛠️ when using tools, ✅ when done)

Expected: Status reactions appear on the message as the agent progresses through its lifecycle (thinking → tool → done/error), similar to Slack and Telegram behavior

Actual: No reactions appear on the Discord message at any point during processing

Verification:

  • Run openclaw config get messages.statusReactions — shows config is correctly set
  • Run openclaw channels status --probe — shows Discord is connected and working
  • Run openclaw logs — no reaction-related errors appear (feature is silently not implemented)

Expected behavior

When an agent processes a Discord message, status reactions should appear on the triggering message showing the agent's progress (queued → thinking → tool → done/error), similar to how it works on Slack and Telegram.

Actual behavior

No status reactions appear on Discord messages. The config validates successfully but nothing happens at runtime.

OpenClaw version

2026.5.7

Operating system

Windows 11

Install method

npm install -g openclaw@latest

Model

openrouter

Provider / routing chain

openrouter/deepseek/deepseek-v4-flash:free

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When an agent processes a Discord message, status reactions should appear on the triggering message showing the agent's progress (queued → thinking → tool → done/error), similar to how it works on Slack and Telegram.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: statusReactions not implemented for Discord channel