Cairn
NousResearch/hermes-agent

Telegram forum topic thread_id lost in cron delivery

Cluster 16795. 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.

Multiple fixes and reports addressing a bug where explicit thread_id values for Telegram forum topics are dropped or ignored during cron-scheduled message delivery. Covers delivery target resolution, session isolation, and routing logic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #16797 fix: preserve telegram cron topic delivery · other → #16846, #16795
  • #16815 fix(cron): preserve explicit thread_id in delivery target resolution (#16795) · done elsewhere → 6ce796b
Closed issues · 1
  • Closed#16795Cron Telegram topic delivery drops explicit thread_id
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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/16795.json
cluster/16795.md