Nothing open on GitHub. Fix merged in #114947 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 #114947. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114947. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address how a one-shot roster clear experiencing errors is handled: whether it is retried or incorrectly marked as spent, which affects whether departed machines' agents remain unresolvable or stay looked up indefinitely.
Open issues0
Open PRs0
Fixes on record
-
#114947 fix(desktop): a failed bot-relay roster clear is retried instead of spent (#113862, salvage #113863)
files:
apps/desktop/src/plugins/hermes-bots/relay.test.ts,apps/desktop/src/plugins/hermes-bots/relay.ts
1 PR closed without merging
From the close comments: merged via another change 1
-
#113863 fix(bot-relay): a failed roster clear is retried, not spent · merged via another change →
2cf2412,#114947,#113862,#113863
Closed issues · 1
- Closed#113862A failed one-shot roster clear is marked spent, so a departed machine's agents stay resolvable forever
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
- #114947
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026