NousResearch/hermes-agent

Dashboard lifecycle verbs routed to wrong profile

Cluster 119886. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #120143 on 23 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 #120143. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #120143. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #120143 Pick up a Lab task

A bug caused lifecycle actions (restart, stop, etc.) triggered from the dashboard or CLI to act on the sticky or served profile instead of the multiplexer. The members address identifying and fixing this misrouting.

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.

#120143 fix: dashboard, tui-gateway and CLI lifecycle verbs act on the right profile (multiplexer, not the sticky/served one)

merged to main

files: hermes_cli/sessions_repair_profiles.py, hermes_cli/update_cmd_fleet.py, hermes_cli/update_cmd_fleet_checkout.py, hermes_cli/web_server_gateway.py, hermes_state_profile_repair.py, tests/hermes_cli/test_gateway_multiplex_served_record.py, tests/hermes_cli/test_sessions_repair_profiles.py, tests/hermes_cli/test_update_fleet_restart_pending.py, tests/tui_gateway/test_fast_session_scope.py, tests/tui_gateway/test_tui_gateway_server.py, tui_gateway/methods_config_set.py

1 PR closed without merging

From the close comments: merged via another change 1

#119887 fix(dashboard): a served profile's lifecycle verbs reach the multiplexer (not the sticky profile, not a phantom own gateway) · merged via another change → b9616fe, #120143

Closed issues · 1

Closed#119886Dashboard: restarting a served profile from a default-home dashboard restarts the sticky active_profile, not the multiplexer

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: #120143
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 23 Sep 2026

For your agent

The same facts, typed.

cluster/119886.json
cluster/119886.md