Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feishu group replies silently broken after v2026.4.27 — messages.groupChat.visibleReplies default changed without documentation [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#74943•Fetched 2026-05-01 05:39:47
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
AxelHuAxelHu
Participants
AxelHuAxelHuclawsweeper[bot]clawsweeper[bot]
Timeline (top)
closed ×1commented ×1

Error Message

After upgrading to v2026.4.27, Feishu group @mention replies stopped being delivered to Feishu — no error, no log entry, the reply appears in gateway UI but never reaches the Feishu group. Reply only appears in gateway UI session history; no Feishu message is sent. No error is logged. The deliver callback is never invoked because sourceReplyDeliveryMode resolves to "message_tool_only".

Root Cause

Root cause identified: commit 3c636208b0 ("keep group/channel replies private by default unless the agent explicitly uses the message tool") changed the default value of messages.groupChat.visibleReplies from "automatic" to "message_tool_only". This was documented only in the Discord section of the changelog, but the code applies to all channel types including Feishu.

Code Example

Discord/group chats: keep group/channel replies private by default unless the agent explicitly uses the message tool, so always-on rooms can lurk without leaking automatic final, block, preview, or status-reaction output; messages.groupChat.visibleReplies: "automatic" restores legacy auto-posting. (#73046)
RAW_BUFFERClick to expand / collapse

Bug Description

After upgrading to v2026.4.27, Feishu group @mention replies stopped being delivered to Feishu — no error, no log entry, the reply appears in gateway UI but never reaches the Feishu group.

Root cause identified: commit 3c636208b0 ("keep group/channel replies private by default unless the agent explicitly uses the message tool") changed the default value of messages.groupChat.visibleReplies from "automatic" to "message_tool_only". This was documented only in the Discord section of the changelog, but the code applies to all channel types including Feishu.

Steps to Reproduce

  1. Have a Feishu group with an always-on bot
  2. Send an @mention to the bot in the group (no messages.groupChat.visibleReplies configured)
  3. Bot responds in gateway UI but the reply is not delivered to the Feishu group

Expected Behavior

Without any configuration, bot should reply in the Feishu group as it did before v2026.4.27.

Actual Behavior

Reply only appears in gateway UI session history; no Feishu message is sent. No error is logged. The deliver callback is never invoked because sourceReplyDeliveryMode resolves to "message_tool_only".

Changelog Reference

Discord/group chats: keep group/channel replies private by default unless the agent explicitly uses the message tool, so always-on rooms can lurk without leaking automatic final, block, preview, or status-reaction output; messages.groupChat.visibleReplies: "automatic" restores legacy auto-posting. (#73046)

This entry only mentions Discord but the code in resolveSourceReplyDeliveryMode applies to Feishu and all other channels with chatType === "group" || chatType === "channel".

Questions

  1. Was this change intentional for Feishu group chats, or was Feishu accidentally included in the scope of this refactor?
  2. If intentional, should this be listed as a breaking change in the release notes since it silently breaks existing always-on Feishu group deployments with no configuration present?
  3. If unintentional, should a fix be prepared to exclude Feishu from this behavior, or should the default for Feishu remain "automatic"?

Suggested Fix (if unintentional)

Either:

  • Restore the default to "automatic" for Feishu channels, OR
  • Add Feishu to the explicit list of channels where "message_tool_only" is the default, while preserving legacy behavior for existing installations

Environment

  • OpenClaw version: v2026.4.27
  • Channel: Feishu (group chat)
  • Configuration: No messages.groupChat config present (was implicit before)

extent analysis

TL;DR

To fix the issue with Feishu group @mention replies not being delivered after upgrading to v2026.4.27, configure messages.groupChat.visibleReplies to "automatic".

Guidance

  • Review the changelog reference and understand the change in default behavior for group/channel replies.
  • Verify that the issue is caused by the new default value of messages.groupChat.visibleReplies being set to "message_tool_only".
  • Consider configuring messages.groupChat.visibleReplies to "automatic" to restore the legacy behavior.
  • If the change was unintentional, a fix may be prepared to exclude Feishu from this behavior or restore the default to "automatic" for Feishu channels.

Example

// Example configuration to restore legacy behavior
messages: {
  groupChat: {
    visibleReplies: "automatic"
  }
}

Notes

The suggested fix assumes that the change was unintentional and that restoring the default to "automatic" for Feishu channels is the desired behavior. However, if the change was intentional, it may be necessary to update existing installations to use the new default behavior.

Recommendation

Apply workaround: configure messages.groupChat.visibleReplies to "automatic" to restore the legacy behavior until a fix is prepared or the change is confirmed to be intentional.

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…
#installation#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING