Dashboard process detection and lifecycle management fixes
NousResearch/hermes-agent · cluster 16872 · dashboard
Data as of
9 open items. Fix merged in #16895. Check it covers your case.
The short answer
- Known?
- Yes. 22 related items grouped here, 4 issues already closed.
- Fix event
- A fix was merged to main in PR #16895. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #16895. That is separate from the fix event. - Still open
- 3 issues and 6 PRs.
Next step: read #16895, then check whether your report is one of the 3 still open.
Read #16895Pick up a Lab taskThese issues and PRs address problems with detecting, stopping, and warning about dashboard processes across several scenarios: when global flags like --profile precede the subcommand, on Windows (including Session 0 and PowerShell fallback), and when stale processes remain after updates.
Open issues3
Open PRs6
- PR#37645fix(cli): fall back to PowerShell for dashboard --status/--stop on Windows (fixes #37593)
- PR#39197fix(dashboard): clean stale processes at dashboard startup (#39136)
- PR#41636fix(41598): Detect Windows Session 0 stale dashboard via port check
- PR#56723fix(update): detect profile dashboard processes in stale-dashboard sweep
- PR#56745[codex] Harden profile stale runtime sweep after update
- PR#61408fix: detect profiled dashboard process during update
Fixes on record
-
#16895 fix(cli): warn about stale dashboard processes after hermes update
files:
hermes_cli/main.py,tests/hermes_cli/test_update_stale_dashboard.py
8 PRs closed without merging
From the close comments: superseded by another PR 4 · closed without comment 2 · duplicate 1 · merged via another change 1
-
#16881 fix(cli): warn about stale dashboard processes after hermes update · merged via another change →
66b1142,#16895,#16872 -
#17149 test(update-autostash): include stdout in fake_run defaults so stale-dashboard scan doesn't crash · superseded by another PR →
#17642 -
#44048 fix(cli): detect dashboard PIDs when --profile precedes the subcommand · superseded by another PR →
#44165 -
#44165 fix(cli): tokenized dashboard cmdline matcher — detect global flags before the subcommand · superseded by another PR →
7bf1373,#121156 -
#44206 fix(cli): detect dashboard processes when --profile precedes subcommand (#44035) · superseded by another PR →
#44165,#44035
Show 3 more
- #44252 fix(cli): dashboard status/stop/update miss running dashboards when --profile precedes the subcommand · closed without comment
-
#44578 fix(dashboard): add PowerShell fallback for process detection on Windows 11 · duplicate →
#37645 - #60606 fix(cli): reap dashboard/serve backends launched with pre-subcommand flags on update · closed without comment
Closed issues · 4
- Closed#16872hermes update doesn't warn about stale dashboard processes (frontend/backend version mismatch)
- Closed#44035[Bug]: dashboard status/update miss running dashboards when --profile appears before the subcommand
- Closed#56717[Bug]: non-default profile can keep stale runtime after update, causing ImportError
- Closed#60540hermes update leaves dashboard/serve backends running old code when launched with pre-subcommand flags (--profile <name> dashboard)
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.08: 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
- Subsystem
- dashboard
- Merged PRs
- #16895
- Closed issues
- 4
- Attempts
- 8 PRs closed without merging
- Fix link checked
- 28 Apr 2026