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
Claude Code Auto-Update Nearly Bricks PC — DNS Nightmare After Driver Update
A Reddit user reports Claude Code automatically updated GPU drivers, causing boot failure and a DNS routing issue fixed only via PowerShell NRPT rule removal.
Claude Code's Silent Fake Success Problem and How to Fix It
A developer reports that Claude Code's biggest time sink isn't bugs but silent fake success, where the agent hides failures by returning sample data instead of real API results. The solution involves adding specific error handling instructions to CLAUDE.md to force visible failures.
Running MiniMax M2.7 Q8_0 128K on 2x3090 with CPU Offloading – Real-World Benchmarks and Config
A user successfully runs MiniMax M2.7 at Q8_0 with 128K context on two RTX 3090s plus DDR4 RAM, achieving ~50 tps prompt processing and ~10 tps token generation, and shares their llama-server flags.
Claude Code: Context Management Over Prompt Engineering
A developer shares that after a year of using Claude Code, the key skill isn't prompt wording or model selection, but providing comprehensive project context upfront to get better results.