NousResearch/hermes-agent

Telegram inline callback auth routing bug and fix

Cluster 86296 · gateway. Data as of

Nothing open on GitHub. Fix merged in #101250 on 2 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #101250. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #101250. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug causes Telegram inline callbacks to reject profile-authorized users under multiplex routing. The associated fixes route inline-callback authentication through the profile-aware runner path and ensure gateway-level inline buttons and early auth honor the correct routed profile, bot policy, and per-profile gates.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #101250 fix(gateway): inline-button and early auth honor the routed profile, bot policy and per-profile Slack gates (#86296 #92840, salvage #65589 #86308 #72657)

    merged to main

    files: gateway/authz_mixin.py, gateway/channel_directory.py, gateway/platforms/base.py, gateway/run.py, plugins/platforms/slack/adapter.py, plugins/platforms/telegram/adapter.py, tests/gateway/test_multiplex_interactive_auth.py, tests/gateway/test_telegram_callback_auth_fail_closed.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #86308 fix(telegram): route inline-callback auth through the profile-aware runner path (#86296) · merged via another change → 11f932c, #101250, #65589
Closed issues · 1
  • Closed#86296[Bug]: Telegram inline callbacks reject profile-authorized users under multiplex routing
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
Merged PRs
#101250
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.