Bug type

Regression (worked before, now fails)

Summary

Control UI / Dashboard returns "Not Found" on Windows (2026.3.x)

Environment

• OS: Windows 10 (10.0.19045, x64)
• OpenClaw: 2026.3.2 (installed via npm/pnpm global)
• Node.js: v22.19.0
• Gateway: Started via openclaw gateway --port 18789 (or a .cmd script that runs the same)

Steps to reproduce

1. Start the gateway: openclaw gateway --port 18789
2. Open in browser: http://127.0.0.1:18789/#token=<gateway-token>
3. Also tried: http://127.0.0.1:18789/ui/#token=<gateway-token> with gateway.controlUi.basePath set to "/ui" in config.

Expected

• Control UI / Dashboard loads at the configured URL (either / or /ui).

Actual

• Both URLs return HTTP 404 "Not Found" (plain text, no HTML).
• Gateway process runs; WebSocket and other gateway features appear to work (e.g. openclaw status, channels).
• Only the web Dashboard fails to load.

Config (relevant part)

"gateway": {
  "port": 18789,
  "mode": "local",
  "bind": "loopback",
  "auth": {
    "mode": "token",
    "token": "<redacted>"
  }
}

Tried adding (no change):

"controlUi": {
  "basePath": "/ui"
}

Then opened http://127.0.0.1:18789/ui/#token=... — still 404.

Workaround

• Using TUI works: openclaw tui connects to the gateway and provides a terminal UI.

Related

• Dashboard/Control UI returns 404 on Windows #24938 (Dashboard/Control UI returns 404 on Windows) — closed as duplicate of [Bug] Dashboard unreachable + gateway instability on Windows in 2026.2.22-2 (fixed by downgrading to 2026.2.21-2) #24879.
• [2026.3.1 regression] Control UI handler runs before plugin HTTP routes — plugin routes unreachable #31766 (Control UI handler runs before plugin HTTP routes) — fix reordered routes; may be related to routing on Windows.

Ask

• Is the Control UI intended to work on Windows in 2026.3.x when serving from / or from a custom controlUi.basePath (e.g. /ui)?
• If there is a known workaround (e.g. specific basePath, or build/run step) for Windows, a note in the docs would help.

Thanks for maintaining OpenClaw.

Steps to reproduce

1. Start the gateway: openclaw gateway --port 18789
2. Open in browser: http://127.0.0.1:18789/#token=<gateway-token>
3. Also tried: http://127.0.0.1:18789/ui/#token=<gateway-token> with gateway.controlUi.basePath set to "/ui" in config.

Expected behavior

• Control UI / Dashboard loads at the configured URL (either / or /ui).

Actual behavior

• Both URLs return HTTP 404 "Not Found" (plain text, no HTML).
• Gateway process runs; WebSocket and other gateway features appear to work (e.g. openclaw status, channels).
• Only the web Dashboard fails to load.

OpenClaw version

2026.3.2

Operating system

window 11

Install method

pnpm

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response