Cairn
NousResearch/hermes-agent

voice.client_direct enabling on invalid or unreadable config

Cluster 140123 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

One bug report describes voice.client_direct turning on for values like 0 and [], or when the config can't be read. Two pull requests propose falling back to relay in those invalid, unknown, or unreadable-config cases.

Open issues1

  • Issue#140123[Bug]: `voice.client_direct` turns on for `0`, `[]` and when the config can't be read

Open PRs2

  • PR#140124fix(voice): fall back to relay for invalid client-direct config
  • PR#140816fix(voice): fall back to relay when client_direct is unknown or the config can't be read
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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/140123.json
cluster/140123.md