Bug type
Regression (worked before, now fails)
Summary
After upgrading OpenClaw from 2026.3.2 to 2026.3.7, the Gateway Dashboard becomes inaccessible. The root path
http://127.0.0.1:18789/ returns 404 Not Found instead of serving the control UI.
Steps to reproduce
- Install OpenClaw 2026.3.7:
pnpm install -g openclaw@2026.3.7
- Start the Gateway:
openclaw gateway start
- Open browser to: http://127.0.0.1:18789/
Expected behavior
The OpenClaw Dashboard should load and display the control UI interface.
Actual behavior
The root path returns 404 Not Found with response body:
Not Found
OpenClaw version
2026.3.7
Operating system
windows 11
Install method
pnpm install -g openclaw@2026.3.7
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
- The issue appears to be in the HTTP routing layer, not the Gateway core functionality
- Static files exist but are not being served by the HTTP server
- The resolveControlUiRootSync() function may not be correctly resolving the pnpm installation path in Windows
- The /__openclaw/control-ui-config.json endpoint works, suggesting the control-ui routes are registered but static
file serving is broken
Bug type
Regression (worked before, now fails)
Summary
After upgrading OpenClaw from 2026.3.2 to 2026.3.7, the Gateway Dashboard becomes inaccessible. The root path
http://127.0.0.1:18789/ returns 404 Not Found instead of serving the control UI.
Steps to reproduce
pnpm install -g openclaw@2026.3.7
openclaw gateway start
Expected behavior
The OpenClaw Dashboard should load and display the control UI interface.
Actual behavior
The root path returns 404 Not Found with response body:
Not Found
OpenClaw version
2026.3.7
Operating system
windows 11
Install method
pnpm install -g openclaw@2026.3.7
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
file serving is broken