How do I fix the OpenClaw v2026.3.22 Dashboard UI bug?

Upgrade to v2026.3.23-2 (current stable as of March 25, 2026) or roll back to v2026.3.13. The bug was caused by missing dist/control-ui/ directory in the npm tarball.

Why is my OpenClaw WhatsApp integration broken after the v2026.3.22 update?

The @openclaw/whatsapp package was moved to a standalone package in v2026.3.22 but not published to npm yet, leaving a broken dependency. Fix: upgrade to v2026.3.23-2.

What are the breaking changes in OpenClaw v2026.3.22?

12 breaking changes including: CLAWDBOT_* and MOLTBOT_* environment variables removed, legacy Chrome extension relay path removed, and ClawHub replacing npm as default plugin store.

What's new in OpenClaw v2026.3.22?

Major features: ClawHub as default plugin store, 48-hour agent session timeout (up from 10 min), GPT-5.4 as default OpenAI model, Anthropic Vertex AI provider support, and 30+ security patches.

Should I upgrade to OpenClaw v2026.3.22?

Skip v2026.3.22 and go directly to v2026.3.23-2 which fixes the Dashboard UI and WhatsApp packaging bugs while retaining all major features.

← Back to dashboard

clawsmith.com/signal/openclaw-v2026-3-22-dashboard-whatsapp-broken

⚠ IssueWide OpenFrameworkLive

OpenClaw v2026.3.22 Breaks Dashboard UI and WhatsApp for npm Users

OpenClaw v2026.3.22 broke Dashboard UI and WhatsApp for npm users via two packaging bugs. Stabilization patches v2026.3.23 and v2026.3.23-2 landed March 23-25, fixing Plugin SDK transition and browser reliability. Users advised to roll back to v2026.3.13 or upgrade to v2026.3.23-2.

Product Idea from this Signal

A sandbox environment that tests OpenClaw upgrades against your agents before they break production

3.2k ▲

Every OpenClaw release breaks something. v2026.3.22 broke the Dashboard and WhatsApp. v2026.3.2 silently disabled all agent tools. v2026.3.8 killed cron jobs and compaction. v2026.3.28 permanently broke the exec tool in a way that downgrading could not fix. Users discover these regressions after upgrading their production instance. There is no pre-upgrade testing, no rollback plan, and no way to know if a new version will break your specific configuration. This tool creates a sandboxed replica of your OpenClaw setup, runs the upgrade there first, executes your critical workflows against it, and gives you a pass/fail verdict before touching production.

DEVTOOLCLITESTINGSYSADMIN

Wide OpenView Opportunity →