openclaw - 💡(How to fix) Fix [Feature Request] TTS voice and text sent as separate messages [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#77850Fetched 2026-05-06 06:20:17
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
2
Author
Timeline (top)
mentioned ×2subscribed ×2closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

When messages.tts.auto: always is enabled, the TTS-generated audio and text reply are sent as one single message — the voice-note appears as a narrow strip above the text caption. This creates a poor UX on Telegram and other channels.

Expected behavior: Voice and text should be sent as two separate messages:

  1. First: pure voice message (voice-note, no caption)
  2. Second: plain text reply

This matches human conversation patterns — voice says it once, text provides follow-up.

Reference:

  • Hermes (another AI assistant) has implemented this: first sends voice message, then text message — two separate bubbles, each properly sized

Environment:

  • OpenClaw version: 2026.4.27
  • Platform: Telegram
  • TTS Provider: Microsoft (Edge TTS)

extent analysis

TL;DR

Modify the message sending logic to separate TTS-generated audio and text replies into two distinct messages when messages.tts.auto: always is enabled.

Guidance

  • Investigate the current implementation of messages.tts.auto: always to understand how it combines voice and text into a single message.
  • Consider introducing a conditional check to split the message into two parts: one for the voice-note and another for the text caption, when this setting is enabled.
  • Review the reference implementation in Hermes to gather insights on how they achieve the desired behavior of sending voice and text as separate messages.
  • Verify the fix by testing the modified logic on Telegram and other supported channels to ensure the voice-note and text reply are sent as two separate messages.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The solution may require adjustments based on the specific requirements of other channels beyond Telegram, as the issue primarily focuses on the Telegram platform.

Recommendation

Apply workaround: Modify the message sending logic to separate TTS-generated audio and text replies, as this approach directly addresses the reported issue and aligns with the expected behavior described.

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 [Feature Request] TTS voice and text sent as separate messages [1 comments, 2 participants]