NousResearch/hermes-agent

Discord voice replies losing message reference data

Cluster 68728 · gateway. Data as of

Nothing open on GitHub. Fix merged in #73517 on 28 Jul 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 #73517. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a bug where Discord voice replies do not preserve their message reference, breaking reply threading. The work involves identifying the issue and applying a fix to retain the message reference field.

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.

  • #73517 fix(discord): voice correctness — callback wiring, warm-up clip fix, threading, drain, configurable timeouts

    merged to main

    files: contributors/emails/[email protected], contributors/emails/[redacted:email], contributors/emails/[redacted:email], gateway/run.py, hermes_cli/config.py, plugins/platforms/discord/adapter.py, plugins/platforms/discord/ffmpeg_utils.py, plugins/platforms/discord/voice_mixer.py, tests/gateway/conftest.py, tests/gateway/test_discord_send.py, tests/gateway/test_discord_voice_mixer.py, tests/gateway/test_platform_reconnect.py, tests/gateway/test_stt_config.py, tests/gateway/test_voice_command.py, website/docs/user-guide/messaging/discord.md

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

  • #68733 fix(discord): preserve voice reply threading · merged via another change → b8c38a4, #73517
  • #68778 fix(discord): preserve message_reference on voice replies (#68728) · other → #68728
Closed issues · 1
  • Closed#68728[Bug]: Discord voice replies drop their message reference
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
#73517
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
28 Jul 2026

For your agent

The same facts, typed.