Cairn

Telegram DM topic opening message routed thread-less, misrouted

NousResearch/hermes-agent · cluster 136567 · gateway

Data as of

Nothing open on GitHub. Fix merged in #141751. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #141751. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #141751. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members all concern the opening message of a newly created Telegram DM topic arriving without a thread ID. They describe lobby recovery possibly sending it to the previous topic, and two propose changes to route it to the new topic instead.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #141751 fix(telegram): a new DM topic's first message lands in that topic, not the previous one (#136567, salvage #137348 #140007)

    merged to main

    files: plugins/platforms/telegram/adapter.py, plugins/platforms/telegram/telegram_topic_routing.py, tests/gateway/test_telegram_new_topic_opener.py

4 PRs closed without merging

From the close comments: done elsewhere 3 · other 1

  • #136581 fix(telegram): route a client-created DM topic's thread-less opener to that topic · done elsewhere → ae596f4, #141751
  • #136596 fix(telegram): route a new DM topic's thread-less opening message into that topic · other → #136567
  • #137348 fix(telegram): route a new DM topic's thread-less opening message into that topic · done elsewhere → ae596f4, #141751
  • #140007 fix(telegram): recover threadless DM-topic openers with bounded one-shot pairing · done elsewhere → ae596f4, #141751
Closed issues · 1
  • Closed#136567Telegram DM topics: opening message of a newly created topic is delivered thread-less → lobby recovery misroutes it to the previous topic
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.33: 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
Merged PRs
#141751
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
20 Oct 2026

For your agent

The same facts, typed.

cluster/136567.json
cluster/136567.md