Workaround for Control UI assets error after OpenClaw 2026.3.22 upgrade
Error and solution for OpenClaw 2026.3.22 upgrade
A user on r/openclaw shared a workaround for the "Control UI assets not found" error that appears after upgrading to OpenClaw version 2026.3.22. The error message states: "Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development."
Steps to fix on macOS with Homebrew Node
The solution involves preserving the control-ui folder during the upgrade process:
- First, install the beta version:
npm install -g [email protected] - Copy the control-ui folder from:
/opt/homebrew/lib/node_modules/openclaw/dist/control-ui - Upgrade to the stable release:
npm install -g openclaw@latest - Paste the control-ui folder back into the new installation directory
The user notes that the same approach should work on other systems—the key is locating the control-ui folder in the OpenClaw installation directory after the beta install and restoring it after the stable upgrade.
📖 Read the full source: r/openclaw
👀 See Also
Running OpenClaw on a Raspberry Pi Model B with Free APIs
OpenClaw runs stably on a Raspberry Pi Model B with free tier APIs including Google Gemma 4 31B IT (~20 RPM, unlimited context) and Gemini Flash, with Firefox headless outperforming Chromium for browser automation.
Reddit user shares common Claude Code prompting mistakes with fixes
A developer using Claude for Node.js backend work identified 10 common prompting mistakes after months of use, including missing validation requirements and treating Claude as one-shot tool. They created a visual guide with fixes for each issue.
Collaborative vs Directive AI Prompts Yield Different Outcomes
A Reddit discussion highlights measurable differences in AI-assisted development outcomes between users who collaborate with AI using "we" language versus those who give directive "do this" commands. The collaborative approach surfaces dead-ends and challenges assumptions through shared context.
Claude Code Self-Audit Finds 3GB of Cruft in ~/.claude — Here's How to Clean It
A user prompted Claude Code to audit its own ~/.claude directory and found 2.6GB of stale session transcripts, 170MB of failed telemetry retry logs, and 153MB of undo buffers — dropping from 3GB to under 200MB after cleanup.