NousResearch/hermes-agent

Voice message transcription fixes across integrations

Cluster 16185 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members address bugs where voice messages were not being automatically transcribed, covering Telegram, gateway agent runs, and a configuration-reading issue for local STT commands.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1

  • #16230 fix(stt): read local_command config from config.yaml, not just env var (#16185) · stale or abandoned → #17140
  • #60696 fix(telegram): voice messages not transcribed automatically (#16185) · done elsewhere → #16185
Closed issues · 1
  • Closed#16185Telegram voice messages not transcribed automatically
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

Subsystem
gateway
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.