#can't access dashboard - Control UI Assets not found after update

1 messages · Page 1 of 1 (latest)

steep berryBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

somber oar
#

where do i run pnpm ui:dev ?

#

i tried in .openclaw but nothing

fossil gulchBOT
#

pnpm ui:dev is only for source/dev installs — run it in the OpenClaw repo root (the folder with package.json, ui/, and scripts/ui.js).

Example:

cd ~/openclaw # your git checkout
pnpm install
pnpm ui:dev

For your case (dashboard broken after update), you usually want:

pnpm ui:build
openclaw gateway restart

…also from that same repo root.

If you installed OpenClaw globally (not from a git checkout), don’t use ui:dev; reinstall instead:

somber oar
#

c@debian:~/.openclaw$ pnpm install
Packages are hard linked from the content-addressable store to the virtual store.
Content-addressable store is at: /home/c/.local/share/pnpm/store/v10
Virtual store is at: node_modules/.pnpm
 ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED  Failed to prepare git-hosted package fetched from "https://codeload.github.com/tobi/qmd/tar.gz/2b8f329d7e4419af736a50e917057f685ad41110": The git-hosted package "@tobilu/qmd@2.0.1" needs to execute build scripts but is not in the "onlyBuiltDependencies" allowlist.

This error happened while installing a direct dependency of /home/c

Add the package to "onlyBuiltDependencies" in your project's pnpm-workspace.yaml to allow it to run scripts. For example:
onlyBuiltDependencies:

  • "@tobilu/qmd"
    Progress: resolved 5, reused 5, downloaded 0, added 0
    c@debian:~/.openclaw$ pnpm ui:dev
    /home/c/.openclaw:
     ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command "ui:dev" not found
    c@debian:~/.openclaw$
fossil gulchBOT
#

Yep — ~/.openclaw is the state/config folder, not the source code folder.
So pnpm ui:build won’t work there.

For your setup, do this instead (global reinstall fixes missing dist/control-ui files):

pnpm add -g openclaw@latest
openclaw doctor
openclaw gateway restart
openclaw dashboard

If that still fails, paste:

openclaw --version
openclaw gateway status
# 
command -v openclaw

and I’ll tell you the exact folder your binary is running from.

#

Perfect, this output confirms the issue:

  • You’re running commands in ~/.openclaw (state dir) — wrong place for ui:dev/ui:build.
  • That @tobilu/qmd error is from another project context, not OpenClaw itself.

Use the OpenClaw updater/repair path instead (no pnpm install in ~/.openclaw):

cd ~
openclaw --version
openclaw update
openclaw doctor
openclaw gateway restart
openclaw dashboard

If dashboard still fails after that, paste:

# 
openclaw gateway status
openclaw status --all

and I’ll give you the exact next fix.

somber oar
#

OpenClaw status --all
Overview

│ Version │ 2026.3.22
│ OS │ linux 6.12.74+deb13+1-amd64 (x64)
│ Node │ 24.13.0
│ Config │ ~/.openclaw/openclaw.json
│ Dashboard │ http://127.0.0.1:18789/
│ Tailscale │ off
│ Channel │ stable (default)
│ Update │ pnpm · up to date · npm latest 2026.3.22 │
│ Gateway │ local · ws://127.0.0.1:18789 (local loopback) · reachable 17ms · auth token │
│ Security │ Run: openclaw security audit --deep │
│ Gateway self │ app 2026.3.22 linux 6.12.74+deb13+1-amd64 │
│ Gateway service │ systemd installed · enabled · running (pid 5859) │
│ Node service │ systemd not installed
│ Agents │ 4 total · 1 bootstrapping · 0 active · 134 sessions

#

Diagnosis (read-only)

Gateway connection details:
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/c/.openclaw/openclaw.json
Bind: loopback

âś“ Config: /home/c/.openclaw/openclaw.json
âś“ Secret diagnostics (0)
âś“ Restart sentinel: none
! Port 18789
Port 18789 is already in use.

  • pid 5859 c: openclaw-gateway (127.0.0.1:18789)
  • Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
    ! Tailscale: off · unknown
    error: Error: spawn tailscale ENOENT
    ✓ Skills: 45 eligible · 0 missing · /home/c/.openclaw/workspace
    âś“ Plugin compatibility (none)
    âś“ Channel issues (none)

Pasteable debug report. Auth tokens redacted.
Troubleshooting: https://docs.openclaw.ai/troubleshooting

#

hello?

fossil gulchBOT
#

Yep, still here đź‘‹

Fastest path now: copy/paste this whole block:

cd ~
openclaw --version
openclaw update
openclaw doctor
openclaw gateway restart
openclaw dashboard

Then paste the output of:

# 
openclaw gateway status

I’ll debug the next step immediately from that.

somber oar
#

openclaw --version
OpenClaw 2026.3.22 (4dcc39c)

#

my token dashboard is in the text

fossil gulchBOT
#

Perfect — version is current ✅

Next step: run these and paste output:

openclaw update
openclaw doctor
openclaw gateway restart
openclaw gateway status

If gateway status still mentions missing Control UI assets, run this too and paste:

openclaw status --all
somber oar
#

c@debian:~/.npm-global/lib/node_modules/openclaw/dist$
c@debian:~/.npm-global/lib/node_modules/openclaw/dist$ pnpm ui:dev

openclaw@2026.3.22 ui:dev /home/c/.npm-global/lib/node_modules/openclaw
node scripts/ui.js dev

node:internal/modules/cjs/loader:1424
throw err;
^

Error: Cannot find module '/home/c/.npm-global/lib/node_modules/openclaw/scripts/ui.js'
at Module._resolveFilename (node:internal/modules/cjs/loader:1421:15)
at defaultResolveImpl (node:internal/modules/cjs/loader:1059:19)
at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1064:22)
at Module._load (node:internal/modules/cjs/loader:1227:37)
at TracingChannel.traceSync (node:diagnostics_channel:328:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:245:24)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}

Node.js v24.13.0
 ELIFECYCLE  Command failed with exit code 1.

fossil gulchBOT
#

Nice catch — that explains it.

ui:dev is not usable in global npm installs (those dev scripts aren’t shipped there).
So yes, this path is a dead end.

Use this recovery flow instead:

cd ~
pnpm remove -g openclaw
pnpm add -g openclaw@2026.3.22
ls -l ~/.npm-global/lib/node_modules/openclaw/dist/control-ui/index.html
openclaw doctor
openclaw gateway restart
openclaw dashboard
#

If that ls line says “No such file”, switch to source install (which includes build tooling):

git clone https://github.com/openclaw/openclaw.git ~/openclaw
cd ~/openclaw
pnpm install
pnpm build
pnpm ui:build
openclaw doctor
openclaw gateway restart

Paste the ls -l .../dist/control-ui/index.html result if you want me to verify before you do more steps.

molten tulip
#

aha,Just updated to 2026.3.22 (4dcc39c) and I'm still getting the same error.

fossil gulchBOT
#

Yep — if you’re on 2026.3.22 and still seeing this, it looks like a packaging regression in that npm release (missing dist/control-ui in global installs).

Quick check:

ls -l ~/.npm-global/lib/node_modules/openclaw/dist/control-ui/index.html

If that file is missing, use one of these workarounds:

Fastest workaround

openclaw update --channel beta
openclaw doctor
openclaw gateway restart
openclaw dashboard
#

Or run from source (fully reliable)

git clone https://github.com/openclaw/openclaw.git ~/openclaw
cd ~/openclaw
pnpm install
pnpm build
pnpm ui:build
openclaw doctor
openclaw gateway restart

Please file a bug with your output (openclaw --version + missing file check):
https://github.com/openclaw/openclaw/issues

Docs: https://docs.openclaw.ai/install/updating

GitHub
openclaw/openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞 - openclaw/openclaw

OpenClaw
Updating - OpenClaw
somber oar
#

c@debian:~$ git clone https://github.com/openclaw/openclaw.git
Cloning into 'openclaw'...
remote: Enumerating objects: 281955, done.
remote: Counting objects: 100% (191/191), done.
remote: Compressing objects: 100% (108/108), done.
remote: Total 281955 (delta 114), reused 83 (delta 83), pack-reused 281764 (from 2)
Receiving objects: 100% (281955/281955), 319.02 MiB | 36.65 MiB/s, done.
Resolving deltas: 100% (181737/181737), done.
c@debian:~$ cd openclaw/
c@debian:~/openclaw$ pnpm install
pnpm build
pnpm ui:build
openclaw doctor
openclaw gateway restart
Scope: all 79 workspace projects
Lockfile is up to date, resolution step is skipped
Packages: +1249
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Downloading node-llama-cpp@3.16.2: 28.41 MB/28.41 MB, done
Downloading @img/sharp-libvips-linuxmusl-x64@1.2.4: 7.65 MB/7.65 MB, done
Downloading @napi-rs/canvas-linux-x64-gnu@0.1.95: 13.94 MB/13.94 MB, done
Downloading @napi-rs/canvas-linux-x64-musl@0.1.95: 13.33 MB/13.33 MB, done
Downloading @node-llama-cpp/linux-x64@3.16.2: 7.42 MB/7.42 MB, done
Downloading @oxlint/binding-linux-x64-gnu@1.56.0: 5.58 MB/5.58 MB, done
Downloading @oxlint-tsgolint/linux-x64@0.17.1: 12.67 MB/12.67 MB, done
Downloading @oxlint/binding-linux-x64-musl@1.56.0: 5.53 MB/5.53 MB, done
Downloading @typescript/native-preview-linux-x64@7.0.0-dev.20260322.1: 9.82 MB/9.82 MB, done
Downloading @rolldown/binding-linux-x64-musl@1.0.0-rc.9: 8.46 MB/8.46 MB, done
Downloading @node-llama-cpp/linux-x64-vulkan@3.16.2: 24.10 MB/24.10 MB, done
Downloading @rolldown/binding-linux-x64-gnu@1.0.0-rc.9: 8.51 MB/8.51 MB, done
Downloading @node-llama-cpp/linux-x64-cuda@3.16.2: 124.72 MB/124.72 MB, done

molten tulip
#

Confirmed on two different PCs. Turns out dist/control-ui was missing. Problem solved

desert current
somber oar
#

../dist/control-ui/assets/instances-QVUbeONf.js 2.86 kB │ gzip: 1.08 kB │ map: 5.71 kB
../dist/control-ui/assets/logs-BbHV8FOx.js 3.12 kB │ gzip: 1.15 kB │ map: 6.55 kB
../dist/control-ui/assets/format-DeRVtGzv.js 3.71 kB │ gzip: 1.60 kB │ map: 19.61 kB
../dist/control-ui/assets/debug-hN0w3Uzd.js 4.23 kB │ gzip: 1.28 kB │ map: 7.43 kB
../dist/control-ui/assets/de-DaHzXuN7.js 4.32 kB │ gzip: 2.11 kB │ map: 6.89 kB
../dist/control-ui/assets/skills-BaxA3XRt.js 4.68 kB │ gzip: 1.63 kB │ map: 9.13 kB
../dist/control-ui/assets/zh-TW-CM-C0Ey2.js 4.69 kB │ gzip: 2.67 kB │ map: 8.08 kB
../dist/control-ui/assets/pt-BR-CUPpmFmM.js 5.15 kB │ gzip: 2.41 kB │ map: 8.62 kB
../dist/control-ui/assets/zh-CN-DYuK7yBr.js 10.95 kB │ gzip: 5.25 kB │ map: 18.70 kB
../dist/control-ui/assets/sessions-DPZqw74P.js 11.66 kB │ gzip: 3.19 kB │ map: 27.87 kB
../dist/control-ui/assets/es-CSJZiMH1.js 11.93 kB │ gzip: 4.83 kB │ map: 19.08 kB
../dist/control-ui/assets/lit-BZwq2xLD.js 15.03 kB │ gzip: 5.87 kB │ map: 34.52 kB
../dist/control-ui/assets/nodes-BXlsFQVB.js 22.67 kB │ gzip: 5.06 kB │ map: 54.44 kB
../dist/control-ui/assets/channels-l3ZU8ltn.js 25.43 kB │ gzip: 4.63 kB │ map: 57.90 kB
../dist/control-ui/assets/agents-DQiopkVo.js 34.75 kB │ gzip: 7.62 kB │ map: 78.71 kB
../dist/control-ui/assets/cron-CcFCC6Kj.js 49.78 kB │ gzip: 8.45 kB │ map: 97.38 kB
../dist/control-ui/assets/index-khmCNvxp.js 579.17 kB │ gzip: 154.87 kB │ map: 1,657.12 kB

âś“ built in 528ms

#

but same error when i access dashboard Control UI assets not found. Build them with pnpm ui:build (auto-installs UI deps), or run pnpm ui:dev during development.

#

how do i switch to run from source?

molten tulip
#

Skip openclaw doctor. Just manually copy the control-ui build to the openclaw/dist/ folder and you're good to go

desert current
molten tulip
#

Clone and build the UI

git clone https://github.com/openclaw/openclaw.git /tmp/openclaw-src
cd /tmp/openclaw-src

pnpm install
pnpm ui:build

Copy to your actual install directory

cp -r dist/control-ui YOUR_INSTALL_DIR/dist/control-ui

somber oar
#

how do i switch from global install to the git clone method?

molten tulip
#

No need to switch . Just build it in a temp dir to grab the control-ui folder.

#

The main issue is that the 2026.3.22 release is missing the control-ui folder. openclaw doctor won't catch this, you'll have to manually build and move it.

somber oar
#

move it to where?

#

i have no clue where my installdir is

molten tulip
#

your openclaw dir

somber oar
#

where?

#

which openclaw
/home/c/.local/share/pnpm/openclaw ?

molten tulip
#

openclaw gateway status

#

Check openclaw gateway status. The Command: field on line 2 will show your actual installation path

strange tinsel
#

same issue here. there is no dist folder in root installation?

cedar oxide
# molten tulip # Clone and build the UI git clone https://github.com/openclaw/openclaw.git /tmp...

sorry, PS C:\tmp\openclaw-src> pnpm install
pnpm : Termine 'pnpm' non riconosciuto come nome di cmdlet, funzione, programma eseguibile o file script. Controllare
l'ortografia del nome o verificare che il percorso sia incluso e corretto, quindi riprovare.
In riga:1 car:1

  • pnpm install
  •   + CategoryInfo          : ObjectNotFound: (pnpm:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException
arctic canopy
cedar oxide
fossil gulchBOT
#

Yep — that PowerShell error means pnpm isn’t installed/active on your Windows shell.

Also, this thread is likely hitting a 2026.3.22 packaging regression (missing dist/control-ui in global install), so even successful update can still show “Control UI assets not found”.

1) Enable pnpm (Windows PowerShell)

corepack enable
corepack prepare pnpm@latest --activate
pnpm -v

2) Temporary workaround (until fixed republish)

Install a working version, then restart gateway:

pnpm add -g openclaw@2026.3.13
openclaw gateway restart
# 
openclaw dashboard

If you want to stay on latest code instead, use source install + build (pnpm ui:build) from a git checkout.

If someone opens a bug for this packaging issue, please use GitHub issues:
https://github.com/openclaw/openclaw/issues

GitHub
openclaw/openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞 - openclaw/openclaw