NousResearch/hermes-agent
Fix Telegram reply threading in forum/multipart messages
Cluster 55059 · gateway. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and fixes address incorrect thread ID handling and message chunking behavior when sending replies on Telegram, particularly for forum topics and multi-part first replies where early chunks may be lost or misrouted.
Open issues1
- Issue#55059Telegram multi-chunk first replies can hide the first chunk
Open PRs1
- PR#55060Fix Telegram multipart first replies
1 PR closed without merging
From the close comments: done elsewhere 1
-
#12873 fix: use _message_thread_id_for_send() in send_model_picker() for forum topics · done elsewhere →
#22410,#22053,#22423,#22267
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.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 0
- Attempts
- 1 PR closed without merging