NousResearch/hermes-agent

Voice rebind utterance posted to wrong channel

Cluster 130311. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #133471 on 6 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #133471, then check it covers your case.

Read #133471 Pick up a Lab task

These items concern a bug where a transcribed voice utterance that spans a /voice join rebind is sent to the original channel rather than the newly bound one. The group includes a bug report and related fix attempts addressing this routing issue.

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.

#133471 fix(discord): an utterance transcribed across a /voice join rebind is not posted to the new channel

merged to main

files: gateway/run_voice.py, plugins/platforms/discord/adapter.py, plugins/platforms/discord/adapter_voice_info.py, tests/gateway/test_discord_voice_stale_binding.py, tests/gateway/test_voice_command.py, website/docs/user-guide/features/voice-mode.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/features/voice-mode.md

1 PR closed without merging

From the close comments: merged via another change 1

#130312 fix(discord): an utterance transcribed across a /voice join rebind is not posted to the new channel (#130311) · merged via another change → #133471

Closed issues · 1

Closed#130311[Bug]: Discord voice utterance in transcription is answered in another text channel after a /voice join rebind

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.67: 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

Merged PRs: #133471
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 6 Oct 2026

For your agent

The same facts, typed.

cluster/130311.json
cluster/130311.md