iOS Talk Mode responses are duplicated to WhatsApp
Environment: OpenClaw 2026.3.2, iOS node paired via Tailscale Serve, WhatsApp channel enabled
What happens:
When using Talk Mode on iOS:
1. Speak → transcript sent via
2. Response streams back to iOS and plays via TTS
3. Same response is ALSO delivered to WhatsApp as a text message
The inbound metadata for iOS Talk Mode messages shows
Expected behavior:
- iOS Talk Mode responses should go back to the device only (TTS), not also to WhatsApp — same as macOS Talk Mode only writes to WebChat
- iOS messages should have a distinct channel identifier so the agent knows the origin
- Optionally, Talk Mode could use a node-scoped session instead of
Impact: Every Talk Mode conversation creates duplicate WhatsApp messages. No config workaround found.
What happens:
When using Talk Mode on iOS:
1. Speak → transcript sent via
chat.sendmain2. Response streams back to iOS and plays via TTS
3. Same response is ALSO delivered to WhatsApp as a text message
The inbound metadata for iOS Talk Mode messages shows
channel: "whatsapp"provider: "whatsapp"Expected behavior:
- iOS Talk Mode responses should go back to the device only (TTS), not also to WhatsApp — same as macOS Talk Mode only writes to WebChat
- iOS messages should have a distinct channel identifier so the agent knows the origin
- Optionally, Talk Mode could use a node-scoped session instead of
mainImpact: Every Talk Mode conversation creates duplicate WhatsApp messages. No config workaround found.
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
Similar Threads
Was this page helpful?
