NousResearch/hermes-agent

hermes update collapsing per-user gateways bug and fix

Cluster 109954. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

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

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

Read #110205 Pick up a Lab task

A bug in hermes update auto-migration incorrectly merges per-UNIX-user or per-scope gateways into a single multiplexer, collapsing privilege isolation. The accompanying fix adds a guard on automatic migration service boundaries and introduces a gateway.auto_multiplex_migration opt-out.

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.

#110205 hermes update no longer folds cross-user / cross-scope per-profile gateways into one multiplexer; gateway.auto_multiplex_migration opt-out (#109954, salvage #110043 #109562)

merged to main

files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], hermes_cli/AGENTS.md, hermes_cli/config_defaults.py, hermes_cli/gateway_migrate.py, hermes_cli/gateway_migrate_guards.py, tests/hermes_cli/test_gateway_migrate_multiplex.py, website/docs/user-guide/multi-profile-gateways.md

1 PR closed without merging

From the close comments: done elsewhere 1

#110043 fix(gateway): guard automatic migration service boundaries · done elsewhere → 0abfd11, 1065471, #110205, #109954

Closed issues · 1

Closed#109954[Bug]: `hermes update` auto-migration uninstalls per-UNIX-user secondary gateways, collapsing a privilege-isolated fleet into one process

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

Merged PRs: #110205
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 13 Sep 2026

For your agent

The same facts, typed.

cluster/109954.json
cluster/109954.md