hermes - 💡(How to fix) Fix [Bug]: 飞书消息回复异常,回复消息发送到非目标用户/群聊 [1 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…

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

Code Example

因网络限制,对hermes debug share --local输出部分日志分析如下:
 找到了问题根源!

    从session文件中看到send_message工具调用:

    json
    {
      "action": "send",
      "target": "feishu",
      "message": "专利交底书流程图已优化完成..."
    }


    问题:target参数只写了"feishu",没有指定chat_id!

    根据send_message工具定义:
    - target: "feishu" → 发送到home channel(默认行为)
    - target: "feishu:oc_35780c18ab5ecafc198cd7752ab315d7" → 发送到xxx私聊

    正确的调用应该是:
    json
    {
      "action": "send",
      "target": "feishu:oc_xxx",
      "message": "..."
    }


    根本原因:
    调用send_message时没有传递完整的target参数(platform:chat_id格式),导致消息fallback到home channel。

    解决方案:
    1. 在gateway会话中使用send_message时,必须从当前会话上下文获取chat_id
    2. 或者应该使用gateway的回复机制而不是send_message工具

---

--local 参数已生效,调试报告直接输出到终端,未上传远程服务器。

    报告摘要:


    version:      0.12.0 (2026.4.30)
    os:           Linux 5.19.17-saturnv01 x86_64
    python:       3.11.15
    profile:      default
    model:        HORIZON-GLM
    provider:     custom
    gateway:      running (manual, pid 140131)
    platforms:    feishu
    cron_jobs:    6 active / 6 total
    skills:       146


    配置覆盖项:
    - agent.max_turns: 50
    - display.streaming: True

    如需保存到文件:

    bash
    hermes debug share --local > ~/hermes-debug-$(date +%Y%m%d).txt
RAW_BUFFERClick to expand / collapse

Bug Description

飞书消息回复到错误的会话

Steps to Reproduce

1、设置home channel后 2、在多个群聊/单聊和它聊天

Expected Behavior

飞书消息回复到正确的会话

Actual Behavior

飞书消息回复到错误的会话

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

No response

Debug Report

因网络限制,对hermes debug share --local输出部分日志分析如下:
 找到了问题根源!

    从session文件中看到send_message工具调用:

    json
    {
      "action": "send",
      "target": "feishu",
      "message": "专利交底书流程图已优化完成..."
    }


    问题:target参数只写了"feishu",没有指定chat_id!

    根据send_message工具定义:
    - target: "feishu" → 发送到home channel(默认行为)
    - target: "feishu:oc_35780c18ab5ecafc198cd7752ab315d7" → 发送到xxx私聊

    正确的调用应该是:
    json
    {
      "action": "send",
      "target": "feishu:oc_xxx",
      "message": "..."
    }


    根本原因:
    调用send_message时没有传递完整的target参数(platform:chat_id格式),导致消息fallback到home channel。

    解决方案:
    1. 在gateway会话中使用send_message时,必须从当前会话上下文获取chat_id
    2. 或者应该使用gateway的回复机制而不是send_message工具

Operating System

Ubuntu 24.04

Python Version

3.11.15

Hermes Version

0.12.0

Additional Logs / Traceback (optional)

--local 参数已生效,调试报告直接输出到终端,未上传远程服务器。

    报告摘要:


    version:      0.12.0 (2026.4.30)
    os:           Linux 5.19.17-saturnv01 x86_64
    python:       3.11.15
    profile:      default
    model:        HORIZON-GLM
    provider:     custom
    gateway:      running (manual, pid 140131)
    platforms:    feishu
    cron_jobs:    6 active / 6 total
    skills:       146


    配置覆盖项:
    - agent.max_turns: 50
    - display.streaming: True

    如需保存到文件:

    bash
    hermes debug share --local > ~/hermes-debug-$(date +%Y%m%d).txt

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

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