Cairn
NousResearch/hermes-agent

Gateway process detection matching 'hermes-gateway' in arguments too broadly

Cluster 140089 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

One issue reports that any process with 'hermes-gateway' as an argument is treated as a gateway, which the update flow then drains and kills. Two related pull requests propose narrowing gateway argv matching so an entrypoint name in argument position is not treated as a gateway.

Open issues1

  • Issue#140089[Bug]: any process with an argument 'hermes-gateway' is treated as a gateway; hermes update drains and kills it

Open PRs2

  • PR#140093fix(gateway): restrict dedicated gateway argv matching
  • PR#140108fix(gateway): an entrypoint name in argument position is not a gateway
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
gateway
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/140089.json
cluster/140089.md