Fix /stop command not halting bot-triggered runs
Cluster 113846. Data as of
Nothing open on GitHub. Fix merged in #114721 on 18 Sep 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 #114721. 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 items address a bug where the /stop command acknowledges but fails to actually interrupt group runs that were dispatched by a bot. The fixes focus on gateway logic to ensure /stop reaches and halts such runs even when chat or session keys don't match exactly.
Open issues0
Open PRs0
Fixes on record
-
#114721 fix(gateway): /stop stops a run in the same chat even when its key misses (#113738, salvage)
files:
gateway/run_busy.py,gateway/slash_commands.py,tests/gateway/test_stop_chat_scope.py,website/docs/user-guide/features/hooks.md,website/docs/user-guide/sessions.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#113853 fix(gateway): let human /stop reach bot-triggered group runs · superseded by another PR →
#114721,#113846
Closed issues · 1
- Closed#113846[Bug][Feishu] /stop acknowledges but does not interrupt a bot-dispatched runaway group session
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
- Merged PRs
- #114721
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026