NousResearch/hermes-agent

Bot Mode ghost-dialing fix for shared remote profiles

Cluster 96493. Data as of 2026-10-25 11:21 UTC

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

open issues

open PRs

items grouped

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

Next step: read #99377, then check it covers your case.

Read #99377 Pick up a Lab task

These items address a Desktop bug where Bot Mode group members stop dialing or go silent when named profiles reuse a primary WebSocket connection on shared or remote backends. The work focuses on preserving profile scope and ensuring member session creation in that configuration.

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.

#98169 fix(desktop): keep profile scope when reusing primary remote backend

merged to main

files: apps/desktop/electron/main.ts, apps/desktop/electron/registry-primary-profile-scope.test.ts
#99377 fix(desktop): Bot Mode group members stop ghost-dialing — named profiles reuse the primary WS on shared remotes (#96493, salvage #96537)

merged to main

files: apps/desktop/src/store/gateway-profile-request.test.ts, apps/desktop/src/store/gateway.ts, contributors/emails/[redacted:email]

1 PR closed without merging

From the close comments: merged via another change 1

#96537 fix(desktop): reuse primary WS for named profiles on attached shared remote (#96493) · merged via another change → 89c28cc, #99377, #98169, #96493

Closed issues · 1

Closed#96493[Bug]: Bot Mode group rooms silent when Desktop is remote (Windows → Tailscale gateway) — no member session.create

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: #98169, #99377
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 31 Aug 2026

For your agent

The same facts, typed.

cluster/96493.json
cluster/96493.md