# NousResearch/hermes-agent · Dashboard status incorrectly identifies lifecycle commands as servers

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #59626: dashboard --status can report wrapper lifecycle commands as running servers

## Prior & competing PRs

- **#59813: fix(cli): exclude lifecycle flags from stale-dashboard match (#59626)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`
- **#59931: fix(dashboard): exclude lifecycle commands from --status PID scan (#59626)**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#59813`, `#37419`, `#59626`

## Fix status

- No merged fix on record.
- Subsystem: `dashboard`