@takibeiy/moltbot_cn 2026.1.28 → 2026.2.1-beta.1

package/docs/tts.md

@@ -4,12 +4,13 @@ read_when:
   - Enabling text-to-speech for replies
   - Configuring TTS providers or limits
   - Using /tts commands
+title: "Text-to-Speech"
 ---
 
 # Text-to-speech (TTS)
 
-Moltbot can convert outbound replies into audio using ElevenLabs, OpenAI, or Edge TTS.
-It works anywhere Moltbot can send audio; Telegram gets a round voice-note bubble.
+OpenClaw can convert outbound replies into audio using ElevenLabs, OpenAI, or Edge TTS.
+It works anywhere OpenClaw can send audio; Telegram gets a round voice-note bubble.
 
 ## Supported services
 
@@ -32,10 +33,11 @@ does not publish limits, so assume similar or lower limits. citeturn0searc
 ## Optional keys
 
 If you want OpenAI or ElevenLabs:
+
 - `ELEVENLABS_API_KEY` (or `XI_API_KEY`)
 - `OPENAI_API_KEY`
 
-Edge TTS does **not** require an API key. If no API keys are found, Moltbot defaults
+Edge TTS does **not** require an API key. If no API keys are found, OpenClaw defaults
 to Edge TTS (unless disabled via `messages.tts.edge.enabled=false`).
 
 If multiple providers are configured, the selected provider is used first and the others are fallback options.
@@ -61,7 +63,7 @@ when no OpenAI or ElevenLabs API keys are available.
 
 ## Config
 
-TTS config lives under `messages.tts` in `moltbot.json`.
+TTS config lives under `messages.tts` in `openclaw.json`.
 Full schema is in [Gateway configuration](/gateway/configuration).
 
 ### Minimal config (enable + provider)
@@ -71,9 +73,9 @@ Full schema is in [Gateway configuration](/gateway/configuration).
   messages: {
     tts: {
       auto: "always",
-      provider: "elevenlabs"
-    }
-  }
+      provider: "elevenlabs",
+    },
+  },
 }
 ```
 
@@ -87,12 +89,12 @@ Full schema is in [Gateway configuration](/gateway/configuration).
       provider: "openai",
       summaryModel: "openai/gpt-4.1-mini",
       modelOverrides: {
-        enabled: true
+        enabled: true,
       },
       openai: {
         apiKey: "openai_api_key",
         model: "gpt-4o-mini-tts",
-        voice: "alloy"
+        voice: "alloy",
       },
       elevenlabs: {
         apiKey: "elevenlabs_api_key",
@@ -107,11 +109,11 @@ Full schema is in [Gateway configuration](/gateway/configuration).
           similarityBoost: 0.75,
           style: 0.0,
           useSpeakerBoost: true,
-          speed: 1.0
-        }
-      }
-    }
-  }
+          speed: 1.0,
+        },
+      },
+    },
+  },
 }
 ```
 
@@ -129,10 +131,10 @@ Full schema is in [Gateway configuration](/gateway/configuration).
         lang: "en-US",
         outputFormat: "audio-24khz-48kbitrate-mono-mp3",
         rate: "+10%",
-        pitch: "-5%"
-      }
-    }
-  }
+        pitch: "-5%",
+      },
+    },
+  },
 }
 ```
 
@@ -143,10 +145,10 @@ Full schema is in [Gateway configuration](/gateway/configuration).
   messages: {
     tts: {
       edge: {
-        enabled: false
-      }
-    }
-  }
+        enabled: false,
+      },
+    },
+  },
 }
 ```
 
@@ -159,9 +161,9 @@ Full schema is in [Gateway configuration](/gateway/configuration).
       auto: "always",
       maxTextLength: 4000,
       timeoutMs: 30000,
-      prefsPath: "~/.clawdbot/settings/tts.json"
-    }
-  }
+      prefsPath: "~/.openclaw/settings/tts.json",
+    },
+  },
 }
 ```
 
@@ -171,9 +173,9 @@ Full schema is in [Gateway configuration](/gateway/configuration).
 {
   messages: {
     tts: {
-      auto: "inbound"
-    }
-  }
+      auto: "inbound",
+    },
+  },
 }
 ```
 
@@ -183,9 +185,9 @@ Full schema is in [Gateway configuration](/gateway/configuration).
 {
   messages: {
     tts: {
-      auto: "always"
-    }
-  }
+      auto: "always",
+    },
+  },
 }
 ```
 
@@ -203,7 +205,7 @@ Then run:
 - `enabled`: legacy toggle (doctor migrates this to `auto`).
 - `mode`: `"final"` (default) or `"all"` (includes tool/block replies).
 - `provider`: `"elevenlabs"`, `"openai"`, or `"edge"` (fallback is automatic).
-- If `provider` is **unset**, Moltbot prefers `openai` (if key), then `elevenlabs` (if key),
+- If `provider` is **unset**, OpenClaw prefers `openai` (if key), then `elevenlabs` (if key),
   otherwise `edge`.
 - `summaryModel`: optional cheap model for auto-summary; defaults to `agents.defaults.model.primary`.
   - Accepts `provider/model` or a configured model alias.
@@ -250,6 +252,7 @@ Here you go.
 ```
 
 Available directive keys (when enabled):
+
 - `provider` (`openai` | `elevenlabs` | `edge`)
 - `voice` (OpenAI voice) or `voiceId` (ElevenLabs)
 - `model` (OpenAI TTS model or ElevenLabs model id)
@@ -265,10 +268,10 @@ Disable all model overrides:
   messages: {
     tts: {
       modelOverrides: {
-        enabled: false
-      }
-    }
-  }
+        enabled: false,
+      },
+    },
+  },
 }
 ```
 
@@ -281,20 +284,21 @@ Optional allowlist (disable specific overrides while keeping tags enabled):
       modelOverrides: {
         enabled: true,
         allowProvider: false,
-        allowSeed: false
-      }
-    }
-  }
+        allowSeed: false,
+      },
+    },
+  },
 }
 ```
 
 ## Per-user preferences
 
 Slash commands write local overrides to `prefsPath` (default:
-`~/.clawdbot/settings/tts.json`, override with `CLAWDBOT_TTS_PREFS` or
+`~/.openclaw/settings/tts.json`, override with `OPENCLAW_TTS_PREFS` or
 `messages.tts.prefsPath`).
 
 Stored fields:
+
 - `enabled`
 - `provider`
 - `maxLength` (summary threshold; default 1500 chars)
@@ -314,13 +318,14 @@ These override `messages.tts.*` for that host.
   - Output format values follow Microsoft Speech output formats (including Ogg/WebM Opus). citeturn1search0
   - Telegram `sendVoice` accepts OGG/MP3/M4A; use OpenAI/ElevenLabs if you need
     guaranteed Opus voice notes. citeturn1search1
-  - If the configured Edge output format fails, Moltbot retries with MP3.
+  - If the configured Edge output format fails, OpenClaw retries with MP3.
 
 OpenAI/ElevenLabs formats are fixed; Telegram expects Opus for voice-note UX.
 
 ## Auto-TTS behavior
 
-When enabled, Moltbot:
+When enabled, OpenClaw:
+
 - skips TTS if the reply already contains media or a `MEDIA:` directive.
 - skips very short replies (< 10 chars).
 - summarizes long replies when enabled using `agents.defaults.model.primary` (or `summaryModel`).
@@ -350,7 +355,7 @@ Reply -> TTS enabled?
 There is a single command: `/tts`.
 See [Slash commands](/tools/slash-commands) for enablement details.
 
-Discord note: `/tts` is a built-in Discord command, so Moltbot registers
+Discord note: `/tts` is a built-in Discord command, so OpenClaw registers
 `/voice` as the native command there. Text `/tts ...` still works.
 
 ```
@@ -362,10 +367,11 @@ Discord note: `/tts` is a built-in Discord command, so Moltbot registers
 /tts provider openai
 /tts limit 2000
 /tts summary off
-/tts audio Hello from Moltbot
+/tts audio Hello from OpenClaw
 ```
 
 Notes:
+
 - Commands require an authorized sender (allowlist/owner rules still apply).
 - `commands.text` or native command registration must be enabled.
 - `off|always|inbound|tagged` are per‑session toggles (`/tts on` is an alias for `/tts always`).
@@ -381,6 +387,7 @@ Telegram sends a voice bubble.
 ## Gateway RPC
 
 Gateway methods:
+
 - `tts.status`
 - `tts.enable`
 - `tts.disable`

package/docs/tui.md

@@ -3,27 +3,37 @@ summary: "Terminal UI (TUI): connect to the Gateway from any machine"
 read_when:
   - You want a beginner-friendly walkthrough of the TUI
   - You need the complete list of TUI features, commands, and shortcuts
+title: "TUI"
 ---
+
 # TUI (Terminal UI)
 
 ## Quick start
-1) Start the Gateway.
+
+1. Start the Gateway.
+
 ```bash
-moltbot gateway
+openclaw gateway
 ```
-2) Open the TUI.
+
+2. Open the TUI.
+
 ```bash
-moltbot tui
+openclaw tui
 ```
-3) Type a message and press Enter.
+
+3. Type a message and press Enter.
 
 Remote Gateway:
+
 ```bash
-moltbot tui --url ws://<host>:<port> --token <gateway-token>
+openclaw tui --url ws://<host>:<port> --token <gateway-token>
 ```
+
 Use `--password` if your Gateway uses password auth.
 
 ## What you see
+
 - Header: connection URL, current agent, current session.
 - Chat log: user messages, assistant replies, system notices, tool cards.
 - Status line: connection/run state (connecting, running, streaming, idle, error).
@@ -31,6 +41,7 @@ Use `--password` if your Gateway uses password auth.
 - Input: text editor with autocomplete.
 
 ## Mental model: agents + sessions
+
 - Agents are unique slugs (e.g. `main`, `research`). The Gateway exposes the list.
 - Sessions belong to the current agent.
 - Session keys are stored as `agent:<agentId>:<sessionKey>`.
@@ -42,19 +53,22 @@ Use `--password` if your Gateway uses password auth.
 - The current agent + session are always visible in the footer.
 
 ## Sending + delivery
+
 - Messages are sent to the Gateway; delivery to providers is off by default.
 - Turn delivery on:
   - `/deliver on`
   - or the Settings panel
-  - or start with `moltbot tui --deliver`
+  - or start with `openclaw tui --deliver`
 
 ## Pickers + overlays
+
 - Model picker: list available models and set the session override.
 - Agent picker: choose a different agent.
 - Session picker: shows only sessions for the current agent.
 - Settings: toggle deliver, tool output expansion, and thinking visibility.
 
 ## Keyboard shortcuts
+
 - Enter: send message
 - Esc: abort active run
 - Ctrl+C: clear input (press twice to exit)
@@ -66,7 +80,9 @@ Use `--password` if your Gateway uses password auth.
 - Ctrl+T: toggle thinking visibility (reloads history)
 
 ## Slash commands
+
 Core:
+
 - `/help`
 - `/status`
 - `/agent <id>` (or `/agents`)
@@ -74,6 +90,7 @@ Core:
 - `/model <provider/model>` (or `/models`)
 
 Session controls:
+
 - `/think <off|minimal|low|medium|high>`
 - `/verbose <on|full|off>`
 - `/reasoning <on|off|stream>`
@@ -83,6 +100,7 @@ Session controls:
 - `/deliver <on|off>`
 
 Session lifecycle:
+
 - `/new` or `/reset` (reset the session)
 - `/abort` (abort the active run)
 - `/settings`
@@ -91,26 +109,31 @@ Session lifecycle:
 Other Gateway slash commands (for example, `/context`) are forwarded to the Gateway and shown as system output. See [Slash commands](/tools/slash-commands).
 
 ## Local shell commands
+
 - Prefix a line with `!` to run a local shell command on the TUI host.
 - The TUI prompts once per session to allow local execution; declining keeps `!` disabled for the session.
 - Commands run in a fresh, non-interactive shell in the TUI working directory (no persistent `cd`/env).
 - A lone `!` is sent as a normal message; leading spaces do not trigger local exec.
 
 ## Tool output
+
 - Tool calls show as cards with args + results.
 - Ctrl+O toggles between collapsed/expanded views.
 - While tools run, partial updates stream into the same card.
 
 ## History + streaming
+
 - On connect, the TUI loads the latest history (default 200 messages).
 - Streaming responses update in place until finalized.
 - The TUI also listens to agent tool events for richer tool cards.
 
 ## Connection details
+
 - The TUI registers with the Gateway as `mode: "tui"`.
 - Reconnects show a system message; event gaps are surfaced in the log.
 
 ## Options
+
 - `--url <url>`: Gateway WebSocket URL (defaults to config or `ws://127.0.0.1:<port>`)
 - `--token <token>`: Gateway token (if required)
 - `--password <password>`: Gateway password (if required)
@@ -122,13 +145,15 @@ Other Gateway slash commands (for example, `/context`) are forwarded to the Gate
 ## Troubleshooting
 
 No output after sending a message:
+
 - Run `/status` in the TUI to confirm the Gateway is connected and idle/busy.
-- Check the Gateway logs: `moltbot logs --follow`.
-- Confirm the agent can run: `moltbot status` and `moltbot models status`.
+- Check the Gateway logs: `openclaw logs --follow`.
+- Confirm the agent can run: `openclaw status` and `openclaw models status`.
 - If you expect messages in a chat channel, enable delivery (`/deliver on` or `--deliver`).
 - `--history-limit <n>`: History entries to load (default 200)
 
 ## Troubleshooting
+
 - `disconnected`: ensure the Gateway is running and your `--url/--token/--password` are correct.
-- No agents in picker: check `moltbot agents list` and your routing config.
+- No agents in picker: check `openclaw agents list` and your routing config.
 - Empty session picker: you might be in global scope or have no sessions yet.

package/docs/vps.md

@@ -1,9 +1,11 @@
 ---
-summary: "VPS hosting hub for Moltbot (Oracle/Fly/Hetzner/GCP/exe.dev)"
+summary: "VPS hosting hub for OpenClaw (Oracle/Fly/Hetzner/GCP/exe.dev)"
 read_when:
   - You want to run the Gateway in the cloud
   - You need a quick map of VPS/hosting guides
+title: "VPS Hosting"
 ---
+
 # VPS hosting
 
 This hub links to the supported VPS/hosting guides and explains how cloud

package/docs/web/control-ui.md

@@ -3,13 +3,15 @@ summary: "Browser-based control UI for the Gateway (chat, nodes, config)"
 read_when:
   - You want to operate the Gateway from a browser
   - You want Tailnet access without SSH tunnels
+title: "Control UI"
 ---
+
 # Control UI (browser)
 
 The Control UI is a small **Vite + Lit** single-page app served by the Gateway:
 
 - default: `http://<host>:18789/`
-- optional prefix: set `gateway.controlUi.basePath` (e.g. `/moltbot`)
+- optional prefix: set `gateway.controlUi.basePath` (e.g. `/openclaw`)
 
 It speaks **directly to the Gateway WebSocket** on the same port.
 
@@ -19,15 +21,17 @@ If the Gateway is running on the same computer, open:
 
 - http://127.0.0.1:18789/ (or http://localhost:18789/)
 
-If the page fails to load, start the Gateway first: `moltbot gateway`.
+If the page fails to load, start the Gateway first: `openclaw gateway`.
 
 Auth is supplied during the WebSocket handshake via:
+
 - `connect.params.auth.token`
 - `connect.params.auth.password`
-The dashboard settings panel lets you store a token; passwords are not persisted.
-The onboarding wizard generates a gateway token by default, so paste it here on first connect.
+  The dashboard settings panel lets you store a token; passwords are not persisted.
+  The onboarding wizard generates a gateway token by default, so paste it here on first connect.
 
 ## What it can do (today)
+
 - Chat with the model via Gateway WS (`chat.history`, `chat.send`, `chat.abort`, `chat.inject`)
 - Stream tool calls + live tool output cards in Chat (agent events)
 - Channels: WhatsApp/Telegram/Discord/Slack + plugin channels (Mattermost, etc.) status + QR login + per-channel config (`channels.status`, `web.login.*`, `config.patch`)
@@ -37,7 +41,7 @@ The onboarding wizard generates a gateway token by default, so paste it here on
 - Skills: status, enable/disable, install, API key updates (`skills.*`)
 - Nodes: list + caps (`node.list`)
 - Exec approvals: edit gateway or node allowlists + ask policy for `exec host=gateway/node` (`exec.approvals.*`)
-- Config: view/edit `~/.clawdbot/moltbot.json` (`config.get`, `config.set`)
+- Config: view/edit `~/.openclaw/openclaw.json` (`config.get`, `config.set`)
 - Config: apply + restart with validation (`config.apply`) and wake the last active session
 - Config writes include a base-hash guard to prevent clobbering concurrent edits
 - Config schema + form rendering (`config.schema`, including plugin + channel schemas); Raw JSON editor remains available
@@ -62,14 +66,15 @@ The onboarding wizard generates a gateway token by default, so paste it here on
 Keep the Gateway on loopback and let Tailscale Serve proxy it with HTTPS:
 
 ```bash
-moltbot gateway --tailscale serve
+openclaw gateway --tailscale serve
 ```
 
 Open:
+
 - `https://<magicdns>/` (or your configured `gateway.controlUi.basePath`)
 
 By default, Serve requests can authenticate via Tailscale identity headers
-(`tailscale-user-login`) when `gateway.auth.allowTailscale` is `true`. Moltbot
+(`tailscale-user-login`) when `gateway.auth.allowTailscale` is `true`. OpenClaw
 verifies the identity by resolving the `x-forwarded-for` address with
 `tailscale whois` and matching it to the header, and only accepts these when the
 request hits loopback with Tailscale’s `x-forwarded-*` headers. Set
@@ -79,10 +84,11 @@ if you want to require a token/password even for Serve traffic.
 ### Bind to tailnet + token
 
 ```bash
-moltbot gateway --bind tailnet --token "$(openssl rand -hex 32)"
+openclaw gateway --bind tailnet --token "$(openssl rand -hex 32)"
 ```
 
 Then open:
+
 - `http://<tailscale-ip>:18789/` (or your configured `gateway.controlUi.basePath`)
 
 Paste the token into the UI settings (sent as `connect.params.auth.token`).
@@ -91,9 +97,10 @@ Paste the token into the UI settings (sent as `connect.params.auth.token`).
 
 If you open the dashboard over plain HTTP (`http://<lan-ip>` or `http://<tailscale-ip>`),
 the browser runs in a **non-secure context** and blocks WebCrypto. By default,
-Moltbot **blocks** Control UI connections without device identity.
+OpenClaw **blocks** Control UI connections without device identity.
 
 **Recommended fix:** use HTTPS (Tailscale Serve) or open the UI locally:
+
 - `https://<magicdns>/` (Serve)
 - `http://127.0.0.1:18789/` (on the gateway host)
 
@@ -104,8 +111,8 @@ Moltbot **blocks** Control UI connections without device identity.
   gateway: {
     controlUi: { allowInsecureAuth: true },
     bind: "tailnet",
-    auth: { mode: "token", token: "replace-me" }
-  }
+    auth: { mode: "token", token: "replace-me" },
+  },
 }
 ```
 
@@ -125,7 +132,7 @@ pnpm ui:build # auto-installs UI deps on first run
 Optional absolute base (when you want fixed asset URLs):
 
 ```bash
-CLAWDBOT_CONTROL_UI_BASE_PATH=/moltbot/ pnpm ui:build
+OPENCLAW_CONTROL_UI_BASE_PATH=/openclaw/ pnpm ui:build
 ```
 
 For local development (separate dev server):
@@ -142,8 +149,8 @@ The Control UI is static files; the WebSocket target is configurable and can be
 different from the HTTP origin. This is handy when you want the Vite dev server
 locally but the Gateway runs elsewhere.
 
-1) Start the UI dev server: `pnpm ui:dev`
-2) Open a URL like:
+1. Start the UI dev server: `pnpm ui:dev`
+2. Open a URL like:
 
 ```text
 http://localhost:5173/?gatewayUrl=ws://<gateway-host>:18789
@@ -156,6 +163,7 @@ http://localhost:5173/?gatewayUrl=wss://<gateway-host>:18789&token=<gateway-toke
 ```
 
 Notes:
+
 - `gatewayUrl` is stored in localStorage after load and removed from the URL.
 - `token` is stored in localStorage; `password` is kept in memory only.
 - Use `wss://` when the Gateway is behind TLS (Tailscale Serve, HTTPS proxy, etc.).

package/docs/web/dashboard.md

@@ -2,16 +2,20 @@
 summary: "Gateway dashboard (Control UI) access and auth"
 read_when:
   - Changing dashboard authentication or exposure modes
+title: "Dashboard"
 ---
+
 # Dashboard (Control UI)
 
 The Gateway dashboard is the browser Control UI served at `/` by default
 (override with `gateway.controlUi.basePath`).
 
 Quick open (local Gateway):
+
 - http://127.0.0.1:18789/ (or http://localhost:18789/)
 
 Key references:
+
 - [Control UI](/web/control-ui) for usage and UI capabilities.
 - [Tailscale](/gateway/tailscale) for Serve/Funnel automation.
 - [Web surfaces](/web) for bind modes and security notes.
@@ -26,17 +30,17 @@ Prefer localhost, Tailscale Serve, or an SSH tunnel.
 ## Fast path (recommended)
 
 - After onboarding, the CLI now auto-opens the dashboard with your token and prints the same tokenized link.
-- Re-open anytime: `moltbot dashboard` (copies link, opens browser if possible, shows SSH hint if headless).
+- Re-open anytime: `openclaw dashboard` (copies link, opens browser if possible, shows SSH hint if headless).
 - The token stays local (query param only); the UI strips it after first load and saves it in localStorage.
 
 ## Token basics (local vs remote)
 
-- **Localhost**: open `http://127.0.0.1:18789/`. If you see “unauthorized,” run `moltbot dashboard` and use the tokenized link (`?token=...`).
-- **Token source**: `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`); the UI stores it after first load.
+- **Localhost**: open `http://127.0.0.1:18789/`. If you see “unauthorized,” run `openclaw dashboard` and use the tokenized link (`?token=...`).
+- **Token source**: `gateway.auth.token` (or `OPENCLAW_GATEWAY_TOKEN`); the UI stores it after first load.
 - **Not localhost**: use Tailscale Serve (tokenless if `gateway.auth.allowTailscale: true`), tailnet bind with a token, or an SSH tunnel. See [Web surfaces](/web).
 
 ## If you see “unauthorized” / 1008
 
-- Run `moltbot dashboard` to get a fresh tokenized link.
-- Ensure the gateway is reachable (local: `moltbot status`; remote: SSH tunnel `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/?token=...`).
-- In the dashboard settings, paste the same token you configured in `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`).
+- Run `openclaw dashboard` to get a fresh tokenized link.
+- 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/?token=...`).
+- In the dashboard settings, paste the same token you configured in `gateway.auth.token` (or `OPENCLAW_GATEWAY_TOKEN`).

package/docs/web/index.md

@@ -3,13 +3,15 @@ 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
+title: "Web"
 ---
+
 # Web (Gateway)
 
 The Gateway serves a small **browser Control UI** (Vite + Lit) from the same port as the Gateway WebSocket:
 
 - default: `http://<host>:18789/`
-- optional prefix: set `gateway.controlUi.basePath` (e.g. `/moltbot`)
+- optional prefix: set `gateway.controlUi.basePath` (e.g. `/openclaw`)
 
 Capabilities live in [Control UI](/web/control-ui).
 This page focuses on bind modes, security, and web-facing surfaces.
@@ -27,8 +29,8 @@ You can control it via config:
 ```json5
 {
   gateway: {
-    controlUi: { enabled: true, basePath: "/moltbot" } // basePath optional
-  }
+    controlUi: { enabled: true, basePath: "/openclaw" }, // basePath optional
+  },
 }
 ```
 
@@ -42,18 +44,19 @@ Keep the Gateway on loopback and let Tailscale Serve proxy it:
 {
   gateway: {
     bind: "loopback",
-    tailscale: { mode: "serve" }
-  }
+    tailscale: { mode: "serve" },
+  },
 }
 ```
 
 Then start the gateway:
 
 ```bash
-moltbot gateway
+openclaw gateway
 ```
 
 Open:
+
 - `https://<magicdns>/` (or your configured `gateway.controlUi.basePath`)
 
 ### Tailnet bind + token
@@ -63,18 +66,19 @@ Open:
   gateway: {
     bind: "tailnet",
     controlUi: { enabled: true },
-    auth: { mode: "token", token: "your-token" }
-  }
+    auth: { mode: "token", token: "your-token" },
+  },
 }
 ```
 
 Then start the gateway (token required for non-loopback binds):
 
 ```bash
-moltbot gateway
+openclaw gateway
 ```
 
 Open:
+
 - `http://<tailscale-ip>:18789/` (or your configured `gateway.controlUi.basePath`)
 
 ### Public internet (Funnel)
@@ -84,8 +88,8 @@ Open:
   gateway: {
     bind: "loopback",
     tailscale: { mode: "funnel" },
-    auth: { mode: "password" } // or CLAWDBOT_GATEWAY_PASSWORD
-  }
+    auth: { mode: "password" }, // or OPENCLAW_GATEWAY_PASSWORD
+  },
 }
 ```