hermes - 💡(How to fix) Fix [Bug]: Telegram gateway only acknowledges tool requests but never delivers final results

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

Root Cause

Root Cause Analysis (speculative) Likely same root as #19287: gateway routing layer only passes partial data (paths/status) instead of full native result objects back to the Telegram adapter. Tool completion path is broken for TG sessions.

Fix Action

Fix / Workaround

Additional Logs / Traceback Gateway appears to handle initial message and tool dispatch, but fails at final answer routing / delivery for non-trivial tool outputs.

RAW_BUFFERClick to expand / collapse

Bug Description Telegram bot (gateway) acknowledges tool-using requests (e.g. "用 x search 搜 post") with "好的,正在搜索……" but then completely fails to execute the tool result delivery back to the user. The session hangs with no final answer.

This is a follow-up / related manifestation of #19287 (Telegram 图片 bug, gateway 只传路径不走 native routing).

Steps to Reproduce

  1. Use Hermes via Telegram bot
  2. Send message: 用x search,搜索post,关键词gpt image2 提示词
  3. Bot immediately replies: "好的,用 x search 搜 post。关键词:gpt image2 提示词 正在搜索……"
  4. No further messages, no result, task never completes

Expected Behavior Full tool result (x_search answer with prompt guide) should be delivered back in the same Telegram chat.

Actual Behavior Only intermediate "正在搜索" message, then silence. Tool runs successfully on backend but result is never pushed to TG channel.

Affected Component

  • Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform

  • Telegram

Debug Report Run hermes debug share on the host and paste links here (user to provide).

Operating System Linux (6.17.0-23-generic)

Hermes Version Current main (as of 2026-05)

Additional Logs / Traceback Gateway appears to handle initial message and tool dispatch, but fails at final answer routing / delivery for non-trivial tool outputs.

Root Cause Analysis (speculative) Likely same root as #19287: gateway routing layer only passes partial data (paths/status) instead of full native result objects back to the Telegram adapter. Tool completion path is broken for TG sessions.

Proposed Fix Ensure gateway fully routes final agent responses (including long tool outputs) via native TG sendMessage after tool execution, similar to how CLI handles final results.

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

hermes - 💡(How to fix) Fix [Bug]: Telegram gateway only acknowledges tool requests but never delivers final results