Cairn
NousResearch/hermes-agent

Gateway status shows wrong profile PIDs

Cluster 97360 · 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.

A bug where the gateway status command reports PIDs from other profiles instead of scoping results to the specified profile. The members include a bug report and associated fixes targeting this scoping behavior.

Open issues1

  • Issue#97360hermes -p <profile> gateway status reports other profiles PIDs and claims "running" when that profile has no gateway

Open PRs1

  • PR#19504fix(gateway): filter status PIDs by profile

1 PR closed without merging

From the close comments: done elsewhere 1

  • #97428 fix(gateway): scope systemd service PIDs to current profile in gateway status · done elsewhere → 82d7a13, 9f8557a, cc9ef82, #97360, #16375
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/97360.json
cluster/97360.md