Cairn
NousResearch/hermes-agent

Gateway HOME directory and lock path fallback issues

Cluster 35059 · environments. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

These issues and fixes concern the gateway service failing when HOME points to an unwritable or incorrect directory (e.g., /root for non-root users), with proposed fallbacks using HERMES_HOME or HERMES_REAL_HOME to locate lock state and SSH config files after s6 privilege drops.

Open issues0

No open issues.

Open PRs1

  • PR#56840fix: use HERMES_REAL_HOME for HOME in s6 startup scripts

4 PRs closed without merging

From the close comments: done elsewhere 2 · duplicate 2

  • #35069 fix(gateway): preserve HOME after s6 privilege drop (#35059) · done elsewhere → c341a2d, #34837
  • #56421 fix(gateway): fall back from unwritable lock state home · done elsewhere → c341a2d, #56402, #33481
  • #56455 fix(gateway): fallback lock dir when HOME is unwritable · duplicate → #56421, #56402
  • #56785 fix(gateway): fall back to HERMES_HOME for gateway-locks state dir (#56402) · duplicate → #56421, #56402
Closed issues · 2
  • Closed#35059non-default profile gateway fails: /root/.ssh/config not found
  • Closed#56402[Bug] gateway-locks PermissionError when HOME=/root and gateway runs as non-root UID (silently pauses Telegram)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: 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
environments
Closed issues
2
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/35059.json
cluster/35059.md