OpenClaw Doctor Fails on WhatsApp After 2026.4.20 Update (Missing @whiskeysockets/baileys)

If you updated to OpenClaw 2026.4.20 and are now seeing this error from openclaw doctor:

Error: Cannot find module '@whiskeysockets/baileys'
Require stack:
/root/.nvm/.../openclaw/dist/extensions/whatsapp/auth-store-DY1p5mrF.js

You've hit GitHub issue #69842 — a broader bundled runtime regression in the 4.20 update path.

What's Actually Happening

OpenClaw bundles channel runtimes (Telegram uses grammy, WhatsApp uses @whiskeysockets/baileys) directly inside the npm package. The 4.20 update broke the rebuild path that restores these bundled deps after an upgrade.

The failure happens in two stages:

1. First: openclaw update fails on missing grammy (Telegram runtime) — covered in our earlier post
2. Then: After running npm rebuild -g openclaw to fix Telegram, the doctor now fails on WhatsApp's @whiskeysockets/baileys

This isn't a WhatsApp-specific issue — it's a sign that the rebuild doesn't fully restore all bundled channel runtimes in one pass.

Workarounds (Pick One)

Option 1: Full Reinstall (Most Reliable)

openclaw gateway stop
npm uninstall -g openclaw
npm install -g openclaw@latest
openclaw gateway start
openclaw doctor

A clean install skips the broken rebuild path entirely and starts fresh with all bundled deps intact.

Option 2: Run npm install Inside the Package Dir

cd $(npm root -g)/openclaw
npm install
openclaw gateway restart

This forces npm to re-resolve and install all bundled deps from inside the package directory, which the global rebuild doesn't always cover.

Option 3: Stay on 2026.4.15

npm install -g openclaw@2026.4.15

If you don't need 4.20 features right now, 4.15 is stable. Wait for the patch release before upgrading.

Who Is Affected

• Global npm installs (npm install -g openclaw) — not git checkouts
• Users upgrading from 2026.4.15 or earlier to 2026.4.20
• Anyone using WhatsApp or Telegram channels (both bundled runtimes are broken)
• Node v22+ on Linux/Ubuntu (most common reported environment)

If you're running a git checkout or Docker image that builds from source, you're likely not affected.

Status

As of April 22, 2026: open issue, no patch released yet. The Telegram grammy fix (#69837) was merged separately but the underlying rebuild regression persists for WhatsApp.

Don't Want to Debug This Yourself?

This is exactly the kind of upstream regression that breaks production setups without warning. ClawReady's managed care clients get:

• Upgrade monitoring — we watch GitHub issues so you don't have to
• Same-day remediation on critical bugs like this one
• Rollback assistance when an update breaks your setup

Book a Free Audit →