#WhatsApp

1 messages · Page 1 of 1 (latest)

quasi frost
halcyon wasp
#

NICE!

dim prairie
#

no maintainer here?

tough socket
#

Anyone having problem with whatsapp qr pairing?

atomic gyro
# quasi frost https://docs.openclaw.ai/channels/whatsapp

I have 2 fixes I've been applying on top of the release tag for the past week that fix the WhatsApp pairing issues I was seeing:

https://github.com/openclaw/openclaw/pulls/asyncjason

I created the PRs first, and then realized I should have created issues too, so they both have associated issues now.

These are tested and fix the WhatsApp pairing.

This link shows the process working (note 3rd party UI, using OpenClaw under the hood)
https://streamable.com/2aac9z

Tested in 2026.3.7

I'm keen to get these PRs merged to resolve the WhatsApp pairing issues. Please let me know what else is needed from my side to GTM.

dim prairie
wanton monolith
#

I added the ability to specify systemPrompt per account and per group. The design and implementation follows the similar telegram pattern.

The PR is here: https://github.com/openclaw/openclaw/pull/40250

I would appreciate feedback / review
Thanks!

bold panther
#

WHATSAPP LISTENER BUG — CONFIRMED FIX FOR v2026.3.13 (Windows + Linux/macOS)

Same symptoms: channels status shows linked, running, connected, inbound auto-replies work, but all proactive sends fail with No active WhatsApp Web listener.

The bundler creates multiple independent listeners Map instances. Fix: patch all affected chunks to share via globalThis.

Step 1 — Find affected files:
powershell
$dist = "$env:APPDATA\npm\node_modules\openclaw\dist"
Get-ChildItem "$dist*.js" | ForEach-Object {
$m = Select-String -Path $.FullName -Pattern "const listeners = /* @PURE */ new Map()" -Quiet
if ($m) { Write-Host $.Name }
}

Step 2 — Patch all of them:
powershell
$old = 'const listeners = /* @PURE / new Map()'
$new = 'const listeners = globalThis.__openclaw_wa_listeners ??= / @PURE */ new Map()'
Get-ChildItem "$dist*.js" | ForEach-Object {
$c = Get-Content $.FullName -Raw
if ($c -match [regex]::Escape($old)) { $c.Replace($old,$new) | Set-Content $.FullName -NoNewline; Write-Host "Patched: $($_.Name)" }
}

Step 3 — Restart:
powershell
$gwpid = (Get-NetTCPConnection -LocalPort 18789 | Where-Object State -eq 'Listen').OwningProcess | Select-Object -First 1
taskkill /PID $gwpid /F; Start-Sleep 3; openclaw gateway run

Step 4 — Verify: openclaw channels status then test a send.

⚠️ Patch is overwritten by npm update — reapply after updates. Linux/macOS: use /usr/local/lib/node_modules/openclaw/dist

balmy light
#

Hey! For me its working fine as DMs. What I don't understand is how to properly select which Groups I want the bot to interact with. I understand you setup "*" in the allow list and allow them all and then filter down using a phone number allowlist, filtering channels where that specific number is found. (I guess you could use the bots own phone number if its separate). I think this is very broad and must be a limitation imposed by whatsapp.

For testing purposes I'm using a personal phone number. How to define, at a very granular level, which group I want the agent to collaborate?

#

@stray igloo What do yuo think of my question?

dim prairie
spiral berry
#

Hey — I'm on v2026.3.13 (Windows) and the message tool always fails with "No active WhatsApp Web listener" even though WhatsApp is fully connected. Inbound messages and auto-replies work fine, but proactive sends via the tool or CLI always fail. Persists through restarts and relinks. Anyone seen this?

wanton monolith
# balmy light Hey! For me its working fine as DMs. What I don't understand is how to properly ...

My 2c: You specify the whatsapp group id in the policy: something like
''' "groupAllowFrom": [
"*"
],
"groupPolicy": "allowlist",
"groups": {
"972543343341-1427116328@g.us": {
"requireMention": true
},
"120363412702758156@g.us": {
"requireMention": false
}
},
'''
To figure out the group-id you can use a chrome plugin I wrote:
https://chromewebstore.google.com/detail/whatsapp-group-id-extract/lndnieincflimcbelmimbndcplbffheh
Hope it helps, feedback is welcome

delicate cape
spiral berry
clear summit
#

I think it's broken again. it got renamed cloud api

surreal elbow
#

◇ Config warnings ─────────────────────────────────────────────────────────────────────╮
│ │
│ - plugins.entries.whatsapp: plugin not found: whatsapp (stale config entry ignored; │
│ remove it from plugins config) │
│

grim stratus
surreal elbow
#

and how did you solved it ?

grim stratus
#

Rolling back to the previous version
npm install -g openclaw@2026.3.13

surreal elbow
#

i was not prepared for that :))

clear summit
#

shouldn't we wait for a fix ? haha

grim stratus
# clear summit shouldn't we wait for a fix ? haha

Estoy esperando:
[plugins] No se ha podido cargar Telegram desde /home/claw/openclaw/extensions/telegram/index.ts: Error: No se encuentra el módulo «openclaw/plugin-sdk»
Pila de requisitos:

  • /home/claw/openclaw/extensions/telegram/index.ts
    17:58:40 [plugins] error al cargar WhatsApp desde /home/claw/openclaw/extensions/whatsapp/index.ts: Error: No se encuentra el módulo “openclaw/plugin-sdk”
    Pila de requisitos:
  • /home/claw/openclaw/extensions/whatsapp/index.ts
clear summit
#

did it happen with telegram also for you ?

grim stratus
#

plugins] plugins.allow is empty; discovered non-bundled plugins may auto-load: whatsapp (/home/claw/.npm-global/lib/node_modules/openclaw/dist/extensions/whatsapp/index.js). Set plugins.allow to explicit trusted ids.

mint sand
#

We have a new 2nd release today to fix Whatsapp

dim prairie
#

yo yes it broke whatsapp

wanton monolith
#

Hi.
Rebased my pull request. Add account/group systemPrompt hierarchy:
https://github.com/openclaw/openclaw/pull/40250
All CI green, manually tested, All Codex issues resolved.

Feedback much appreciated.

WhatsApp system prompts for groups

WhatsApp supports per-account and per-group system prompts. For group messages, the final prompt delivered to the agent is the account prompt and group prompt joined with a blank line (either part is omitted if not set).

Resolution hierarchy:

  1. Account system prompt (channels.whatsapp.systemPrompt or accounts.<id>.systemPrompt): the root value applies to all accounts; an account-level value overrides it for that account.
  2. Group system prompt (groups["<groupId>"].systemPrompt or groups["*"].systemPrompt): the specific group entry is used if it defines a systemPrompt; falls back to groups["*"].systemPrompt for groups with no specific entry. Account groups fully overrides root groups (same override semantics as Telegram). This means root groups["*"] applies automatically when an account defines no groups of its own, but is replaced entirely once an account defines any groups entry.

Example:

{
  channels: {
    whatsapp: {
      systemPrompt: "Respond in English only.",
      groups: {
        // Applies to all accounts that do not define their own groups map.
        "*": { systemPrompt: "Default prompt for all groups." },
      },
      accounts: {
        work: {
          systemPrompt: "You are a work assistant.",
          groups: {
            // This account defines its own groups, so root groups are fully
            // replaced. To keep a wildcard, define "*" explicitly here too.
            "120363406415684625@g.us": {
              requireMention: false,
              systemPrompt: "Focus on project management.",
            },
            "*": { systemPrompt: "Default prompt for work groups." },
          },
        },
      },
    },
  },
}
winter pilot
#

why i cant use exec tool on whatsapp , but on local GUI chat its working ? any configure i miss?

fallow sparrow
#

🐛 Bug Report: Outbound messages echoed as inbound

Problem: When the agent sends a WhatsApp message, it gets echoed back as an incoming message, causing the agent to respond to its own messages in a loop.

Config: selfChatMode: false is set but doesn't prevent this.

Steps to reproduce:

  1. Agent sends message via WhatsApp
  2. Same message appears as "incoming" with sender_id = user's own number
  3. Agent responds to own message → echo loop

Expected: Outbound messages should not trigger inbound processing.

Version: OpenClaw 2026.3.23-2
Platform: Windows 11, WhatsApp channel

Anyone else seeing this? 🦞

delicate cape
#

The new OpenClaw's version is making WhatsApp users to suffer a bit. I had not saw this king of troubles, this is new.

thorn ingot
fallow sparrow
# thorn ingot Can you test this again?

I just install the Git version. It looks like the WhatsApp issue is gone. But I have different problems right now. I will provide more information once I get the system stable and running again. Went from 23 to 27 now

fallow sparrow
# thorn ingot Can you test this again?

@Marcus Yes! After running v27 for a full day now, I can confirm the echo loop issue is fully resolved. Outbound WhatsApp messages are no longer echoed back as inbound — selfChatMode: false works correctly now.

The system has been stable with the agent sending and receiving messages throughout the day without any self-triggering loops.

One minor observation: I'm seeing periodic WhatsApp gateway disconnects (status 499) with immediate reconnects roughly every 60 seconds. Doesn't affect functionality — messages go through fine — but it's a new pattern since v27 that wasn't there before. Could be related to the WhatsApp bridge or just my setup. Anyone else seeing this?

Overall: echo bug = fixed in v27 ✅

thorn ingot
fallow sparrow
wanton monolith
brisk zealot
#

any idea how to fix this

23:38:58 [health-monitor] [whatsapp:default] health-monitor: restart failed: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
23:38:59 [health] refresh failed: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

raven hedge
#

Just curious if anyone has had their whatsapp number banned when using Baileys with OpenClaw. Have read a few cases where people have been banned, being the unofficial (non Meta) whatsapp implementation

tough fable
#

🚀