Cairn
NousResearch/hermes-agent

Telegram group authorization short-circuit bug

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

A bug where the allow_from setting incorrectly short-circuits group-scoped authorization in the Telegram adapter. Multiple fixes and a bug report address preserving the authorization union across group sources.

Open issues1

  • Issue#68716[Bug] Telegram adapter allow_from short-circuits group-scoped authorization

Open PRs1

  • PR#72084fix(telegram): preserve authorization union across group sources

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #68784 fix(telegram): don't let allow_from short-circuit group authorization (#68716) · done elsewhere → a61183b, #68716
  • #69617 fix(telegram): preserve group authorization union · other
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/68716.json
cluster/68716.md