Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feishu] Group chat replies not sent (replies=0) — DM works fine [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#77203•Fetched 2026-05-05 05:51:11
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
wangzhe-1992wangzhe-1992
Participants
clawsweeper[bot]clawsweeper[bot]wangzhe-1992wangzhe-1992
Timeline (top)
closed ×1commented ×1

Root Cause

Suspected Root Cause

Fix Action

Workaround

Use DM (direct message) instead of group chat.

Code Example

2026-05-04T16:08:20.157+08:00 [feishu] feishu[jianli]: received message ... in oc_c70dd73a3f7fa1e8eff161075bf3b211 (group)
2026-05-04T16:08:20.162+08:00 [feishu] feishu[jianli]: group session scope=group, peer=oc_c70dd73a3f7fa1e8eff161075bf3b211
2026-05-04T16:08:20.164+08:00 [feishu] feishu[jianli]: Feishu[jianli] message in group: 测试
2026-05-04T16:08:21.287+08:00 [feishu] feishu[jianli]: dispatching to agent (session=agent:jianli:feishu:group:oc_c70dd73a3f7fa1e8eff161075bf3b211)
2026-05-04T16:08:33.130+08:00 [feishu] feishu[jianli]: dispatch complete (queuedFinal=false, replies=0)

---

{
  "channels": {
    "feishu": {
      "groupPolicy": "open",
      "groups": {}
    }
  },
  "accounts": {
    "jianli": {
      "appId": "cli_a949e4e2de3d1bb3",
      "groupAllowFrom": ["oc_c70dd73a3f7fa1e8eff161075bf3b211"]
    }
  }
}
RAW_BUFFERClick to expand / collapse

Bug Description

Feishu channel group chat replies are not being sent to the group. DM (direct message) replies work correctly.

Version: [email protected]

Steps to Reproduce

  1. Send a message in a Feishu group where the bot is present
  2. Bot receives the message and dispatches to agent
  3. Agent model generates a reply (confirmed in trajectory)
  4. dispatch complete shows queuedFinal=false, replies=0 — no reply is sent

Expected vs Actual

Session Typedispatch completeReply sent?
DM (direct)queuedFinal=true, replies=1Yes
Group chatqueuedFinal=false, replies=0No

Agent Trajectory Evidence

Model output is generated correctly for group sessions:

  • assistantTexts: ["收到，王总！监理助理正常运行中 👋"]

But this is never routed to the Feishu channel for sending.

Gateway Logs

2026-05-04T16:08:20.157+08:00 [feishu] feishu[jianli]: received message ... in oc_c70dd73a3f7fa1e8eff161075bf3b211 (group)
2026-05-04T16:08:20.162+08:00 [feishu] feishu[jianli]: group session scope=group, peer=oc_c70dd73a3f7fa1e8eff161075bf3b211
2026-05-04T16:08:20.164+08:00 [feishu] feishu[jianli]: Feishu[jianli] message in group: 测试
2026-05-04T16:08:21.287+08:00 [feishu] feishu[jianli]: dispatching to agent (session=agent:jianli:feishu:group:oc_c70dd73a3f7fa1e8eff161075bf3b211)
2026-05-04T16:08:33.130+08:00 [feishu] feishu[jianli]: dispatch complete (queuedFinal=false, replies=0)

Configuration

{
  "channels": {
    "feishu": {
      "groupPolicy": "open",
      "groups": {}
    }
  },
  "accounts": {
    "jianli": {
      "appId": "cli_a949e4e2de3d1bb3",
      "groupAllowFrom": ["oc_c70dd73a3f7fa1e8eff161075bf3b211"]
    }
  }
}

Suspected Root Cause

Regression in how group session replies are routed back to the Feishu channel send function. DM works fine with the same agent and model.

Workaround

Use DM (direct message) instead of group chat.

extent analysis

TL;DR

The issue can be mitigated by investigating the routing of group session replies to the Feishu channel send function, potentially involving a configuration or code adjustment to correctly handle group chat replies.

Guidance

  • Review the groupPolicy setting in the Feishu channel configuration to ensure it is correctly set to handle group chat replies.
  • Verify that the groupAllowFrom list in the account configuration includes the group ID oc_c70dd73a3f7fa1e8eff161075bf3b211 to confirm that the group is allowed to receive replies.
  • Investigate the difference in handling between DM and group chat replies in the agent and model to identify any discrepancies that might be causing the issue.
  • Check the Feishu API documentation to ensure that the integration is correctly implemented for group chat replies.

Example

No specific code example can be provided without further details on the implementation, but reviewing the code that handles the dispatching of replies to the Feishu channel for group chats might reveal the root cause.

Notes

The provided workaround of using DM instead of group chat is not a permanent solution and does not address the underlying issue. The root cause seems to be related to how group session replies are routed back to the Feishu channel, which needs to be investigated further.

Recommendation

Apply a workaround by using DM for critical communications until the root cause of the group chat reply issue is identified and fixed, as the current implementation seems to have a regression affecting group chat functionality.

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#tensor shape#autograd error#model save/load#optimization

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 [Feishu] Group chat replies not sent (replies=0) — DM works fine [1 comments, 2 participants]