Cairn
NousResearch/hermes-agent

Gateway service detection and PID classification fixes

Cluster 16264 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items relate to incorrect detection of whether the gateway is running as a managed system service, including fixes for PID classification and systemd service status checks when the .service file is not at the expected path.

Open issues1

  • Issue#16264✓ Gateway is running (PID: 1896, 1893, 8140) (Running manually, not as a system service) To install as a service: hermes gateway install sudo hermes gateway install --system falsely reports 'Running manually' when gateway is actually a systemd user service

Open PRs1

  • PR#16349fix(gateway): classify service-managed status pids

1 PR closed without merging

From the close comments: other 1

  • #99200 fix(gateway): detect active systemd service even when .service file not at expected profile path · other → #26731, #20254
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/16264.json
cluster/16264.md