Telegram voice/STT bug on OpenClaw 2026.3.2
Hey team — I think I hit a Telegram voice/STT bug on OpenClaw 2026.3.2.
Setup
macOS 26.3 arm64, Node 25.7.0
Telegram bot DM works (text works)
tools.media.audio.enabled = true
skills.entries.openai-whisper-api.apiKey set
Gateway healthy (openclaw gateway status OK)
Issue
When I send a Telegram voice note:
raw Telegram update includes voice payload,
agent run starts + completes,
bot replies,
but no STT/transcription step happens (no transcript available).
Debug snippet shows:
telegram/raw-update ... "voice": {...}
embedded run start
embedded run end
telegram sendMessage ok
(no audio/transcript logs in between)
Is this a known regression or am I missing a new config flag in 2026.3.2?
Note: This description was written for me by my OpenClaw.
Setup
macOS 26.3 arm64, Node 25.7.0
Telegram bot DM works (text works)
tools.media.audio.enabled = true
skills.entries.openai-whisper-api.apiKey set
Gateway healthy (openclaw gateway status OK)
Issue
When I send a Telegram voice note:
raw Telegram update includes voice payload,
agent run starts + completes,
bot replies,
but no STT/transcription step happens (no transcript available).
Debug snippet shows:
telegram/raw-update ... "voice": {...}
embedded run start
embedded run end
telegram sendMessage ok
(no audio/transcript logs in between)
Is this a known regression or am I missing a new config flag in 2026.3.2?
Note: This description was written for me by my OpenClaw.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
