Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Bug]: HTML/browser UI voice setup inserts code into chat input and freezes [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#19049•Fetched 2026-05-03 04:52:38
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
9jss7nwwbk-svg9jss7nwwbk-svg
Participants
9jss7nwwbk-svg9jss7nwwbk-svg
Timeline (top)
labeled ×4

Error Message

Voice setup failures should fail closed with a short visible error/recovery instruction, not corrupt the chat input state.

RAW_BUFFERClick to expand / collapse

Bug Description

A Windows 11 / WSL2 user reports that Hermes in the browser/HTML interface becomes unusable after a voice-related setup/fix flow. The user says voice appears off/normal after refreshing the HTML page, but when they ask Hermes in the HTML interface to fix/setup voice, Hermes eventually starts inserting a large command/code block into the chat input box itself. The input box continuously fills with code/text, the user cannot copy/paste or regain control of the chat input, and the page freezes/has to be refreshed. In one case the HTML UI became mostly blank with only a cursor.

Important: this is not simply voice being enabled. Refreshing the browser restores the interface, but repeating the voice-fix task causes the input-box self-insertion/loop again.

Steps to Reproduce

  1. Windows 11 laptop with Hermes installed in WSL2 Ubuntu.
  2. Use the Hermes browser/HTML interface / sidecar-style UI.
  3. Ask Hermes from the HTML UI to fix or set up voice.
  4. After it appears to finish or while it is generating setup instructions, a large command/code block is inserted into the chat input box rather than only appearing as assistant output.
  5. The input box keeps filling / becomes uncontrollable; user cannot copy the intended command; UI freezes until browser refresh.

Expected Behavior

Assistant-generated commands should render as assistant output only. They should never be auto-inserted into the user's chat input box unless the user explicitly pastes or accepts them.

Voice setup failures should fail closed with a short visible error/recovery instruction, not corrupt the chat input state.

Actual Behavior

The HTML chat input appears to receive/generated command text continuously, locking the user out of the input and freezing the UI.

Affected Component

Browser/HTML interface / browser sidecar / web UI input handling; possibly voice setup flow interaction with input textarea/state.

Environment

  • Windows 11
  • WSL2 Ubuntu
  • Hermes Agent v0.12.0 shown in local CLI
  • User is using local Hermes in the TLC project folder through WSL/PowerShell and also testing an HTML/browser Hermes interface.

Related issues/PRs that may be relevant

  • #4212 chat input box bug around input sizing/focus
  • #16803 CLI/input unresponsive state
  • #17573 / #17608 WSL2 voice/TTS routing issues
  • #4520 browser sidecar bridge and extension
  • #12438 gateway restart failures when unresponsive

Severity / UX impact

High for non-technical users: the UI appears to have “a mind of its own,” repeatedly corrupts the input box, and forces refresh/restart. This makes voice setup and browser UI unsafe to recommend for non-technical Windows users.

extent analysis

TL;DR

The issue can be mitigated by investigating and fixing the interaction between the voice setup flow and the HTML input handling in the browser interface.

Guidance

  • Review the related issues #4212, #16803, and #4520 to identify potential causes of the input box corruption and unresponsive state.
  • Investigate the voice setup flow in the HTML interface to determine why it's inserting command blocks into the chat input box instead of rendering them as assistant output.
  • Check the WSL2 Ubuntu environment and Hermes Agent v0.12.0 configuration to ensure that there are no compatibility issues or misconfigurations contributing to the problem.
  • Consider adding error handling and input validation to the voice setup flow to prevent it from corrupting the chat input state.

Example

No code snippet is provided due to the lack of specific technical details, but the fix may involve modifying the JavaScript code that handles the voice setup flow and input box interaction in the HTML interface.

Notes

The issue may be related to the WSL2 environment and Hermes Agent version, so testing with different environments and versions may be necessary to identify the root cause. Additionally, the fix may require changes to the browser sidecar bridge and extension, as mentioned in related issue #4520.

Recommendation

Apply a workaround by modifying the voice setup flow to prevent it from inserting command blocks into the chat input box, and investigate the root cause of the issue to develop a permanent fix. This approach allows for a temporary solution while still addressing the underlying problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#installation#tensor shape#autograd error#model save/load

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING