NousResearch/hermes-agent

Fix sudo system gateway service name regression

Cluster 108674. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #108885 on 12 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #108885. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #108885. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #108885, then check it covers your case.

Read #108885 Pick up a Lab task

These issues and pull requests address a regression where sudo hermes gateway start/stop --system incorrectly targeted a hashed service unit name instead of the installed hermes-gateway unit, causing 'Unit not found' errors. The work focuses on preserving or anchoring the correct system service identity when running under sudo.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#108885 fix(gateway): sudo --system commands target the installed hermes-gateway unit again (#108674, salvage #108681 + #108706)

merged to main

files: contributors/emails/[email protected], hermes_cli/gateway.py, hermes_cli/main.py, hermes_constants.py, tests/hermes_cli/test_gateway_service.py

2 PRs closed without merging

From the close comments: merged via another change 2

#108681 fix(gateway): preserve system service name under sudo · merged via another change → #108885, #105525, #108706
#108706 fix(gateway): anchor system service identity on the installed unit (#108674) · merged via another change → #108885, #108681

Closed issues · 1

Closed#108674[Bug]: sudo `hermes gateway start|stop --system` targets `hermes-gateway-<hash>.service` and fails with "Unit ... not found" (exit 5) — regression from the #105525 fix

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

Merged PRs: #108885
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 12 Sep 2026

For your agent

The same facts, typed.

cluster/108674.json
cluster/108674.md