Gateway multi-tenant scoping and state accuracy fixes
Cluster 121352. Data as of
Nothing open on GitHub. Fix merged in #126163 on 28 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #126163. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #126163. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs where gateway served-profile guards and status reporting fail to correctly scope behavior to a specific Hermes home, causing incorrect rejections and misleading state when multiple tenants share one host.
Open issues0
Open PRs0
Fixes on record
-
#126163 Gateway status, update, dashboard and served-profile guard stop lying about multiplex/standalone state (#120991 #125390 #123088 #123869 #121352 #120871 #124553, salvage #120997 #125397 #123106 #121574 #122169 #124669)
files:
gateway/host_attach.py,gateway/host_topology.py,gateway/run.py,gateway/status.py,hermes_cli/cron.py,hermes_cli/dump.py,hermes_cli/gateway.py,hermes_cli/gateway_multiplex_mode.py,hermes_cli/gateway_profile_lifecycle.py,hermes_cli/web_routers/messaging.py,hermes_cli/web_routers/status.py,tests/gateway/test_host_attach_lifecycle.py,tests/gateway/test_host_gateway_lock_refusal.py,tests/gateway/test_host_topology.py,tests/hermes_cli/test_dump_gateway_status.py,tests/hermes_cli/test_gateway.py,tests/hermes_cli/test_gateway_multiplex_lifecycle.py,tests/hermes_cli/test_gateway_multiplex_mode.py,tests/hermes_cli/test_gateway_served_guard_ownership.py,tests/hermes_cli/test_served_profile_mirror_platforms.py(+2 more)
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#121352[gateway] Two Hermes homes on one host: CLI served-profile guard refuses the second tenant's own gateway (exit 78) without --force
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.00means 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 LabAt a glance
- Merged PRs
- #126163
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 28 Sep 2026