Secondary bot callback auth scope fix in multiplex
Cluster 120639. Data as of
Nothing open on GitHub. Fix merged in #122550 on 26 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 #122550. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #122550. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where inline/button callback authorization for secondary-profile bots was evaluated outside their own profile secret scope, causing allowlisted users to be incorrectly refused. The cluster covers the bug report and related fix attempts targeting this scoping issue.
Open issues0
Open PRs0
Fixes on record
-
#122550 fix(gateway): secondary-profile bots authorize button taps against their own allowlist (#120639, salvage #120642)
files:
gateway/run_adapters.py,tests/gateway/test_multiplex_interactive_auth.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1
Closed issues · 1
- Closed#120639[Bug]: Telegram inline callbacks refuse allowlisted user when a secondary profile owns its own bot under multiplex (callback auth runs outside profile secret scope)
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 LabAt a glance
- Merged PRs
- #122550
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 26 Sep 2026