Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Web UI: add a clear TTS toggle and default voice picker in Settings [1 comments, 2 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
openclaw/openclaw#71487•Fetched 2026-04-26 05:12:17
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
wen0531wen0531
Participants
steipetesteipetewen0531wen0531
Timeline (top)
commented ×1

Root Cause

TTS already exists and can be configured, but users reasonably expect an actual UI switch for a feature this visible. Right now the product feels like it has TTS "under the hood" rather than as a polished surfaced capability.

RAW_BUFFERClick to expand / collapse

Problem

Right now TTS is configurable, but the UX is much more command/config driven than it should be.

In practice, a user can enable TTS with commands like:

  • openclaw infer tts enable
  • openclaw infer tts disable
  • openclaw infer tts set-provider --provider microsoft

and preferences are written to ~/.openclaw/settings/tts.json.

That works technically, but from the Control UI / webchat perspective, there is no obvious visible "switch" for:

  • turning TTS on/off
  • seeing whether it is currently enabled
  • selecting a default provider
  • selecting a default voice

This creates a mismatch between capability and discoverability.

Request

Please add a first-class TTS section in the Control UI Settings (or another obvious UI surface) with:

  1. A visible TTS enable/disable toggle

    • reflect current state
    • persist to the same underlying preferences

  2. Default provider selector

    • show available/configured providers
    • indicate unavailable/unconfigured providers clearly

  3. Default voice selector

    • filter by selected provider
    • especially important for providers like Microsoft/Google/MiniMax with many voices

  4. Optional test/play button

    • generate a short sample line with the currently selected provider/voice
    • helps users verify the setup without using CLI commands

Why this matters

TTS already exists and can be configured, but users reasonably expect an actual UI switch for a feature this visible. Right now the product feels like it has TTS "under the hood" rather than as a polished surfaced capability.

Concrete example

A user wanted to:

  • enable TTS
  • set default voice to zh-CN-XiaoxiaoNeural

This ended up being done through CLI/config instead of a simple Settings toggle + voice dropdown.

Suggested UX copy

  • Text-to-Speech
  • Toggle: "Read replies aloud when supported"
  • Provider: dropdown
  • Voice: dropdown
  • Test button: "Play sample"

Thanks — this feels like a pretty high-leverage polish fix.

extent analysis

TL;DR

Add a TTS section to the Control UI Settings with a toggle, provider selector, voice selector, and optional test button to improve discoverability and user experience.

Guidance

  • Create a new section in the Control UI Settings dedicated to TTS configuration, including a visible toggle for enabling/disabling TTS.
  • Implement a provider selector that shows available/configured providers and indicates unavailable/unconfigured ones.
  • Develop a voice selector that filters by the selected provider, allowing users to choose from available voices.
  • Consider adding an optional test/play button to generate a short sample line with the currently selected provider and voice.

Example

No code snippet is provided as the issue focuses on UX improvements rather than specific code changes.

Notes

The solution requires updates to the Control UI Settings and may involve modifications to the underlying preferences storage and retrieval mechanisms.

Recommendation

Apply a workaround by adding the requested TTS section to the Control UI Settings, as this will improve the user experience and provide a more polished surfaced capability for TTS configuration.

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…
#prompt issue#agent setup#task chaining#parallel task#integration issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING