Cairn
NousResearch/hermes-agent

Gateway restart behavior on non-systemd environments, plus broader regression fixes

Cluster 29603 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 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 0 PRs.

Two members concern gateway restart handling, one describing a restarted gateway instance being killed on non-systemd setups such as Termux/Android and another proposing a Python-watcher respawn approach. The third title mentions cron, CLI, doctor, and Termux regressions more broadly, so it overlaps only partly with the restart theme.

Open issues1

  • Issue#29603gateway restart kills new instance on non-systemd environments (Termux/Android)

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #29619 fix(gateway): respawn via Python watcher so /restart doesn't SIGHUP new gateway (#29603) · other
  • #36897 Fix cron, CLI, doctor, and Termux regressions · done elsewhere → b94397f, 6b21a93, #56168, #36815, #11336, #36867, #36771, #29603, #36287
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

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/29603.json
cluster/29603.md