Skip to main content

Web (Gateway)

The Gateway serves its browser surfaces from the same port as the Gateway WebSocket:
  • Control UI v2, the operator console, at the root (/) by default (gateway.controlUiV2.basePath remounts it)
  • the web client at /v2/client when gateway.webClient.enabled: true (gateway.webClient.basePath remounts it)
Capabilities live in Control UI v2. This page focuses on bind modes, security, and web-facing surfaces. The web client also brings browser voice features: Dictate and Voice mode in the message box (see Using the web client).

Webhooks

When hooks.enabled=true, the Gateway also exposes a small webhook endpoint on the same HTTP server. See Gateway configuration → hooks for auth + payloads.

Config (default-on)

The operator console is served by default. Control it via config:

Tailscale access

Keep the Gateway on loopback and let Tailscale Serve proxy it:
Then start the gateway:
Open:
  • https://<magicdns>/ (or your configured console path)

Tailnet bind + token

Then start the gateway (token required for non-loopback binds):
Open:
  • http://<tailscale-ip>:18789/ (or your configured console path)

Public internet (Funnel)

Security notes

  • Gateway auth is required by default (token/password or Tailscale identity headers).
  • Non-loopback binds still require a shared token/password (gateway.auth or env).
  • The wizard generates a gateway token by default (even on loopback).
  • The UI sends connect.params.auth.token or connect.params.auth.password.
  • For non-loopback console deployments, set gateway.controlUi.allowedOrigins explicitly (full origins). Without it, gateway startup is refused by default. This covers the Control UI v2 console.
  • gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true enables Host-header origin fallback mode, but is a dangerous security downgrade.
  • With Serve, Tailscale identity headers can satisfy Control UI/WebSocket auth when gateway.auth.allowTailscale is true (no token/password required). HTTP API endpoints still require token/password. Set gateway.auth.allowTailscale: false to require explicit credentials. See Tailscale and Security. This tokenless flow assumes the gateway host is trusted.
  • gateway.tailscale.mode: "funnel" requires gateway.auth.mode: "password" (shared password).

Building the console

From a source checkout, build the packaged console bundle the gateway serves:
Hosting options (gateway route, standalone server, container, CDN) are in Control UI v2.