Clarify prompt delivery and timeout handling fixes
Cluster 112684. Data as of
Nothing open on GitHub. Fix merged in #113825 on 17 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 #113825. 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 issues and fixes address bugs in how clarify prompts are delivered, timed out, and retried on messaging platforms, particularly around multi-question flows, unrenderable cards, and delivery uncertainty on Telegram.
Open issues0
Open PRs0
Fixes on record
-
#113202 fix(gateway): a multi-question clarify on messaging platforms stops at the first unanswered question instead of waiting one timeout per question (#112684, salvage #112725)
files:
gateway/run_turn_runner.py,tests/gateway/test_clarify_card_retire_on_timeout.py,tools/clarify_tool.py,website/docs/reference/tools-reference.md -
#113825 fix(gateway): a clarify card that cannot render is re-asked as plain text and never reported as user inactivity (closes remaining atoms of #112684)
files:
gateway/run.py,gateway/run_turn_runner.py,gateway/run_turn_runner_clarify_delivery.py,tests/gateway/test_clarify_delivery_fallback.py,tests/gateway/test_clarify_send_timeout_ambiguity.py,tests/gateway/test_prompt_decline_no_fallback.py,website/docs/reference/tools-reference.md,website/docs/user-guide/messaging/telegram.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#112701 fix(gateway): surface clarify delivery-uncertainty instead of waiting out the timeout · superseded by another PR →
9790d73,b3aef45,#112684,#113825,#113202
Closed issues · 1
- Closed#112684[Bug]: Telegram clarify prompt is not delivered before the tool timeout
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