NousResearch/hermes-agent

Desktop gateway routing and identity preservation fixes

Cluster 95628. Data as of

Nothing open on GitHub. Fix merged in #95692 on 26 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #95692. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #95692. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern bugs and fixes related to how the desktop client routes connections and RPCs across multiple gateways or backends, particularly around preserving the correct primary gateway identity and honoring the switcher-selected source.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #95692 fix(desktop): keep secondary-gateway publication from relabeling the primary socket (salvage #95396 + guard)

    merged to main

    files: apps/desktop/src/app/gateway/hooks/use-gateway-boot.test.tsx, apps/desktop/src/app/gateway/hooks/use-gateway-boot.ts, apps/desktop/src/store/gateway-connection-scope.test.ts, apps/desktop/src/store/gateway.ts

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #95396 fix(desktop): preserve primary gateway identity across source switches · merged via another change → 1a5547c, #95692, #95628, #94724
  • #95680 fix(desktop): fresh-chat RPCs route by the switcher-selected source, never the primary by default · done elsewhere → #95628, #95692
Closed issues · 1
  • Closed#95628Desktop multi-connection routing: new sessions silently default to a different backend than the one selected in the switcher
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.00 means 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

At a glance

Merged PRs
#95692
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
26 Aug 2026

For your agent

The same facts, typed.