Gateway multiplexing clarify/session routing fixes
Cluster 83345 · gateway. Data as of
Nothing open on GitHub. Fix merged in #89860 on 19 Aug 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 #89860. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs where clarify replies and session lanes were incorrectly shared or misrouted across profiles under gateway multiplexing. Fixes involve profile-namespaced session key matching and proper routing of clarify replies by profile.
Open issues0
Open PRs0
Fixes on record
-
#82980 fix(gateway): match the profile-namespaced session key in the clarify bypass lookup
files:
gateway/platforms/base.py,tests/gateway/test_clarify_active_session_bypass.py -
#89860 fix(gateway): multiplexed bots stop sharing one session lane (#88404, salvage #88437)
files:
contributors/emails/[redacted:email],gateway/platforms/base.py,gateway/run.py,plugins/platforms/discord/adapter.py,plugins/platforms/feishu/adapter.py,plugins/platforms/matrix/adapter.py,plugins/platforms/raft/adapter.py,plugins/platforms/slack/adapter.py,plugins/platforms/telegram/adapter.py,plugins/platforms/wecom/adapter.py,plugins/platforms/whatsapp/adapter.py,tests/gateway/test_multiplex_adapter_session_key_namespace.py,tests/gateway/test_multiplex_busy_input_mode.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#83346 fix(gateway): route multiplex clarify replies by profile · done elsewhere →
dbb6acd,525ca9c,21260c3,#82980,#89860,#83345
Closed issues · 1
- Closed#83345[Bug]: clarify replies interrupt secondary profiles under gateway multiplexing
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