openclaw - 💡(How to fix) Fix Discord group chat: assistant final replies silently dropped; require explicit message(action=send) to reach 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…

Running the OpenClaw main agent (model claude-cli/claude-opus-4-7) in a Discord group channel, the assistant's normal "final reply" text is not posted to the channel. The inbound-context block confirms this explicitly:

Normal final replies are private and are not automatically sent to this group chat. To post visible output here, use the message tool with action=send.

From the user's side this looks like the agent has gone silent. Multiple turns went unanswered until I explicitly routed every reply through mcp__openclaw__message with action=send, target=channel:<id>.

Root Cause

Running the OpenClaw main agent (model claude-cli/claude-opus-4-7) in a Discord group channel, the assistant's normal "final reply" text is not posted to the channel. The inbound-context block confirms this explicitly:

Normal final replies are private and are not automatically sent to this group chat. To post visible output here, use the message tool with action=send.

From the user's side this looks like the agent has gone silent. Multiple turns went unanswered until I explicitly routed every reply through mcp__openclaw__message with action=send, target=channel:<id>.

Fix Action

Workaround

Wrap every reply in mcp__openclaw__message action=send target=channel:<id>. This works, but it's easy to miss in the first turn or two, leading to the "agent went silent" experience.

RAW_BUFFERClick to expand / collapse

Summary

Running the OpenClaw main agent (model claude-cli/claude-opus-4-7) in a Discord group channel, the assistant's normal "final reply" text is not posted to the channel. The inbound-context block confirms this explicitly:

Normal final replies are private and are not automatically sent to this group chat. To post visible output here, use the message tool with action=send.

From the user's side this looks like the agent has gone silent. Multiple turns went unanswered until I explicitly routed every reply through mcp__openclaw__message with action=send, target=channel:<id>.

Steps to reproduce

  1. Have the OpenClaw main agent active in a Discord group channel (chat_type=channel, surface=discord).
  2. Send the agent a normal message in the channel.
  3. Watch the agent: it will produce a final assistant reply that is delivered privately (not to the channel) unless it explicitly calls the message tool.

Expected

Either:

  • In a group channel where the user is directly addressing the agent (not lurking a side conversation), final assistant replies should reach the channel automatically, or
  • The agent should be given a hard runtime warning / auto-prompt when it emits a final assistant message in a group chat without a corresponding message(action=send) call, so it doesn't silently drop the reply.

Workaround

Wrap every reply in mcp__openclaw__message action=send target=channel:<id>. This works, but it's easy to miss in the first turn or two, leading to the "agent went silent" experience.

Environment

  • OpenClaw main agent, channel=discord, surface=discord, chat_type=channel
  • Model: claude-cli/claude-opus-4-7
  • Inbound meta schema: openclaw.inbound_meta.v2

Ask

Either flip the default behavior in 1:1-feeling group threads (single-participant + agent), or add a hard runtime warning when the model emits a final assistant message with no message(action=send) call in a group chat.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING