OpenClaw v2026.3.22 upgrade breaks WhatsApp — recovery via v2026.3.23-2
Context
NOVA recommended upgrading from v2026.3.13 to v2026.3.22 (cron deadlock fix, security hardening, compaction persona drift fix). Update succeeded but WhatsApp channel failed to load — NOVA went dark for ~12 hours.
Root Cause
v2026.3.22 unbundled WhatsApp from stock extensions (moved to plugin architecture) but shipped without light-runtime-api.js — the runtime bridge the new plugin system requires. Error: WhatsApp plugin runtime is unavailable: missing light-runtime-api for plugin 'whatsapp'.
Recovery Steps
- Fix config: remove
context1m: true(native on Max plan), changethinkingDefault: "xhigh"→"high"(valid values: low/medium/high) - Upgrade to v2026.3.23-2 (hotfix that restores
light-runtime-api.jsin extensions/whatsapp/) - Run
openclaw plugins install whatsapp— required for new plugin architecture (addsplugins.load.pathsandplugins.installs) - Set
plugins.allow: ["whatsapp", "perplexity"]— security hardening - Fix systemd: entrypoint
entry.js→index.js, version label - Run
openclaw doctor --fix— scaffold safeBinProfiles - Remove
jqfrom safeBins (env builtin leaks environment variables) - Clean stale backups and npm logs
Key Lessons
- v2026.3.22 is broken for WhatsApp — always verify extensions list before upgrading
- v2026.3.23-2 is the minimum viable version for WhatsApp plugin runtime
openclaw plugins install whatsappis NOW REQUIRED after any upgrade (new plugin architecture)context1mparam was removed — Max plan provides 1M context nativelythinkingDefaultvalid values: low, medium, high (NOT xhigh)openclaw doctor --fixscaffolds safeBinProfiles entries needed by new version- Perplexity web search migrated from
tools.web.search.perplexitytoplugins.entries.perplexityin v2026.3.23+
Files Modified
/home/openclaw/.openclaw/openclaw.json— 8 config changes/home/openclaw/.config/systemd/user/openclaw-gateway.service— entrypoint + version