TUI gateway prompt-answer race and stall fixes
Cluster 112548 · gateway. Data as of
1 open item. Fix merged in #113820 on 17 Sep 2026. 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 #113820. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113820. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
A cluster of fixes addressing race conditions and stall scenarios in the TUI gateway, specifically around prompt/approval answer delivery, request settlement atomicity, and legacy client deadline handling.
Open issues0
Open PRs1
- PR#112563fix(gateway): prevent lost prompt answers and legacy client stalls
Fixes on record
-
#113227 fix(tui_gateway): prompt answers survive a racing cancel or a last-second deadline (#112548, salvage #112559)
files:
tests/tui_gateway/test_protocol.py,tui_gateway/server_requests.py,website/docs/developer-guide/programmatic-integration.md -
#113820 fix(tui_gateway): old app builds no longer stall the agent on clarify/approval (closes remaining atoms of #112548)
files:
apps/desktop/src/lib/json-rpc-gateway-heartbeat.test.ts,apps/shared/src/gateway-contract.generated.ts,apps/shared/src/gateway-contract.openrpc.json,apps/shared/src/json-rpc-channel.test.ts,apps/shared/src/json-rpc-channel.ts,tests/tools/test_approval_gateway_wait_late_choice.py,tests/tui_gateway/test_protocol.py,tools/approval.py,tools/approval_gateway_wait.py,tui_gateway/AGENTS.md,tui_gateway/contracts/liveness.py,tui_gateway/methods_voice.py,tui_gateway/server.py,tui_gateway/server_requests.py,tui_gateway/session_transports.py,ui-tui/src/__tests__/gatewayClient.test.ts,website/docs/developer-guide/programmatic-integration.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#112559 fix(tui_gateway): make server request settlement atomic · superseded by another PR →
#113227,#113820,#112548
Closed issues · 1
- Closed#112548Follow-up to #110677: resolve_response/cancel race, old-client full-deadline stall, and a doc misname
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.40: 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