Gateway multiplexed bot session lane isolation fixes
Cluster 88404 · gateway. Data as of
Nothing open on GitHub. Fix merged in #89860. Check it covers your case.
The short answer
- Known?
- Yes. 5 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
resolved, deciding PR #89860. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where multiplexed bots incorrectly share a single session lane due to adapter-level session keys omitting the profile. Fixes involve carrying the profile in session keys and stamping it before busy/approval checks.
Open issues0
Open PRs0
Fixes on record
-
#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
3 PRs closed without merging
From the close comments: superseded by another PR 2 · merged via another change 1
-
#69156 fix(gateway): stamp profile before busy/approval checks in handle_message · superseded by another PR →
21260c3,#89860,#88437,#88404 -
#88437 fix(gateway): carry the profile in adapter-derived session keys · merged via another change →
#89860,#88404 - #89827 fix(gateway): multiplexed bots stop sharing one session lane (#88404, salvage #88437) · superseded by another PR
Closed issues · 1
- Closed#88404Multiplex: adapter-level session keys omit the profile, so all bots share one agent:main lane
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.70: 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
- Subsystem
- gateway
- Merged PRs
- #89860
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 19 Aug 2026