hermes - 💡(How to fix) Fix Feishu: group message replies routed to sender's DM instead of group chat [2 pull requests]

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…

Fix Action

Fixed

Code Example

2026-05-11 16:02:03,860 INFO gateway.platforms.feishu: [Feishu] Received raw message type=text message_id=om_xxx
2026-05-11 16:02:03,860 INFO gateway.platforms.feishu: [Feishu] Inbound group message received: id=om_xxx type=text chat_id=oc_4dc303840bf4451a8794a92ce0cae15c sender=user:ou_xxx text='[Mentioned: JessenClaw]...'
2026-05-11 16:02:05,564 INFO gateway.run: inbound message: platform=feishu user=ou_xxx chat=oc_4dc303840bf4451a8794a92ce0cae15c
2026-05-11 16:02:13,606 INFO gateway.run: response ready: platform=feishu chat=oc_4dc303840bf4451a8794a92ce0cae15c time=8.0s
2026-05-11 16:02:13,611 INFO gateway.platforms.base: [Feishu] Sending response (29 chars) to oc_4dc303840bf4451a8794a92ce0cae15c
RAW_BUFFERClick to expand / collapse

Bug Description

When Hermes Agent receives a group message (@mention) on Feishu and generates a response, the gateway log shows the response being sent to the correct group chat_id, but the message actually arrives in the sender's DM instead of the group.

Expected: Reply should appear in the Feishu group chat where the @mention occurred.

Actual: Reply appears in a 1-on-1 DM with the sender.

Environment

  • Hermes Agent version: latest (cloned ~May 2026)
  • Platform: Feishu (Lark)
  • Connection mode: WebSocket
  • Config: FEISHU_GROUP_POLICY=open, allowed_chats: ["*"]

Gateway Log Evidence

2026-05-11 16:02:03,860 INFO gateway.platforms.feishu: [Feishu] Received raw message type=text message_id=om_xxx
2026-05-11 16:02:03,860 INFO gateway.platforms.feishu: [Feishu] Inbound group message received: id=om_xxx type=text chat_id=oc_4dc303840bf4451a8794a92ce0cae15c sender=user:ou_xxx text='[Mentioned: JessenClaw]...'
2026-05-11 16:02:05,564 INFO gateway.run: inbound message: platform=feishu user=ou_xxx chat=oc_4dc303840bf4451a8794a92ce0cae15c
2026-05-11 16:02:13,606 INFO gateway.run: response ready: platform=feishu chat=oc_4dc303840bf4451a8794a92ce0cae15c time=8.0s
2026-05-11 16:02:13,611 INFO gateway.platforms.base: [Feishu] Sending response (29 chars) to oc_4dc303840bf4451a8794a92ce0cae15c

The log clearly shows Sending response to oc_4dc303840bf4451a8794a92ce0cae15c (the correct group chat_id), yet the message arrives in the sender's DM — not in the group.

Steps to Reproduce

  1. Configure Hermes Agent with Feishu WebSocket connection
  2. Set FEISHU_GROUP_POLICY=open and ensure bot is added to a Feishu group
  3. Send a message in the group @mentioning the bot
  4. Observe: bot's reply appears in DM, not in the group

Additional Context

  • DM functionality works correctly
  • Bot receives group messages correctly (confirmed by gateway logs)
  • The issue is specifically in the reply routing — responses to group messages go to DM
  • Similar Telegram/other platform adapters do not exhibit this behavior
  • No existing issues found matching this specific symptom

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