Nothing open on GitHub. Fix merged in #111428 on 15 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 #111428. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111428. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address a bug where removing a machine from Connections causes it to persist incorrectly in other gateways' relay rosters, and a related edge case where the relay clears remaining gateways' rosters when the peer count drops below two.
Open issues0
Open PRs0
Fixes on record
-
#111428 fix(desktop): a machine removed from Connections leaves every gateway's relay roster (#111262, salvage #111264)
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: done elsewhere 1
-
#111264 fix(desktop): the relay clears the remaining gateways' remote roster when the peer set drops below two · done elsewhere →
#111428
Closed issues · 1
- Closed#111262fix(desktop): a machine removed from Connections stays in every other gateway's relay roster
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
- #111428
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026