Cairn
NousResearch/hermes-agent

Telegram DM thread_id routing and fallback fixes

Cluster 35739 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

Multiple fixes and bug reports addressing invalid or spurious message_thread_id values being sent in Telegram DM contexts, with various fallback and normalization strategies proposed. The members share a common theme around thread routing errors in non-forum Telegram DMs.

Open issues1

  • Issue#35739[Bug]: Fix media routing to "All Chats" in Telegram DM Topics (Reply Fallback)

Open PRs1

  • PR#35759fix(telegram): omit message_thread_id in DM topic fallback sends with reply anchor (#35739)

3 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1 · other 1

  • #12853 fix(telegram): route model-picker thread_id through _message_thread_id_for_send · other → #12839
  • #12873 fix: use _message_thread_id_for_send() in send_model_picker() for forum topics · done elsewhere → #22410, #22053, #22423, #22267
  • #28605 fix(telegram): preserve new DM topic lanes · merged via another change → 14ad7b2, #31444, #31086
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.40: 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
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/35739.json
cluster/35739.md