openclaw - 💡(How to fix) Fix WebChat TTS reports success but produces no audible playback or downloadable audio (Telegram works) [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
openclaw/openclaw#57296Fetched 2026-04-08 01:51:25
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
cross-referenced ×1

Code Example

15:13:58+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found
15:15:04+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found
15:15:37+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found
15:15:41+00:00 info gateway/channels/telegram {"subsystem":"gateway/channels/telegram"} telegram sendMessage ok chat=609356996 message=276
15:16:57+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found
RAW_BUFFERClick to expand / collapse

WebChat TTS reports success but produces no audible playback or downloadable audio (Telegram works)

Problem

In WebChat, TTS tool calls return success ("Generated audio reply"), but no audio is heard and no media/file is surfaced to the user.

Environment

  • OpenClaw 2026.3.28 (updated from 2026.3.13)
  • macOS host (Core), WebChat Control UI (openclaw-control-ui)
  • messages.tts.provider = "openai"
  • Telegram channel enabled and healthy

Repro

  1. Open WebChat session.
  2. Trigger TTS for a short phrase (e.g. “Don’t worry. It’s all fine!”).
  3. Observe tool success message.
  4. Run openclaw logs --follow during the trigger.

Expected

WebChat should provide audible playback and/or downloadable audio media, with clear routing logs.

Actual

  • No audible playback in WebChat
  • No downloadable media/file path
  • No obvious TTS playback event in gateway logs for that trigger

Control test

Same TTS works on Telegram (audible result confirmed). Logs show Telegram send success (gateway/channels/telegram ... sendMessage ok ...).

Impact

TTS appears channel-specific: usable on Telegram, unreliable/opaque on WebChat.

Log snippet (exact excerpt from our run)

15:13:58+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found
15:15:04+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found
15:15:37+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found
15:15:41+00:00 info gateway/channels/telegram {"subsystem":"gateway/channels/telegram"} telegram sendMessage ok chat=609356996 message=276
15:16:57+00:00 info agents/model-providers {"subsystem":"agents/model-providers"} [xai-auth] bootstrap config fallback: no config-backed key found

extent analysis

Fix Plan

The fix involves modifying the TTS playback handling in the WebChat control UI to properly handle audio playback and downloadable media.

Step-by-Step Solution

  1. Update TTS Provider Configuration: Ensure the openai TTS provider is correctly configured to return audio data.
  2. Modify WebChat Control UI: Update the WebChat control UI to handle TTS audio playback and downloadable media.

// Example code snippet to handle TTS audio playback function handleTtsAudio(audioData) { const audio = new Audio(); audio.src = URL.createObjectURL(new Blob([audioData], { type: 'audio/mpeg' })); audio.play(); }

3. **Implement Downloadable Media**: Add functionality to provide a downloadable media/file path for the TTS audio.
   ```javascript
// Example code snippet to provide downloadable media
function provideDownloadableMedia(audioData, filename) {
  const link = document.createElement('a');
  link.href = URL.createObjectURL(new Blob([audioData], { type: 'audio/mpeg' }));
  link.download = filename;
  link.click();
}
  1. Verify TTS Playback Event: Ensure the TTS playback event is properly logged in the gateway logs.

Verification

To verify the fix, trigger the TTS tool in WebChat and check for:

  • Audible playback of the TTS audio
  • Presence of a downloadable media/file path
  • TTS playback event logged in the gateway logs

Extra Tips

  • Ensure the openai TTS provider is correctly configured and functioning as expected.
  • Test the TTS tool with different audio formats and providers to ensure compatibility.
  • Monitor the gateway logs for any errors or issues related to TTS playback.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix WebChat TTS reports success but produces no audible playback or downloadable audio (Telegram works) [1 participants]