Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: WhatsApp plugin: outbound messages echo back as inbound [2 comments, 3 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#53729•Fetched 2026-04-08 01:24:16
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
1
Author
jjmartinartesi-a11yjjmartinartesi-a11y
Participants
jjmartinartesi-a11yjjmartinartesi-a11ymcaxtrmcaxtrpidgeon777pidgeon777
Timeline (top)
commented ×2labeled ×2closed ×1locked ×1

• Qué pasa: cada mensaje que envías reaparece como si te lo hubiera enviado Ingrid (la IA). • Cuándo empezó: desde el primer día después de configurar • Gateway config: gateway.bind=lan • OpenClaw version: Versión: OpenClaw 2026.3.23-1

Root Cause

• Qué pasa: cada mensaje que envías reaparece como si te lo hubiera enviado Ingrid (la IA). • Cuándo empezó: desde el primer día después de configurar • Gateway config: gateway.bind=lan • OpenClaw version: Versión: OpenClaw 2026.3.23-1

Code Example

## Issue
Every message I send via WhatsApp is being echoed back as an inbound message, 
as if received from the AI assistant. This creates duplicate messages in the chat.

## Steps to Reproduce
1. Send a message via WhatsApp (through Ingrid)
2. Message appears to send normally
3. Moments later, the same message reappears as if received from the assistant

## Expected Behavior
Message sends. No echo. No duplicate.

## Actual Behavior
Message sends AND immediately reappears as inbound, doubling the chat.

## Environment
- OpenClaw version: OpenClaw 2026.3.23-1
- Gateway config: gateway.bind=lan
- WhatsApp account: Personal
- Channel: Telegram + WhatsApp
- Plugin: whatsapp

## Additional Context
- This started immediately after initial WhatsApp link
- Happened across multiple restarts/reconfigurations
- Deslink/relink didn't help
- Telegram (same config) works perfectly with no echo
- Suggests webhook/event handling issue in WhatsApp plugin
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

• Qué pasa: cada mensaje que envías reaparece como si te lo hubiera enviado Ingrid (la IA). • Cuándo empezó: desde el primer día después de configurar • Gateway config: gateway.bind=lan • OpenClaw version: Versión: OpenClaw 2026.3.23-1

Steps to reproduce

  1. Send a message via WhatsApp (through Ingrid)
  2. Message appears to send normally
  3. Moments later, the same message reappears as if received from the assistant

Expected behavior

Message sends. No echo. No duplicate.

Actual behavior

Message sends AND immediately reappears as inbound, doubling the chat.

OpenClaw version

Versión: OpenClaw 2026.3.23-1

Operating system

macOS 26.3.1 (25D2128)

Install method

No response

Model

Effective model under test: WhatsApp plugin event handler (not an AI model issue, but the plugin's webhook/message routing logic) Gateway model running: google/gemini-3.1-pro-preview

Provider / routing chain

Provider: WhatsApp (personal account, +5493543583601) Routing chain: OpenClaw agent → WhatsApp plugin → sends outbound, but message reappears as inbound immediately after

Additional provider/model setup details

  • This started immediately after initial WhatsApp link
  • Happened across multiple restarts/reconfigurations
  • Deslink/relink didn't help
  • Telegram (same config) works perfectly with no echo
  • Suggests webhook/event handling issue in WhatsApp plugin

Logs, screenshots, and evidence

## Issue
Every message I send via WhatsApp is being echoed back as an inbound message, 
as if received from the AI assistant. This creates duplicate messages in the chat.

## Steps to Reproduce
1. Send a message via WhatsApp (through Ingrid)
2. Message appears to send normally
3. Moments later, the same message reappears as if received from the assistant

## Expected Behavior
Message sends. No echo. No duplicate.

## Actual Behavior
Message sends AND immediately reappears as inbound, doubling the chat.

## Environment
- OpenClaw version: OpenClaw 2026.3.23-1
- Gateway config: gateway.bind=lan
- WhatsApp account: Personal
- Channel: Telegram + WhatsApp
- Plugin: whatsapp

## Additional Context
- This started immediately after initial WhatsApp link
- Happened across multiple restarts/reconfigurations
- Deslink/relink didn't help
- Telegram (same config) works perfectly with no echo
- Suggests webhook/event handling issue in WhatsApp plugin

Impact and severity

Impact: WhatsApp channel becomes unusable — every message duplicates, creating confusion and spam in conversations. Users must switch to alternative channels (Telegram works fine).

Severity: High — affects core messaging functionality of the WhatsApp integration. Blocks normal use of that provider.

Additional information

Working wrong since the installation.

extent analysis

Fix Plan

To resolve the issue of duplicated messages in WhatsApp, we need to adjust the webhook/event handling logic in the WhatsApp plugin.

Here are the steps:

  • Check the WhatsApp plugin configuration for any misconfigured webhooks or event handlers.
  • Ensure that the gateway.bind=lan configuration is correct and not causing any issues with the webhook callbacks.
  • Update the WhatsApp plugin to the latest version, if available, to ensure any known issues are fixed.
  • Modify the event handling logic in the WhatsApp plugin to prevent echoing back sent messages as inbound messages.

Example code snippet to prevent echoing:

def handle_outbound_message(message):
    # Send the message via WhatsApp
    send_message_via_whatsapp(message)
    
    # Prevent echoing back the sent message
    if message['direction'] == 'outbound':
        return None

def handle_inbound_message(message):
    # Process the inbound message
    process_inbound_message(message)

In the above example, the handle_outbound_message function sends the message via WhatsApp and then checks if the message is outbound. If it is, the function returns None to prevent the message from being echoed back as an inbound message.

Verification

To verify that the fix worked, follow these steps:

  • Send a message via WhatsApp using the updated plugin.
  • Check if the message is sent successfully and does not reappear as an inbound message.
  • Test the fix with multiple messages and restarts to ensure it is working consistently.

Extra Tips

  • Regularly update the WhatsApp plugin to ensure any known issues are fixed.
  • Monitor the plugin's configuration and event handling logic to prevent similar issues in the future.
  • Consider implementing a message deduplication mechanism to prevent duplicate messages in case of any issues with the plugin.

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…

FAQ

Expected behavior

Message sends. No echo. No duplicate.

#installation#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING