Gateway messaging: chat input ordering and slash-command queueing
Cluster 140572 · gateway. Data as of
Nothing open on GitHub. Fix merged in #140973 on 18 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #140973. 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.
The three members relate to the gateway handling messaging chat input in order, including slash commands such as /queue, /steer, /plan, and skill commands that appear to run ahead of already-waiting messages. One member also mentions Bot Chat deliveries regardless of who created the chat; titles alone do not show outcomes.
Open issues0
Open PRs0
Fixes on record
-
#140973 fix(gateway): keep chat input in FIFO order and land Bot Chat deliveries whoever created the chat (package 10, lane 5)
files:
gateway/platforms/api_server.py,gateway/platforms/api_server_bot_chat.py,gateway/platforms/api_server_runs.py,gateway/platforms/base.py,gateway/platforms/webhook_ingress.py,gateway/run_busy.py,gateway/run_inbound.py,gateway/run_inbound_transcription.py,gateway/run_turn_prepare.py,gateway/session_authority.py,gateway/session_bot.py,gateway/session_controls.py,gateway/session_envelope.py,gateway/session_ingress.py,gateway/session_ingress_burst.py,gateway/session_ingress_media.py,gateway/session_local.py,gateway/session_local_migration.py,gateway/session_policy.py,gateway/session_policy_refresh.py(+24 more)
1 PR closed without merging
From the close comments: done elsewhere 1
-
#140573 fix(gateway): queue messaging slash-command turns behind the chat's waiting messages · done elsewhere →
#140973
Closed issues · 1
- Closed#140572Messaging: /queue, /steer, /plan and skill commands run ahead of messages already waiting in the chat
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.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
- #140973
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Oct 2026