Cairn
NousResearch/hermes-agent

Discord message metadata leaking into persisted content

Cluster 71304 · gateway. Data as of

Nothing open on GitHub. Fix merged in #114830. Check it covers your case.

The short answer

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

These issues and fixes address Discord triggering-message metadata and routing notes being incorrectly stored as user-authored content or transcript history. Multiple fix attempts target stripping or excluding this metadata before persistence.

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.

  • #114830 fix(gateway, desktop): Discord turns persist and display the user's text, not the triggering-message note (#114719, #71304, salvage #71309)

    merged to main

    files: apps/desktop/src/lib/chat-messages.test.ts, apps/desktop/src/lib/chat-messages/hydration.ts, gateway/run_inbound.py, gateway/run_turn.py, tests/gateway/test_discord_triggering_note_persistence.py, tests/tui_gateway/test_tui_gateway_server.py, tui_gateway/session_history.py, website/docs/developer-guide/gateway-session-lifecycle.md

3 PRs closed without merging

From the close comments: superseded by another PR 3

  • #71309 fix(gateway): strip Discord triggering-note before persisting user message (#71304) · superseded by another PR → 3569a13, #114830, #114719, #71304, #71309
  • #71357 fix(gateway): persist original user text, not augmented routing note, for Discord messages (#71304) · superseded by another PR → #71309, #71304
  • #71619 fix(discord): keep triggering IDs out of transcript history · superseded by another PR → 3569a13, #114830, #114719, #71304, #71309
Closed issues · 1
  • Closed#71304[Bug]: Discord triggering-message metadata is persisted as user-authored content
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.40: 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
#114830
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/71304.json
cluster/71304.md