Cairn
NousResearch/hermes-agent

Telegram gateway routing and message leakage fixes

Cluster 37555 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address bugs in the Telegram gateway involving out-of-context replies, duplicate messages, tool-trace leakage, stale generation responses, and DM-topic routing. The work is focused on correcting message handling and routing correctness in the Telegram integration.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: partial fix 1 · superseded by another PR 1

  • #37698 fix(gateway): drop stale generation final responses · superseded by another PR → #38732
  • #38732 fix(gateway): prevent Telegram duplicate messages and tool-trace leakage (#36965 #37555) · partial fix → #36965, #37555
Closed issues · 1
  • Closed#37555[Bug]: Telegram gateway replies out-of-context (tool trace leakage + duplicated messages)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/37555.json
cluster/37555.md