Cairn
NousResearch/hermes-agent

Gateway status detection bugs and environment fixes

Cluster 4776 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 3 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
Nothing open on GitHub.

These issues and PRs address cases where the gateway is incorrectly reported as stopped or not running due to missing D-Bus environment variables, SSH sessions, Docker/Kubernetes PID 1 contexts, or permission-limited processes. The work involves improving gateway status detection across various runtime environments and CLI surfaces.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

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

  • #4792 fix(status): detect gateway process when running as PID 1 in Docker/Kubernetes · superseded by another PR → #4776
  • #5133 fix(status): #5130 add pid fallback check for ssh sessions without d-bus · done elsewhere
  • #10894 Use gateway systemctl helper in status command · other
  • #10902 fix(status): bootstrap user systemd env for gateway checks · duplicate → #10894
Closed issues · 3
  • Closed#4776[Bug]: hermes status reports Gateway as 'stopped' when running as PID 1 in Docker/Kubernetes
  • Closed#5130[Bug]: hermes status reports gateway as "stopped" when running via SSH without user D-Bus session
  • Closed#10851[Bug]: `hermes status` reports gateway as "stopped" when D-Bus env vars are missing
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.22: 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
3
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/4776.json
cluster/4776.md