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
Don't Just Paste the AI — Write Your Own Take
A direct plea to developers: stop copying AI chatbot answers verbatim. Use AI as a drafting partner, then rewrite the reply in your own words.
Routing Agent Subtasks to Cheaper Models Dropped Cost from $18 to $4 on Same Refactor
A developer cut agent run costs from $18 to $4 by routing routine subtasks (lint, rename, config edits) to cheap models like DeepSeek V4 Pro and Tencent Hunyuan Hy3, reserving Opus 4.7 for complex reasoning.
35 Days of Claude Code: Why 3 Parallel Agents Is the Real Ceiling
Analysis of 1,800+ Claude Code turns shows the bottleneck isn't context—it's human join capacity. A simple formula N ≈ 1 / (fraction of time waiting on you) explains the wall at 3 agents.
Community Discusses Solutions for OpenClaw Token Consumption
Users share strategies for managing high token usage when running AI agents around the clock.