Cairn
NousResearch/hermes-agent

Telegram Bot API guest message handling

Cluster 46196 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 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 0 PRs.

These items cover implementing and refining support for Telegram's guest mode, where bots receive and respond to messages from non-member chats via the Bot API. Work includes delivery, answering guest queries, and disabling streaming for those replies.

Open issues1

  • Issue#46196[Bug]: disable streaming for guest replies that use answerGuestQuery

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #43049 feat(telegram): implement Bot API 10.0 guest mode (@mention from non-member chats) · superseded by another PR → #56476, #56477
  • #51082 feat(telegram): deliver and answer Bot API guest messages · superseded by another PR → #43049
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

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/46196.json
cluster/46196.md