Skip to main content

Dashboard (Control UI)

The Gateway dashboard is the browser Control UI (the v2 console, served at / by default; gateway.controlUiV2.basePath remounts it). Quick open (local Gateway): Key references: Authentication is enforced at the WebSocket handshake via connect.params.auth (token or password). See gateway.auth in Gateway configuration. Security note: the Control UI is an admin surface (config, channels, exec approvals, device tokens). Do not expose it publicly. The console never stores the gateway token in the browser - it holds it in memory for the connection and keeps only the device token the gateway mints. Prefer localhost, Tailscale Serve, or an SSH tunnel.
  • After onboarding, the CLI auto-opens the dashboard; the link carries the gateway token in its #token= fragment, which the console strips after sign-in.
  • Re-open anytime: openclaw dashboard (copies link, opens browser if possible, shows SSH hint if headless).
  • If the UI prompts for auth, paste the token from gateway.auth.token (or OPENCLAW_GATEWAY_TOKEN) into the console sign-in screen.

Token basics (local vs remote)

  • Localhost: open http://127.0.0.1:18789/.
  • Token source: gateway.auth.token (or OPENCLAW_GATEWAY_TOKEN); openclaw dashboard passes it to the console in the launch link, and the console stores only the device token it mints.
  • Not localhost: use Tailscale Serve (tokenless for Control UI/WebSocket if gateway.auth.allowTailscale: true, assumes trusted gateway host; HTTP APIs still need token/password), tailnet bind with a token, or an SSH tunnel. See Web surfaces.

If you see “unauthorized” / 1008

  • Ensure the gateway is reachable (local: openclaw status; remote: SSH tunnel ssh -N -L 18789:127.0.0.1:18789 user@host then open http://127.0.0.1:18789/).
  • Retrieve the token from the gateway host: openclaw config get gateway.auth.token (or generate one: openclaw doctor --generate-gateway-token).
  • Paste the token into the console sign-in screen, then connect.