Bot Chat relay DM returns receipt instead of reply
Cluster 115316. Data as of
Nothing open on GitHub. Fix merged in #116838 on 20 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 #116838. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116838. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where a DM relayed into a Bot Chat open in Desktop returns a receipt to the sender rather than the target's actual reply. The relay logic does not wait on the owner's receipt the same way local DMs do, causing incorrect response routing.
Open issues0
Open PRs0
Fixes on record
-
#116838 fix(bot-mode): a DM or peer run into a Bot Chat open in Desktop is answered by that chat, on every transport (#114959, #115174, #115316, salvage #114962 #115175 #115318)
files:
gateway/platforms/api_server.py,gateway/platforms/api_server_runs.py,tests/gateway/test_peer_dm_into_open_bot_chat.py,tools/bot_live_delivery.py,tools/bot_mode_dm.py,tui_gateway/methods_bot_relay.py -
#116933 fix(bot-relay): a relayed DM into a Bot Chat open in Desktop returns the target's reply, not a receipt (#115316, salvage #115318)
files:
tests/tui_gateway/test_bot_relay_methods.py,tui_gateway/methods_bot_relay.py,website/docs/user-guide/bot-mode.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#115318 fix(bot-relay): a relayed DM into a Bot Chat open in Desktop returns the target's answer, not a receipt (#115316) · merged via another change →
#116933,#115316
Closed issues · 1
- Closed#115316A cross-machine DM into a Bot Chat open in Desktop returns a receipt sentence to the sender, never the target's reply — the relay does not wait on the owner's receipt the way local DMs do
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