openclaw - 💡(How to fix) Fix [Bug]: Control UI Not Working - Port 18789 [1 comments, 1 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#53672Fetched 2026-04-08 01:25:02
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×2commented ×1

After upgrading from 2026.3.13 to 2026.3.22 it worked fine, until I had to update my codex Oauth, after updating it, the Control UI shows this error: Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

After updating pnpm it still doesn't work. Tried both Claude and Codex, neither could solve, so reversed back to 2026.3.13, now it works again w new Oauth.

Error Message

After upgrading from 2026.3.13 to 2026.3.22 it worked fine, until I had to update my codex Oauth, after updating it, the Control UI shows this error: error shown above

Root Cause

After upgrading from 2026.3.13 to 2026.3.22 it worked fine, until I had to update my codex Oauth, after updating it, the Control UI shows this error: Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

After updating pnpm it still doesn't work. Tried both Claude and Codex, neither could solve, so reversed back to 2026.3.13, now it works again w new Oauth.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

After upgrading from 2026.3.13 to 2026.3.22 it worked fine, until I had to update my codex Oauth, after updating it, the Control UI shows this error: Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

After updating pnpm it still doesn't work. Tried both Claude and Codex, neither could solve, so reversed back to 2026.3.13, now it works again w new Oauth.

Steps to reproduce

Codex Oauth then Control UI doesn't work on 18789

Expected behavior

Control UI doesn't work

Actual behavior

error shown above

OpenClaw version

2026.3.22

Operating system

Ubuntu 24

Install method

npm

Model

codex 5.4

Provider / routing chain

??

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 with the Control UI not working after updating Codex Oauth, follow these steps:

  • Run pnpm ui:build to build the Control UI assets.
  • If the issue persists, try running pnpm ui:dev during development.
  • Ensure that all dependencies are up-to-date by running pnpm install.
  • If you are using a version control system, try reverting any recent changes to the package.json file.

Example code to build and run the Control UI:

pnpm ui:build
pnpm ui:dev

Alternatively, you can try to update the dependencies manually:

pnpm update
pnpm install

Verification

To verify that the fix worked, check the Control UI for any errors. If the issue is resolved, the UI should load correctly without displaying the "Control UI assets not found" error.

Extra Tips

  • Make sure to check the version compatibility of the Codex Oauth and Control UI.
  • If the issue persists, try to reset the node_modules directory by running pnpm install or npm install.
  • Consider using a version control system to track changes to your project's dependencies and configuration.

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 doesn't work

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 - 💡(How to fix) Fix [Bug]: Control UI Not Working - Port 18789 [1 comments, 1 participants]