Cairn
NousResearch/hermes-agent

Secondary profile voice state sync on initial connect

Cluster 84872 · gateway. Data as of

Nothing open on GitHub. Fix merged in #101248 on 2 Sep 2026. Check it covers your case.

The short answer

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

These items concern a bug where secondary-profile adapters fail to sync voice state when first connecting, causing voice-to-voice replies not to fire. A fix addressing this and related gateway startup and session-recovery issues is proposed.

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.

  • #101248 fix(gateway): per-profile /voice state, off-loop startup hydration, session-recovery owner fence, int route ids (#84872 #74285 #88381 #86470, salvage #99519 #70815 #85245)

    merged to main

    files: contributors/emails/[redacted:email], gateway/profile_routing.py, gateway/run.py, gateway/session.py, gateway/slash_commands.py, hermes_cli/platform_actions.py, hermes_state.py, tests/gateway/test_multiplex_adapter_registry.py, tests/gateway/test_multiplex_phase0.py, tests/gateway/test_profile_routing.py, tests/gateway/test_voice_mode_platform_isolation.py, tests/hermes_cli/test_platform_actions.py, tests/test_hermes_state.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #84873 fix(gateway): sync /voice state on secondary profile initial connect · superseded by another PR → #89866, #89867
Closed issues · 1
  • Closed#84872Multiplex secondary-profile adapters never sync /voice state at initial connect — voice replies to voice input never fire
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.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

Subsystem
gateway
Merged PRs
#101248
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.

cluster/84872.json
cluster/84872.md