Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Provides a patch for Clawdbot fixing TTS auto-replies on inbound voice memos by disabling block streaming to ensure final payload reaches TTS pipeline.
Provides a patch for Clawdbot fixing TTS auto-replies on inbound voice memos by disabling block streaming to ensure final payload reaches TTS pipeline.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill provides a core patch for Moltbot that fixes voice memo TTS auto-replies. The issue occurs when block streaming prevents the final payload from reaching the TTS synthesis pipeline.
Core Patch / Documentation This is not a traditional plugin that extends functionality - it's a documentation package with patch files for core Clawdbot modifications.
Use this if you're experiencing: Voice memos not triggering TTS responses TTS working for text messages but not audio messages TTS auto mode = "inbound" not functioning
# 1. Locate your clawdbot installation CLAWDBOT_PATH=$(which clawdbot) CLAWDBOT_DIR=$(dirname $(dirname $CLAWDBOT_PATH)) # 2. Backup original files cp $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/auto-reply/reply/dispatch-from-config.js \ $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/auto-reply/reply/dispatch-from-config.js.backup cp $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/tts/tts.js \ $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/tts/tts.js.backup # 3. Apply patch cp patch/dispatch-from-config.js $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/auto-reply/reply/ cp patch/tts.js $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/tts/ # 4. Restart clawdbot clawdbot restart
If this patch gets accepted into core Clawdbot, you can simply update: npm install -g clawdbot@latest
No additional configuration needed beyond existing TTS settings. Ensure you have: { "messages": { "tts": { "auto": "inbound", // or "always" "provider": "openai", // or "elevenlabs" or "edge" "elevenlabs": { "apiKey": "your-key-here" } } } }
Configure TTS with auto: "inbound" Send a voice memo to your bot Check logs for debug output: [TTS-DEBUG] inboundAudio=true ttsAutoResolved=inbound ttsWillFire=true [TTS-APPLY] PASSED all checks, proceeding to textToSpeech [TTS-SPEECH] ... Verify bot responds with audio
The patch includes extensive debug logging. To view: # Logs will show in your clawdbot console clawdbot gateway start Look for: [TTS-DEBUG] - Shows TTS detection logic [TTS-APPLY] - Shows TTS payload processing decisions [TTS-SPEECH] - Shows TTS synthesis attempt
Important: Before deploying to production, consider: Remove debug logging - The console.log statements should be removed or made configurable Test thoroughly - Ensure voice memos work correctly Monitor performance - Disabling block streaming may impact streaming behavior To remove debug logging, edit the patched files and remove lines containing: console.log('[TTS-DEBUG]' console.log('[TTS-APPLY]' console.log('[TTS-SPEECH]'
If you need to revert the patch: # Restore backups CLAWDBOT_PATH=$(which clawdbot) CLAWDBOT_DIR=$(dirname $(dirname $CLAWDBOT_PATH)) cp $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/auto-reply/reply/dispatch-from-config.js.backup \ $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/auto-reply/reply/dispatch-from-config.js cp $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/tts/tts.js.backup \ $CLAWDBOT_DIR/lib/node_modules/clawdbot/dist/tts/tts.js clawdbot restart
Block streaming is used to send incremental text chunks to the user as they're generated. However, TTS synthesis hooks into the "final" payload type by default. When block streaming is enabled: Text chunks are sent as "block" payloads The final assembled text is sent as a "final" payload But block streaming optimization drops the final payload (text already sent) TTS never fires because it only processes "final" payloads
The patch adds detection logic to identify when TTS should fire: Inbound message has audio attachment (isInboundAudioContext()) TTS auto mode is "inbound" or "always" Valid TTS provider and API key configured When these conditions are met, block streaming is temporarily disabled for that specific reply, ensuring the final payload reaches the TTS pipeline.
dispatchReplyFromConfig() โโ isInboundAudioContext(ctx) โ detects audio โโ resolveSessionTtsAuto(ctx, cfg) โ gets TTS settings โโ ttsWillFire = conditions met? โโ getReplyFromConfig({ disableBlockStreaming: ttsWillFire }) โโ maybeApplyTtsToPayload() receives final payload โโ textToSpeech() synthesizes audio
Clawdbot: 1.0.0+ Node.js: 18+ Platforms: All platforms supported by Clawdbot
Debug logging is verbose (should be removed for production) Modifies compiled dist files (not source) May need to reapply after clawdbot updates
To improve this patch: Test with different TTS providers (OpenAI, ElevenLabs, Edge) Test with different auto modes ("always", "inbound", "tagged") Suggest optimizations to reduce debug logging overhead Propose integration into core Clawdbot source
If you encounter issues: Check logs for [TTS-DEBUG] output Verify TTS configuration is correct Ensure API keys are valid Check that block streaming was actually disabled (disableBlockStreaming: true in logs)
Same as Moltbot.
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.