Cairn
NousResearch/hermes-agent

Show crash cause in gateway back-online notifications

Cluster 41360 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items concern adding crash-cause diagnostics to the gateway's 'back online' notification, so users can see why an agent died rather than only that it restarted. The group spans a feature request and an implementation across potentially multiple platforms.

Open issues1

  • Issue#41763[Feature]: Crash-cause diagnostics — parse why the agent died, not just that it restarted

Open PRs2

  • PR#42528Crash-cause diagnostics on the gateway "back online" notification
  • PR#44275feat(gateway): show crash cause in the back-online notification after an unclean restart
Closed issues · 1
  • Closed#41360[Feature]: Cross-platform crash-cause diagnostics — parse *why* the agent died, not just that it restarted
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.39: 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
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/41360.json
cluster/41360.md