Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Feishu group chat: replies=0 despite successful dispatch to agent [2 comments, 3 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#77869•Fetched 2026-05-06 06:20:02
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
2
Author
situjieliangsitujieliang
Participants
clawsweeper[bot]clawsweeper[bot]openxxsopenxxssitujieliangsitujieliang
Timeline (top)
commented ×2mentioned ×2subscribed ×2

Fix Action

Fix / Workaround

Bug: Feishu Group Chat — No Reply Sent Despite Successful Dispatch

Issue Summary

Feishu group messages are successfully dispatched to the tang agent (typing indicator appears), but no reply is ever sent — replies=0 in gateway logs. Direct messages (DM) work correctly.

Gateway Log Evidence

All group messages show identical pattern: ``` 2026-05-05T21:46:38.158+08:00 [feishu] feishu[default]: received message from ... in oc_ab8d5d61779baafbdd96324f7b5525d4 (group) 2026-05-05T21:46:38.167+08:00 [feishu] feishu[default]: dispatching to agent (session=agent:tang:feishu:group:oc_ab8d5d61779baafbdd96324f7b5525d4) 2026-05-05T21:46:46.175+08:00 [feishu] feishu[default]: dispatch complete (queuedFinal=false, replies=0) ```

RAW_BUFFERClick to expand / collapse

Bug: Feishu Group Chat — No Reply Sent Despite Successful Dispatch

Environment

  • OpenClaw version: 2026.5.2 (8b2a6e5)
  • macOS (Mac mini)
  • Feishu integration via WebSocket (lark-oapi)

Issue Summary

Feishu group messages are successfully dispatched to the tang agent (typing indicator appears), but no reply is ever sent — replies=0 in gateway logs. Direct messages (DM) work correctly.

Steps to Reproduce

  1. Send any message to a Feishu group where the OpenClaw bot is a member
  2. Observe: bot receives message, typing indicator appears briefly (agent is processing)
  3. After ~8-10 seconds: typing indicator disappears, no reply sent, replies=0

Gateway Log Evidence

All group messages show identical pattern: ``` 2026-05-05T21:46:38.158+08:00 [feishu] feishu[default]: received message from ... in oc_ab8d5d61779baafbdd96324f7b5525d4 (group) 2026-05-05T21:46:38.167+08:00 [feishu] feishu[default]: dispatching to agent (session=agent:tang:feishu:group:oc_ab8d5d61779baafbdd96324f7b5525d4) 2026-05-05T21:46:46.175+08:00 [feishu] feishu[default]: dispatch complete (queuedFinal=false, replies=0) ```

What Works

  • Feishu DM to the same bot: replies correctly (replies=1)
  • Feishu group for other channels (luban, zhangqian): replies=1 ✓

Session Details

  • Group session: `agent:tang:feishu:group:oc_ab8d5d61779baafbdd96324f7b5525d4`
  • Multiple attempts over several hours all resulted in replies=0

Questions

  1. Is there any per-session or per-group configuration that could cause group replies to be silently dropped?
  2. Is there a known issue with the `static` reply mode in group chats?
  3. Any diagnostic commands to further isolate whether the issue is in the agent runtime or the Feishu channel layer?

extent analysis

TL;DR

Investigate per-session or per-group configuration for the Feishu group chat integration to identify potential causes for silently dropped replies.

Guidance

  • Review the configuration for the specific Feishu group session (agent:tang:feishu:group:oc_ab8d5d61779baafbdd96324f7b5525d4) to check for any settings that might be causing replies to be dropped.
  • Compare the configuration of the problematic Feishu group chat with other working group chats (e.g., luban, zhangqian) to identify potential differences.
  • Use diagnostic commands to isolate whether the issue lies in the agent runtime or the Feishu channel layer, focusing on the static reply mode in group chats.
  • Verify if there are any known issues with the static reply mode in group chats that could be contributing to the problem.

Example

No specific code snippet can be provided without further information on the configuration or implementation details.

Notes

The issue seems to be specific to the Feishu group chat integration and the static reply mode. Further investigation into the configuration and diagnostic logs is necessary to determine the root cause.

Recommendation

Apply workaround: Investigate and adjust the per-session or per-group configuration for the Feishu group chat integration, as this seems to be the most likely cause of the issue.

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…
#api#prompt issue#agent setup#task chaining#parallel task

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] Feishu group chat: replies=0 despite successful dispatch to agent [2 comments, 3 participants]