Cairn
NousResearch/hermes-agent

TTS provider SDK missing detection in CLI status

Cluster 90610 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items address a gap where selecting a TTS provider with a missing SDK fails silently and reports a healthy status. The work adds validation and visible flagging of missing TTS SDKs in the hermes status command.

Open issues1

  • Issue#90610TTS: selecting a provider whose SDK is missing fails silently; `hermes status` shows ✓ and auto-TTS degrades to text with no user-visible error

Open PRs1

  • PR#90620fix(cli): flag a configured TTS provider whose SDK is missing in status

1 PR closed without merging

From the close comments: duplicate 1

  • #90764 fix(cli): validate TTS SDK availability in hermes status · duplicate → #90620
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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/90610.json
cluster/90610.md