Cairn
NousResearch/hermes-agent

Background process notification off-mode and internal event handling in gateway

Cluster 9290 · gateway. Data as of

Nothing open on GitHub. Fix merged in #85923 on 14 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #85923. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #85923. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items center on background_process_notifications=off still allowing synthetic watch-pattern SYSTEM messages into conversations, with related pull requests that address honoring that setting. Some members also mention broader changes such as hardening internal background events, redaction, watch_overflow, and a compression guard, but the titles alone don't show details of those.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #85923 fix(gateway,tools): salvage background-notification cluster — off-mode gate, redaction, watch_overflow, compression guard

    merged to main

    files: agent/context_compressor.py, contributors/emails/[redacted:email], contributors/emails/[email protected], contributors/emails/[redacted:email], gateway/run.py, tests/agent/test_context_compressor_zero_user_provenance.py, tests/gateway/test_background_process_notifications.py, tests/tools/test_process_registry.py, tests/tools/test_watch_patterns.py, tools/process_registry.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #9341 fix(gateway): honor background_process_notifications=off for watch reinjection · done elsewhere → #85923, #9290
  • #18099 fix(gateway): harden internal background events · other → #9290, #9341
Closed issues · 1
  • Closed#9290Bug: background_process_notifications=off still injects synthetic watch-pattern SYSTEM messages into conversations
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.50: 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
Merged PRs
#85923
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
14 Aug 2026

For your agent

The same facts, typed.

cluster/9290.json
cluster/9290.md