Multiplexed secondary-profile messaging status stuck correction

NousResearch/hermes-agent · cluster 112765

Data as of 2026-10-23 11:54 UTC

Nothing open on GitHub. Fix merged in #113045. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #113045 Pick up a Lab task

A bug caused messaging pages and cards for multiplexed secondary-profile platforms to permanently show 'Restart needed' because the platform status key <profile>:<platform> was never correctly looked up past a stale own runtime record. These changes identify and correct that status-resolution logic.

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.

#113045 Messaging card for a multiplexed profile no longer stuck on 'Restart needed' past a stale own record (#112765, salvage #112784/#112790/#112786)

merged to main

files: hermes_cli/web_routers/messaging.py, tests/hermes_cli/test_served_profile_mirror_platforms.py

3 PRs closed without merging

From the close comments: merged via another change 3

#112784 fix(messaging): ignore a served profile's stale own runtime record · merged via another change → a09195b, #113045
#112786 fix(messaging): resolve secondary-profile platform status under multiplexing · merged via another change → a09195b, #113045
#112790 fix(desktop): resolve multiplexed secondary-profile platform state past a stale own record · merged via another change → a09195b, #113045

Closed issues · 1

Closed#112765Messaging page shows permanent "Restart needed" for multiplexed secondary-profile platforms (status key <profile>:<platform> never resolved)

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.40: 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: #113045
Closed issues: 1
Attempts: 3 PRs closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/112765.json
cluster/112765.md