NousResearch/hermes-agent

Background process notifications misread as user messages, stale reply anchors

Cluster 52694 · agent. Data as of

Nothing open on GitHub. Fix merged in #122958 on 27 Sep 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 #122958. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #122958. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members share one theme: synthetic background process notifications in the gateway may be treated as user messages and may reply to a stale trigger message (reported for Discord DMs). Several members propose changes such as marking these notifications internal (e.g., an [INTERNAL] marker) and no longer anchoring them to the old message.

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.

  • #122958 fix(gateway): mark synthetic process notifications internal and stop stale reply anchors

    merged to main

    files: gateway/run_notifications.py, tests/gateway/test_background_process_notifications.py

  • #123097 fix(gateway): stop anchoring synthetic process notifications to the stale trigger message

    merged to main

    files: gateway/run_notifications.py, tests/gateway/test_background_process_notifications.py

1 PR closed without merging

From the close comments: done elsewhere 1

  • #52701 fix(process): use [INTERNAL] marker for background process notifications (#52694) · done elsewhere → #52694
Closed issues · 1
  • Closed#52694[Bug]: Background process notifications can be misinterpreted as user messages and reply to stale Discord DM anchors
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
agent
Merged PRs
#122958, #123097
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
27 Sep 2026

For your agent

The same facts, typed.