openclaw - ✅(Solved) Fix [Bug]: Control UI missing in npm package v2026.3.22 [1 pull requests, 3 comments, 4 participants]

openclaw2026-03-23 12:02:11

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#52817•Fetched 2026-04-08 01:18:54

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Participants

Timeline (top)

commented ×3labeled ×2referenced ×2subscribed ×2

Control UI (web dashboard) inaccessible after npm install of v2026.3.22 — returns 503 with "assets not found"

Error Message

503 error: "Control UI assets not found. Build them with pnpm ui:build"

Root Cause

Control UI (web dashboard) inaccessible after npm install of v2026.3.22 — returns 503 with "assets not found"

Fix Action

Fix / Workaround

Affected: All users who accessRegression: v2026.3.11 did not have this issue (dist/control-ui/ was present in the npm package) Workaround: Manually clone repo, run pnpm ui:build, copy dist/control-ui/ to npm package directory OpenClaw via browser (Control UI) Severity: High — Control UI completely inaccessible, only TUI works Frequency: 100% (every fresh install of v2026.3.22) Consequence: Users cannot use the web dashboard; workaround is to use TUI (terminal) instead

Affected: All users who access OpenClaw via browser (Control UI) Severity: High — Control UI completely inaccessible, only TUI works Frequency: 100% (every fresh install of v2026.3.22) Consequence: Users cannot use the web dashboard; workaround is to use TUI (terminal) instead

Regression: v2026.3.11 did not have this issue (dist/control-ui/ was present in the npm package) Workaround: Manually clone repo, run pnpm ui:build, copy dist/control-ui/ to npm package directory

PR fix notes

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

Repository: openclaw/openclaw
Author: Linux2010
State: closed | merged: False
Link: https://github.com/openclaw/openclaw/pull/52839

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:

✅ dist/control-ui/ directory exists
✅ index.html is present
✅ assets/ directory exists with files
❌ 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)

Code Example

$ curl http://127.0.0.1:18789/
Control UI assets not found. Build them with `pnpm ui:build` (auto-installs UI deps), or run `pnpm ui:dev` during development.

$ ls ~/.nvm/versions/node/v22.22.0/lib/node_modules/openclaw/dist/
# control-ui/ directory is MISSING (only control-ui-assets-*.js and control-ui-shared-*.js exist)

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Control UI (web dashboard) inaccessible after npm install of v2026.3.22 — returns 503 with "assets not found"

Steps to reproduce

npm install -g [email protected]
openclaw gateway start
Visit http://127.0.0.1:18789/

Expected behavior

Control UI loads and displays the web dashboard (worked correctly in v2026.3.11)

Actual behavior

503 error: "Control UI assets not found. Build them with pnpm ui:build" The dist/control-ui/ directory is missing from the npm package

OpenClaw version

2026.3.22

Operating system

Ubuntu 22.04 (Linux 6.8.0)

Install method

npm global install

Model

minimax-portal/MiniMax-M2.7

Provider / routing chain

direct to minimax API (no gateway/proxy)

Additional provider/model setup details

Logs, screenshots, and evidence

$ curl http://127.0.0.1:18789/
Control UI assets not found. Build them with `pnpm ui:build` (auto-installs UI deps), or run `pnpm ui:dev` during development.

$ ls ~/.nvm/versions/node/v22.22.0/lib/node_modules/openclaw/dist/
# control-ui/ directory is MISSING (only control-ui-assets-*.js and control-ui-shared-*.js exist)

Impact and severity

Additional information

Regression: v2026.3.11 did not have this issue (dist/control-ui/ was present in the npm package) Workaround: Manually clone repo, run pnpm ui:build, copy dist/control-ui/ to npm package directory

extent analysis

Fix Plan

To fix the issue of the Control UI being inaccessible after installing OpenClaw v2026.

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?

FAQ

Expected behavior

Control UI loads and displays the web dashboard (worked correctly in v2026.3.11)

#api #ssr #prompt issue #agent setup #task chaining

Still need to ship something?

×6

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

openclaw - ✅(Solved) Fix [Bug]: Control UI missing in npm package v2026.3.22 [1 pull requests, 3 comments, 4 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

PR fix notes

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

Description (problem / solution / changelog)

Summary

Problem

Root Cause

Solution

Changes

Testing

Impact

Related Issues

Workaround for Affected Users

Changed files

Code Example

Bug type

Summary

Steps to reproduce

Expected behavior

Actual behavior

OpenClaw version

Operating system

Install method

Model

Provider / routing chain

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

Additional information

extent analysis

Fix Plan

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING