Cairn
NousResearch/hermes-agent

Voice-channel note read from wrong Discord bot adapter

Cluster 139345 · gateway. Data as of

1 open item. Fix merged in #140186 on 17 Oct 2026. Check it covers your case.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #140186. 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
1 issue and 0 PRs.

These members concern the gateway reading the voice-channel note from the adapter that handled or will answer the turn, rather than from the primary adapter. One is a bug report about a multiplexed secondary Discord bot not receiving the note, and two are fix-oriented pull requests with similar titles.

Open issues1

  • Issue#139345[Bug]: Multiplexed secondary Discord bot never gets the voice-channel note (read from the primary adapter)

Open PRs0

No open pull requests.

Fixes on record

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

  • #140186 fix(gateway): multiplexed WhatsApp TIME-WAIT, Feishu comment scope, Discord voice, webhook cron profile (package 7, MSG-16, MSG-13, MSG-14, CRON-2)

    merged to main

    files: gateway/run_agent_cache.py, gateway/run_turn.py, gateway/run_turn_progress.py, gateway/run_voice.py, hermes_cli/main.py, hermes_cli/webhook.py, plugins/platforms/feishu/adapter.py, plugins/platforms/feishu/feishu_comment.py, plugins/platforms/whatsapp/bridge_ownership.py, tests/gateway/test_feishu_profile_scope_hops.py, tests/gateway/test_prompt_tail_freeze.py, tests/gateway/test_whatsapp_multiplex.py, tests/hermes_cli/test_webhook_cron_profile.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #139356 fix(gateway): read the voice-channel note from the adapter that answers the source · done elsewhere → 3c401c4, #140186
  • #139359 fix(gateway): read the voice-channel note from the bot that received the turn · superseded by another PR → #139356
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
#140186
Closed issues
0
Attempts
2 PRs closed without merging
Fix link checked
17 Oct 2026

For your agent

The same facts, typed.

cluster/139345.json
cluster/139345.md