NousResearch/hermes-agent

Multiplex pairing store routing fixes and improvements

Cluster 70858 · gateway. Data as of

Nothing open on GitHub. Fix merged in #74446 on 30 Jul 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 #74446. 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 address a bug where multiplex pairing codes are generated in the wrong (default) pairing store rather than the correct routed profile's store, preventing secondary-profile DMs from pairing. Related work adds profile-correct approval handling and a desktop surface for approvals.

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.

  • #74446 feat(pairing): profile-correct approvals, and a desktop surface to do them from

    merged to main

    files: apps/desktop/src/app/messaging/index.test.tsx, apps/desktop/src/app/messaging/index.tsx, apps/desktop/src/app/session/hooks/use-message-stream/gateway-event.ts, apps/desktop/src/hermes.ts, apps/desktop/src/i18n/en.ts, apps/desktop/src/i18n/types.ts, apps/desktop/src/i18n/zh.ts, apps/desktop/src/pairing-scope.test.ts, apps/desktop/src/store/live-sync.ts, apps/desktop/src/types/hermes.ts, gateway/pairing.py, gateway/run.py, hermes_cli/web_models.py, hermes_cli/web_server.py, hermes_constants.py, tests/gateway/test_multiplex_pairing_stores.py, tests/gateway/test_pairing.py, tests/gateway/test_unauthorized_dm_behavior.py, tests/hermes_cli/test_dashboard_admin_endpoints.py, tests/tui_gateway/test_change_watcher.py (+2 more)

1 PR closed without merging

From the close comments: merged via another change 1

  • #70932 fix(gateway): align multiplex pairing stores · merged via another change → #74446, #60564, #37758
Closed issues · 1
  • Closed#70858[Bug]: multiplex pairing code is generated in the default PairingStore, not the routed profile's — secondary-profile DMs can never pair
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
#74446
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
30 Jul 2026

For your agent

The same facts, typed.