Cairn
NousResearch/hermes-agent

Systemd gateway install and non-standard HERMES_HOME handling

Cluster 6729 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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.

The members appear to share one theme: the systemd gateway installation not honoring an explicitly set HERMES_HOME. One is a bug report, and the others are fix-oriented titles (two with identical titles) about honoring or preserving the target HERMES_HOME during install.

Open issues1

  • Issue#6729[Bug]: Systemd Gateway installation does not honor non-standard HERMES_HOME env variable

Open PRs1

  • PR#14450fix(gateway): preserve target HERMES_HOME for systemd install

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #6822 fix(gateway): honor explicit HERMES_HOME in systemd install · superseded by another PR → #6941
  • #6941 fix(gateway): honor explicit HERMES_HOME in systemd install · done elsewhere
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

Subsystem
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/6729.json
cluster/6729.md