Cairn
NousResearch/hermes-agent

Cron gateway liveness HERMES_HOME resolution fix

Cluster 109360. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These items address a bug where the cronjob tool's gateway liveness check incorrectly resolves HERMES_HOME, causing false 'gateway not running' warnings. The fix involves reading HERMES_HOME from the process environment when the tool context strips it.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #109366 fix(cron): resolve gateway liveness from request home · done elsewhere → b71c3cc, #109360
  • #110062 fix(cron): resolve HERMES_HOME from proc environ when tool context strips it (#109360) · done elsewhere → b71c3cc, #109360
Closed issues · 1
  • Closed#109360[Bug]: cronjob tool's gateway-liveness check resolves HERMES_HOME incorrectly, reports false "gateway not running" warning
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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/109360.json
cluster/109360.md