# NousResearch/hermes-agent · Cron gateway liveness HERMES_HOME resolution fix

## Open now

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

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #109360: \[Bug\]: cronjob tool's gateway-liveness check resolves HERMES_HOME incorrectly, reports false "gateway not running" warning

## Prior & competing PRs

- **#109366: fix(cron): resolve gateway liveness from request home**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `b71c3cc13c7d`, `#109360`
- **#110062: fix(cron): resolve HERMES_HOME from proc environ when tool context strips it (#109360)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `b71c3cc13c7d`, `#109360`

## Fix status

- No merged fix on record.