Cairn
NousResearch/hermes-agent

Voice reply transcription during pending clarify prompts

Cluster 52998 · gateway. Data as of

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

These issues and fixes address a bug where voice message replies to pending clarify prompts were being handled as raw filenames rather than transcribed text. The work focuses on ensuring transcription occurs before clarify resolution and related routing logic.

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.

  • #73518 fix(gateway): transcribe voice replies before clarify resolution and busy steering

    merged to main

    files: contributors/emails/[redacted:email], gateway/platforms/base.py, gateway/run.py, tests/gateway/test_busy_session_ack.py, tests/gateway/test_platform_base.py, tests/gateway/test_telegram_voice_v0_regressions.py, tests/gateway/test_unknown_command.py

3 PRs closed without merging

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

  • #50925 fix(gateway): transcribe voice replies to a pending clarify prompt · other
  • #53020 fix(gateway): transcribe voice replies before resolving clarify prompts · merged via another change → ea80b55, ebe57ca, #73518
  • #56743 fix(gateway): transcribe voice messages during pending clarify · superseded by another PR → #56743, #50925, #53020
Closed issues · 1
  • Closed#52998Voice message replies to pending clarify are sent as filename, not transcript
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
#73518
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
28 Jul 2026

For your agent

The same facts, typed.

cluster/52998.json
cluster/52998.md