OpenClaw 2026.3.22 releases an upgraded plugin and multi-model capabilities, but due to a missing control panel UI package, the dashboard is almost unusable, sparking community concerns.
The open-source AI agent project OpenClaw released version OpenClaw 2026.3.22 last night. This update includes upgrades to the plugin ecosystem, model capabilities, and infrastructure. However, the community quickly discovered a serious issue: resources related to the Control UI were not properly packaged in the release, causing many users to be unable to use the dashboard normally.
This update marks an important step as OpenClaw transitions from an agent framework to an agent platform:
Introducing ClawHub plugin marketplace, allowing developers to distribute, install, and manage various agent plugins, enhancing ecosystem expansion.
Integrates MiniMax M2.7, GPT-5.4 mini / nano, and per-agent reasoning (each agent can be configured for independent reasoning).
Adds /btw side questions, enabling agents to insert auxiliary queries outside their main tasks, improving context handling for complex tasks.
Introduces SSH sandboxes, allowing agents to operate in isolated environments, enhancing security and control.
Integrates multiple external search sources like Exa, Tavily, Firecrawl, strengthening agents’ information retrieval and real-time decision-making.
Despite significant feature upgrades, shortly after release, developers quickly reported issues on X (Twitter) and GitHub: “Control UI assets not found. Build them with pnpm ui:build.”
This indicates the new version missed packaging the control panel UI, and it may be removed in subsequent updates. Community members even said, “It took me 30 minutes to fix, this really shouldn’t happen,” and some mentioned it’s especially problematic for non-coders.
Since the Control UI is one of the core components of OpenClaw (agent monitoring, task management, token control, etc.), this packaging omission effectively means that the default installation of the new version “lacks a control panel.” This is particularly critical for new users, as onboarding can succeed and the gateway can start, but the dashboard is completely unusable. Resulting in a state that appears normal but is actually non-functional.