Abandoned turn harvesting and marker handling fixes
Cluster 115431. Data as of
Nothing open on GitHub. Fix merged in #117011 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 #117011. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116943. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address how in-flight turns (room and group chat) are handled when a Desktop client abandons them mid-flight, focusing on ensuring stranded turns are harvested at appropriate boundaries and that session markers are written correctly rather than lost.
Open issues0
Open PRs0
Fixes on record
-
#116943 fix(desktop): group member turns are harvested when abandoned, keep working past 20 min, and name why they failed (#115431, #100274, #116458, salvage #115437 #116468 #116598)
files:
apps/desktop/src/plugins/hermes-bots/group-activity.test.ts,apps/desktop/src/plugins/hermes-bots/group-activity.ts,apps/desktop/src/plugins/hermes-bots/group-round-members.ts,apps/desktop/src/plugins/hermes-bots/group-rounds.ts,apps/desktop/src/plugins/hermes-bots/group-turns.test.ts,apps/desktop/src/plugins/hermes-bots/group-turns.ts,apps/desktop/src/plugins/hermes-bots/types.ts,website/docs/user-guide/bot-mode.md -
#117011 fix(desktop): a Group Chat turn the Desktop abandons mid-flight is harvested at the next boundary, not lost (#115431, salvage #115437)
files:
apps/desktop/src/plugins/hermes-bots/group-turns.test.ts
1 PR closed without merging
From the close comments: merged via another change 1
-
#115437 fix(desktop): a room turn a Desktop abandons mid-flight is harvested, not lost — the marker goes down at submit (#115431) · merged via another change →
ead1a80,#117011,#115431,#115437
Closed issues · 1
- Closed#115431Group chat: a remote member's turn that outlives the Desktop finishes on its gateway but its reply is lost, and the next send re-drives the still-running session — the stranded marker is written only on 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