NousResearch/hermes-agent

Telegram group mention gating and bot-message handling

Cluster 54370 · 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.

Most members concern Telegram group messages and mention rules: one reports that the require_mention gate can be bypassed during an active group session, and two propose changes to how active-session messages are filtered. A fourth adds a TELEGRAM_ALLOW_BOTS option (none/mentions/all), which is related but a distinct feature.

Open issues1

  • Issue#54370bug(gateway): require_mention gate bypassed when message arrives during active group session

Open PRs1

  • PR#115252fix(telegram): drop no-mention group msgs during active session

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #54374 feat(telegram): add TELEGRAM_ALLOW_BOTS support (none/mentions/all) · done elsewhere → fc70d02, #54370
  • #54709 fix(telegram): gate active-session dispatch by mention rules · superseded by another PR → #54370, #54374
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.