openclaw - 💡(How to fix) Fix Duplicate audio messages when sending MEDIA: with audio files to Telegram [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#70265Fetched 2026-04-23 07:26:59
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Participants
Timeline (top)
closed ×1commented ×1unsubscribed ×1
RAW_BUFFERClick to expand / collapse

Bug description: When using "MEDIA:/path/to/audio.ogg" or "MEDIA:/path/to/audio.mp3" to send audio files to Telegram, the recipient receives TWO audio messages instead of one:

  1. One as a regular audio file attachment
  2. One as a Telegram voice message

Expected behavior: Only ONE audio message should be sent (either as file OR as voice message, not both).

Actual behavior: Two separate audio messages are delivered.

Steps to reproduce:

  1. Generate an audio file (e.g., via OpenAI TTS)
  2. Send it using "MEDIA:/path/to/file.ogg" or "MEDIA:/path/to/file.mp3"
  3. Check Telegram — two messages arrive

Environment:

  • OpenClaw version: 2026.4.21
  • Channel: Telegram
  • Audio format tested: .ogg (opus), .mp3

Additional context: The issue seems to affect all audio formats. Both MEDIA: directive and possibly [[audio_as_voice]] tag may trigger this behavior.

extent analysis

TL;DR

The most likely fix involves modifying the handling of the MEDIA: directive or the [[audio_as_voice]] tag to prevent sending audio files as both regular attachments and voice messages.

Guidance

  • Investigate the MEDIA: directive implementation to ensure it doesn't automatically convert audio files to voice messages when sending to Telegram.
  • Check the [[audio_as_voice]] tag's behavior and consider disabling or modifying it to prevent dual message sending.
  • Verify if the issue persists when using different audio formats or channels to isolate the problem.
  • Review the OpenClaw version's documentation for any known issues or updates related to audio message handling.

Example

No specific code snippet can be provided without more context about the implementation, but checking the logic around MEDIA: and [[audio_as_voice]] in the codebase is crucial.

Notes

The solution may involve updating the OpenClaw version if a fix for this specific issue is available in a newer version, but this is not explicitly stated in the provided information.

Recommendation

Apply a workaround by modifying the MEDIA: directive or the [[audio_as_voice]] tag to prevent dual message sending, as upgrading to a potentially fixed version is not confirmed as an option based on the given information.

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 Duplicate audio messages when sending MEDIA: with audio files to Telegram [1 comments, 2 participants]