Telegram multiplex profile isolation and routing fixes
Cluster 87239 · gateway. Data as of
Nothing open on GitHub. Fix merged in #101250 on 2 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 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 #101249. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs where multiplexed Telegram profiles incorrectly share or cross-contaminate DM topic lanes, session state, and message routing. Related fixes also extend profile-aware routing to inline buttons and early auth flows across gateway and egress layers.
Open issues0
Open PRs0
Fixes on record
-
#101249 fix(telegram): multiplexed profiles keep separate DM topic lanes in the shared state.db (#76423 #87239, salvage #76487)
files:
contributors/emails/[redacted:email],gateway/platforms/base.py,gateway/run.py,gateway/slash_commands.py,hermes_state.py,plugins/platforms/telegram/adapter.py,tests/gateway/test_telegram_topic_profile_isolation_76423.py,tests/gateway/test_telegram_topic_profile_routing_76423.py,tests/test_hermes_state.py,website/docs/user-guide/messaging/telegram.md -
#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)
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
-
#87240 fix(multiplex): isolate Telegram profiles across egress, DM topics, and session listings · merged via another change →
bb7838c,11f932c,#101249,#76487,#101250
Closed issues · 1
- Closed#87239Multiplexed Telegram profiles share DM topic lanes: secondary-profile replies are addressed to another bot's thread and dropped
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.00means 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