Cairn
NousResearch/hermes-agent

Telegram channel post handling fixes

Cluster 3634 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues 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
1 issue and 1 PR.

These issues and pull requests address a gap where the Telegram adapter was not processing channel_post (and related) update types. The changes add or correct handlers and routing so channel posts are treated consistently alongside group messages.

Open issues1

  • Issue#3634Telegram adapter does not process channel_post updates

Open PRs1

  • PR#28614fix(telegram): handle channel_post media via effective_message

2 PRs closed without merging

From the close comments: stale or abandoned 1 · superseded by another PR 1

  • #3683 fix(telegram): add channel_post and edited_channel_post handlers · stale or abandoned
  • #53675 fix(telegram): route channel posts through the same gates as groups · superseded by another PR → #53750, #54280
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.50: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/3634.json
cluster/3634.md