Cairn
NousResearch/hermes-agent

Dashboard status incorrectly identifies lifecycle commands as servers

Cluster 59626 · dashboard. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

The dashboard's --status flag can misidentify wrapper lifecycle commands (rather than actual running servers) as active processes. Two fixes address this by excluding lifecycle flags and commands from the PID scan and stale-dashboard matching logic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #59813 fix(cli): exclude lifecycle flags from stale-dashboard match (#59626) · done elsewhere
  • #59931 fix(dashboard): exclude lifecycle commands from --status PID scan (#59626) · duplicate → #59813, #37419, #59626
Closed issues · 1
  • Closed#59626dashboard --status can report wrapper lifecycle commands as running servers
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

Subsystem
dashboard
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/59626.json
cluster/59626.md