Files
openclaw/docs/web.md

116 lines
2.8 KiB
Markdown
Raw Normal View History

2025-12-18 22:40:46 +00:00
---
summary: "Gateway web surfaces: Control UI, bind modes, and security"
read_when:
- You want to access the Gateway over Tailscale
- You want the browser Control UI and config editing
---
# Web (Gateway)
The Gateway serves a small **browser Control UI** (Vite + Lit) from the same port as the Gateway WebSocket:
- default: `http://<host>:18789/`
2026-01-04 14:32:47 +00:00
- optional prefix: set `gateway.controlUi.basePath` (e.g. `/clawdbot`)
2025-12-18 22:40:46 +00:00
The UI talks directly to the Gateway WS and supports:
- Chat (`chat.history`, `chat.send`, `chat.abort`)
- Chat tool cards (agent tool events)
2025-12-21 00:34:39 +00:00
- Connections (provider status, WhatsApp QR, Telegram config)
- Instances (`system-presence`)
- Sessions (`sessions.list`, `sessions.patch`)
- Cron (`cron.*`)
- Skills (`skills.status`, `skills.update`, `skills.install`)
2025-12-18 22:40:46 +00:00
- Nodes (`node.list`, `node.describe`, `node.invoke`)
2026-01-04 14:32:47 +00:00
- Config (`config.get`, `config.set`) for `~/.clawdbot/clawdbot.json`
2025-12-21 00:34:39 +00:00
- Debug (status/health/models snapshots + manual calls)
2025-12-18 22:40:46 +00:00
2025-12-24 14:32:55 +00:00
## Webhooks
2026-01-06 18:25:52 +00:00
When `hooks.enabled=true`, the Gateway also exposes a small webhook endpoint on the same HTTP server.
2026-01-06 18:59:06 +01:00
See [`docs/configuration.md`](https://docs.clawd.bot/configuration) → `hooks` for auth + payloads.
2025-12-24 14:32:55 +00:00
2025-12-18 22:40:46 +00:00
## Config (default-on)
The Control UI is **enabled by default** when assets are present (`dist/control-ui`).
You can control it via config:
```json5
{
gateway: {
2026-01-04 14:32:47 +00:00
controlUi: { enabled: true, basePath: "/clawdbot" } // basePath optional
2025-12-18 22:40:46 +00:00
}
}
```
2025-12-21 00:34:39 +00:00
## Tailscale access
2025-12-18 22:40:46 +00:00
2025-12-21 00:34:39 +00:00
### Integrated Serve (recommended)
2025-12-18 22:40:46 +00:00
2025-12-21 00:34:39 +00:00
Keep the Gateway on loopback and let Tailscale Serve proxy it:
```json5
{
gateway: {
bind: "loopback",
tailscale: { mode: "serve" }
}
}
```
Then start the gateway:
```bash
2026-01-04 14:32:47 +00:00
clawdbot gateway
2025-12-21 00:34:39 +00:00
```
Open:
- `https://<magicdns>/` (or your configured `gateway.controlUi.basePath`)
2025-12-21 00:34:39 +00:00
### Tailnet bind + token (legacy)
2025-12-18 22:40:46 +00:00
```json5
{
gateway: {
bind: "tailnet",
controlUi: { enabled: true }
}
}
```
Then start the gateway (token required for non-loopback binds):
```bash
2026-01-04 14:32:47 +00:00
export CLAWDBOT_GATEWAY_TOKEN="…your token…"
clawdbot gateway
2025-12-18 22:40:46 +00:00
```
Open:
- `http://<tailscale-ip>:18789/` (or your configured `gateway.controlUi.basePath`)
2025-12-18 22:40:46 +00:00
2025-12-21 00:34:39 +00:00
### Public internet (Funnel)
2025-12-18 22:40:46 +00:00
2025-12-21 00:34:39 +00:00
```json5
{
gateway: {
bind: "loopback",
tailscale: { mode: "funnel" },
2026-01-04 14:32:47 +00:00
auth: { mode: "password" } // or CLAWDBOT_GATEWAY_PASSWORD
2025-12-21 00:34:39 +00:00
}
}
2025-12-18 22:40:46 +00:00
```
## Security notes
2026-01-04 14:32:47 +00:00
- Binding the Gateway to a non-loopback address **requires** auth (`CLAWDBOT_GATEWAY_TOKEN` or `gateway.auth`).
2025-12-21 00:34:39 +00:00
- The UI sends `connect.params.auth.token` or `connect.params.auth.password`.
- Use `gateway.auth.allowTailscale: false` to require explicit credentials even in Serve mode.
- `gateway.tailscale.mode: "funnel"` requires `gateway.auth.mode: "password"` (shared password).
2025-12-18 22:40:46 +00:00
## Building the UI
The Gateway serves static files from `dist/control-ui`. Build them with:
```bash
bun run ui:install
bun run ui:build
2025-12-18 22:40:46 +00:00
```