Cairn
NousResearch/hermes-agent

Fix voice input labeling in CLI speech-to-text

Cluster 65827 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 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 issues and PRs address a bug where the CLI incorrectly marks typed messages as voice input, with fixes to restrict voice-related prefixes and behavior to messages that actually originate from speech-to-text.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: duplicate 1 · other 2

  • #11744 fix(cli): route voice reply behavior by input origin · duplicate → #65827
  • #65925 fix(cli): only mark speech-to-text messages as voice input · other → #11744
  • #65961 fix: only prefix voice-transcribed messages with [Voice input...] prefix (#65827) · other → #11744
Closed issues · 1
  • Closed#65827CLI voice mode marks typed messages as voice input
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
hermes cli
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/65827.json
cluster/65827.md