Cairn

Gateway shutdown notification spam controls and options

NousResearch/hermes-agent · cluster 20103 · gateway

Data as of

5 open items. Fix attempted, not merged.

The short answer

2open issues
3open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 3 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
2 issues and 3 PRs.

These issues and PRs concern excessive or unwanted gateway shutdown/restart notifications flooding channels, with requests and fixes for suppressing, scoping, or customizing those notices under various conditions such as idle state, planned restarts, or rapid restart loops.

Open issues2

  • Issue#32008gateway: shutdown notices spam chats on reboot; duplicate LaunchAgent can cause --replace flap
  • Issue#60438[Bug]: Gateway restart loop can spam home channel with thousands of shutdown notifications

Open PRs3

  • PR#20943fix(gateway): scope restart interruption notices to active chats
  • PR#57164fix(gateway): skip home-channel shutdown broadcast when idle
  • PR#60529fix(gateway): suppress lifecycle pings during restart loops

2 PRs closed without merging

From the close comments: stale or abandoned 1 · superseded by another PR 1

  • #32154 fix(gateway): suppress shutdown notice on planned --replace takeover (#32008) · stale or abandoned
  • #33910 feat: add gateway.shutdown_notify config option to suppress restart notifications · superseded by another PR → #26005
Closed issues · 3
  • Closed#20103Feature Request: Add config option to suppress shutdown notifications when no active sessions exist
  • Closed#21871Feature request: config option to suppress gateway shutdown/restart notifications
  • Closed#29846Feature request: option to disable/customize gateway shutdown notification
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.16: 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
3
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/20103.json
cluster/20103.md