Description

OpenClaw Gateway v2026.2.22-2 on Windows returns 404 for all HTTP requests to the root path /. The Gateway runs successfully and WebSocket connections work, but the Control UI / Dashboard is not accessible via browser.

Environment

• OpenClaw Version: 2026.2.22-2
• Platform: Windows (Git Bash / MINGW64)
• Node.js: v22.16.0

Steps to Reproduce

1. Install OpenClaw: npm install -g openclaw
2. Start gateway: openclaw gateway run
3. Open browser to http://127.0.0.1:18789/
4. Result: 404 Not Found

Expected Behavior

Dashboard/Control UI should be accessible at http://127.0.0.1:18789/

Additional Details

• WebSocket connection works: ws://127.0.0.1:18789
• Canvas is mounted at /__openclaw__/canvas/ but returns 404
• Config endpoint /__openclaw/control-ui-config.json returns JSON when controlUi.basePath is configured
• Static files in dist/control-ui/ exist but are not served

Configuration

{
  "gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "loopback"
  }
}

Investigation Notes

The issue appears to be in the HTTP request handler - when controlUi.basePath is not set, the Control UI routes return 404. Even when basePath is configured, the static files are not being served correctly on Windows.