openclaw - ✅(Solved) Fix [Bug]: 2026/3/23最新版的更新之后UI界面不见了,报错了 [1 pull requests, 16 comments, 15 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#52820Fetched 2026-04-08 01:18:49
View on GitHub
Comments
16
Participants
15
Timeline
23
Reactions
2

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

Root Cause

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

Fix Action

Fixed

PR fix notes

PR #52839: fix(packaging): add Control UI build verification to prevent broken releases (#52808)

Description (problem / solution / changelog)

Summary

Adds build verification to prevent npm releases without Control UI assets. Fixes #52808, #52817, #52820.

Problem

v2026.3.22 was published without dist/control-ui/ directory, causing:

  • ❌ 503 error: "Control UI assets not found"
  • ❌ Web dashboard completely inaccessible
  • ❌ 100% reproducible for all npm install users

Root Cause

prepack hook ran pnpm ui:build but didn't verify success before publishing. If ui:build failed silently or was skipped, broken package was published.

Solution

Add verification script that runs after ui:build:

"prepack": "pnpm build && pnpm ui:build && node scripts/verify-ui-build.js"

Verification checks:

  1. dist/control-ui/ directory exists
  2. index.html is present
  3. assets/ directory exists with files
  4. ❌ Fails build with helpful error message if missing

Changes

  • scripts/verify-ui-build.js: New verification script (80 lines)
  • package.json: Add verification to prepack hook
  • CHANGELOG.md: Document the fix

Testing

Run manually:

node scripts/verify-ui-build.js

Expected output:

🔍 Verifying Control UI build...
✅ Control UI directory exists: /path/to/dist/control-ui
✅ Required file present: index.html
✅ Required directory present: assets/ (X files)
✅ Control UI verification PASSED

If UI not built:

❌ Control UI directory not found: /path/to/dist/control-ui
This usually means the UI build failed or was skipped.

Impact

  • ✅ Prevents future broken releases
  • ✅ Fails fast with helpful error message
  • ✅ Zero runtime impact (build-time only)
  • ✅ Backward compatible

Related Issues

  • Fixes #52808 - Bug: dist/control-ui/ missing from npm package in 2026.3.22
  • Fixes #52817 - Control UI missing in npm package v2026.3.22
  • Fixes #52820 - 2026/3/23 最新版的更新之后 UI 界面不见了,报错了

Workaround for Affected Users

Until v2026.3.23 is released:

# Option 1: Copy from 2026.3.13
npm pack [email protected]
tar -xzf openclaw-2026.3.13.tgz
cp -r package/dist/control-ui/ $(npm root -g)/openclaw/dist/
openclaw gateway restart

# Option 2: Manual build
cd $(npm root -g)/openclaw
pnpm ui:build
openclaw gateway restart

Changed files

  • package.json (modified, +2/-1)
  • scripts/verify-ui-build.js (added, +93/-0)
  • src/infra/fs-safe.test.ts (modified, +48/-0)
  • src/infra/fs-safe.ts (modified, +3/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

Steps to reproduce

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

Expected behavior

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

Actual behavior

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

OpenClaw version

2026/3/23

Operating system

windows

Install method

No response

Model

minimax2.5

Provider / routing chain

xxx

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue of Control UI assets not being found, follow these steps:

  • Run pnpm ui:build to build the UI assets and auto-install dependencies.
  • Alternatively, run pnpm ui:dev during development.

Code Changes

No code changes are required. However, ensure that your package.json file contains the necessary scripts:

"scripts": {
  "ui:build": "build command here",
  "ui:dev": "development command here"
}

Replace "build command here" and "development command here" with the actual commands for building and developing your UI assets.

Verification

After running pnpm ui:build or pnpm ui:dev, verify that the Control UI assets are accessible and the issue is resolved.

Extra Tips

  • Make sure you are in the correct directory when running the pnpm commands.
  • If you encounter any issues with dependencies, try running pnpm install to ensure all dependencies are installed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: 2026/3/23最新版的更新之后UI界面不见了,报错了 [1 pull requests, 16 comments, 15 participants]