@takibeiy/moltbot_cn 2026.2.1 → 2026.2.3

package/docs/gateway/troubleshooting.md

@@ -1,11 +1,13 @@
 ---
-summary: "Quick troubleshooting guide for common Moltbot failures"
+summary: "Quick troubleshooting guide for common OpenClaw failures"
 read_when:
   - Investigating runtime issues or failures
+title: "Troubleshooting"
 ---
+
 # Troubleshooting 🔧
 
-When Moltbot misbehaves, here's how to fix it.
+When OpenClaw misbehaves, here's how to fix it.
 
 Start with the FAQ’s [First 60 seconds](/help/faq#first-60-seconds-if-somethings-broken) if you just want a quick triage recipe. This page goes deeper on runtime failures and diagnostics.
 
@@ -15,17 +17,17 @@ Provider-specific shortcuts: [/channels/troubleshooting](/channels/troubleshooti
 
 Quick triage commands (in order):
 
-| Command | What it tells you | When to use it |
-|---|---|---|
-| `moltbot status` | Local summary: OS + update, gateway reachability/mode, service, agents/sessions, provider config state | First check, quick overview |
-| `moltbot status --all` | Full local diagnosis (read-only, pasteable, safe-ish) incl. log tail | When you need to share a debug report |
-| `moltbot status --deep` | Runs gateway health checks (incl. provider probes; requires reachable gateway) | When “configured” doesn’t mean “working” |
-| `moltbot gateway probe` | Gateway discovery + reachability (local + remote targets) | When you suspect you’re probing the wrong gateway |
-| `moltbot channels status --probe` | Asks the running gateway for channel status (and optionally probes) | When gateway is reachable but channels misbehave |
-| `moltbot gateway status` | Supervisor state (launchd/systemd/schtasks), runtime PID/exit, last gateway error | When the service “looks loaded” but nothing runs |
-| `moltbot logs --follow` | Live logs (best signal for runtime issues) | When you need the actual failure reason |
+| Command                            | What it tells you                                                                                      | When to use it                                    |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------- |
+| `openclaw status`                  | Local summary: OS + update, gateway reachability/mode, service, agents/sessions, provider config state | First check, quick overview                       |
+| `openclaw status --all`            | Full local diagnosis (read-only, pasteable, safe-ish) incl. log tail                                   | When you need to share a debug report             |
+| `openclaw status --deep`           | Runs gateway health checks (incl. provider probes; requires reachable gateway)                         | When “configured” doesn’t mean “working”          |
+| `openclaw gateway probe`           | Gateway discovery + reachability (local + remote targets)                                              | When you suspect you’re probing the wrong gateway |
+| `openclaw channels status --probe` | Asks the running gateway for channel status (and optionally probes)                                    | When gateway is reachable but channels misbehave  |
+| `openclaw gateway status`          | Supervisor state (launchd/systemd/schtasks), runtime PID/exit, last gateway error                      | When the service “looks loaded” but nothing runs  |
+| `openclaw logs --follow`           | Live logs (best signal for runtime issues)                                                             | When you need the actual failure reason           |
 
-**Sharing output:** prefer `moltbot status --all` (it redacts tokens). If you paste `moltbot status`, consider setting `CLAWDBOT_SHOW_SECRETS=0` first (token previews).
+**Sharing output:** prefer `openclaw status --all` (it redacts tokens). If you paste `openclaw status`, consider setting `OPENCLAW_SHOW_SECRETS=0` first (token previews).
 
 See also: [Health checks](/gateway/health) and [Logging](/logging).
 
@@ -37,16 +39,18 @@ This means the **agent’s auth store is empty** or missing Anthropic credential
 Auth is **per agent**, so a new agent won’t inherit the main agent’s keys.
 
 Fix options:
+
 - Re-run onboarding and choose **Anthropic** for that agent.
 - Or paste a setup-token on the **gateway host**:
   ```bash
-  moltbot models auth setup-token --provider anthropic
+  openclaw models auth setup-token --provider anthropic
   ```
 - Or copy `auth-profiles.json` from the main agent dir to the new agent dir.
 
 Verify:
+
 ```bash
-moltbot models status
+openclaw models status
 ```
 
 ### OAuth token refresh failed (Anthropic Claude subscription)
@@ -59,15 +63,15 @@ switch to a **Claude Code setup-token** and paste it on the **gateway host**.
 
 ```bash
 # Run on the gateway host (paste the setup-token)
-moltbot models auth setup-token --provider anthropic
-moltbot models status
+openclaw models auth setup-token --provider anthropic
+openclaw models status
 ```
 
 If you generated the token elsewhere:
 
 ```bash
-moltbot models auth paste-token --provider anthropic
-moltbot models status
+openclaw models auth paste-token --provider anthropic
+openclaw models status
 ```
 
 More detail: [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth).
@@ -79,6 +83,7 @@ If you open the dashboard over plain HTTP (e.g. `http://<lan-ip>:18789/` or
 blocks WebCrypto, so device identity can’t be generated.
 
 **Fix:**
+
 - Prefer HTTPS via [Tailscale Serve](/gateway/tailscale).
 - Or open locally on the gateway host: `http://127.0.0.1:18789/`.
 - If you must stay on HTTP, enable `gateway.controlUi.allowInsecureAuth: true` and
@@ -96,21 +101,24 @@ If the gateway service is installed but the process exits immediately, the servi
 can appear “loaded” while nothing is running.
 
 **Check:**
+
 ```bash
-moltbot gateway status
-moltbot doctor
+openclaw gateway status
+openclaw doctor
 ```
 
 Doctor/service will show runtime state (PID/last exit) and log hints.
 
 **Logs:**
-- Preferred: `moltbot logs --follow`
-- File logs (always): `/tmp/moltbot/moltbot-YYYY-MM-DD.log` (or your configured `logging.file`)
-- macOS LaunchAgent (if installed): `$CLAWDBOT_STATE_DIR/logs/gateway.log` and `gateway.err.log`
-- Linux systemd (if installed): `journalctl --user -u moltbot-gateway[-<profile>].service -n 200 --no-pager`
-- Windows: `schtasks /Query /TN "Moltbot Gateway (<profile>)" /V /FO LIST`
+
+- Preferred: `openclaw logs --follow`
+- File logs (always): `/tmp/openclaw/openclaw-YYYY-MM-DD.log` (or your configured `logging.file`)
+- macOS LaunchAgent (if installed): `$OPENCLAW_STATE_DIR/logs/gateway.log` and `gateway.err.log`
+- Linux systemd (if installed): `journalctl --user -u openclaw-gateway[-<profile>].service -n 200 --no-pager`
+- Windows: `schtasks /Query /TN "OpenClaw Gateway (<profile>)" /V /FO LIST`
 
 **Enable more logging:**
+
 - Bump file log detail (persisted JSONL):
   ```json
   { "logging": { "level": "debug" } }
@@ -129,44 +137,47 @@ This means the config exists but `gateway.mode` is unset (or not `local`), so th
 Gateway refuses to start.
 
 **Fix (recommended):**
+
 - Run the wizard and set the Gateway run mode to **Local**:
   ```bash
-  moltbot configure
+  openclaw configure
   ```
 - Or set it directly:
   ```bash
-  moltbot config set gateway.mode local
+  openclaw config set gateway.mode local
   ```
 
 **If you meant to run a remote Gateway instead:**
+
 - Set a remote URL and keep `gateway.mode=remote`:
   ```bash
-  moltbot config set gateway.mode remote
-  moltbot config set gateway.remote.url "wss://gateway.example.com"
+  openclaw config set gateway.mode remote
+  openclaw config set gateway.remote.url "wss://gateway.example.com"
   ```
 
 **Ad-hoc/dev only:** pass `--allow-unconfigured` to start the gateway without
 `gateway.mode=local`.
 
-**No config file yet?** Run `moltbot setup` to create a starter config, then rerun
+**No config file yet?** Run `openclaw setup` to create a starter config, then rerun
 the gateway.
 
 ### Service Environment (PATH + runtime)
 
 The gateway service runs with a **minimal PATH** to avoid shell/manager cruft:
+
 - macOS: `/opt/homebrew/bin`, `/usr/local/bin`, `/usr/bin`, `/bin`
 - Linux: `/usr/local/bin`, `/usr/bin`, `/bin`
 
 This intentionally excludes version managers (nvm/fnm/volta/asdf) and package
 managers (pnpm/npm) because the service does not load your shell init. Runtime
-variables like `DISPLAY` should live in `~/.clawdbot/.env` (loaded early by the
+variables like `DISPLAY` should live in `~/.openclaw/.env` (loaded early by the
 gateway).
 Exec runs on `host=gateway` merge your login-shell `PATH` into the exec environment,
 so missing tools usually mean your shell init isn’t exporting them (or set
 `tools.exec.pathPrepend`). See [/tools/exec](/tools/exec).
 
 WhatsApp + Telegram channels require **Node**; Bun is unsupported. If your
-service was installed with Bun or a version-managed Node path, run `moltbot doctor`
+service was installed with Bun or a version-managed Node path, run `openclaw doctor`
 to migrate to a system Node install.
 
 ### Skill missing API key in sandbox
@@ -176,9 +187,10 @@ to migrate to a system Node install.
 **Why:** sandboxed exec runs inside Docker and does **not** inherit host `process.env`.
 
 **Fix:**
+
 - set `agents.defaults.sandbox.docker.env` (or per-agent `agents.list[].sandbox.docker.env`)
 - or bake the key into your custom sandbox image
-- then run `moltbot sandbox recreate --agent <id>` (or `--all`)
+- then run `openclaw sandbox recreate --agent <id>` (or `--all`)
 
 ### Service Running but Port Not Listening
 
@@ -186,37 +198,44 @@ If the service reports **running** but nothing is listening on the gateway port,
 the Gateway likely refused to bind.
 
 **What "running" means here**
+
 - `Runtime: running` means your supervisor (launchd/systemd/schtasks) thinks the process is alive.
 - `RPC probe` means the CLI could actually connect to the gateway WebSocket and call `status`.
 - Always trust `Probe target:` + `Config (service):` as the “what did we actually try?” lines.
 
 **Check:**
-- `gateway.mode` must be `local` for `moltbot gateway` and the service.
-- If you set `gateway.mode=remote`, the **CLI defaults** to a remote URL. The service can still be running locally, but your CLI may be probing the wrong place. Use `moltbot gateway status` to see the service’s resolved port + probe target (or pass `--url`).
-- `moltbot gateway status` and `moltbot doctor` surface the **last gateway error** from logs when the service looks running but the port is closed.
+
+- `gateway.mode` must be `local` for `openclaw gateway` and the service.
+- If you set `gateway.mode=remote`, the **CLI defaults** to a remote URL. The service can still be running locally, but your CLI may be probing the wrong place. Use `openclaw gateway status` to see the service’s resolved port + probe target (or pass `--url`).
+- `openclaw gateway status` and `openclaw doctor` surface the **last gateway error** from logs when the service looks running but the port is closed.
 - Non-loopback binds (`lan`/`tailnet`/`custom`, or `auto` when loopback is unavailable) require auth:
-  `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`).
+  `gateway.auth.token` (or `OPENCLAW_GATEWAY_TOKEN`).
 - `gateway.remote.token` is for remote CLI calls only; it does **not** enable local auth.
 - `gateway.token` is ignored; use `gateway.auth.token`.
 
-**If `moltbot gateway status` shows a config mismatch**
+**If `openclaw gateway status` shows a config mismatch**
+
 - `Config (cli): ...` and `Config (service): ...` should normally match.
 - If they don’t, you’re almost certainly editing one config while the service is running another.
-- Fix: rerun `moltbot gateway install --force` from the same `--profile` / `CLAWDBOT_STATE_DIR` you want the service to use.
+- Fix: rerun `openclaw gateway install --force` from the same `--profile` / `OPENCLAW_STATE_DIR` you want the service to use.
+
+**If `openclaw gateway status` reports service config issues**
 
-**If `moltbot gateway status` reports service config issues**
 - The supervisor config (launchd/systemd/schtasks) is missing current defaults.
-- Fix: run `moltbot doctor` to update it (or `moltbot gateway install --force` for a full rewrite).
+- Fix: run `openclaw doctor` to update it (or `openclaw gateway install --force` for a full rewrite).
 
 **If `Last gateway error:` mentions “refusing to bind … without auth”**
+
 - You set `gateway.bind` to a non-loopback mode (`lan`/`tailnet`/`custom`, or `auto` when loopback is unavailable) but didn’t configure auth.
-- Fix: set `gateway.auth.mode` + `gateway.auth.token` (or export `CLAWDBOT_GATEWAY_TOKEN`) and restart the service.
+- Fix: set `gateway.auth.mode` + `gateway.auth.token` (or export `OPENCLAW_GATEWAY_TOKEN`) and restart the service.
+
+**If `openclaw gateway status` says `bind=tailnet` but no tailnet interface was found**
 
-**If `moltbot gateway status` says `bind=tailnet` but no tailnet interface was found**
 - The gateway tried to bind to a Tailscale IP (100.64.0.0/10) but none were detected on the host.
 - Fix: bring up Tailscale on that machine (or change `gateway.bind` to `loopback`/`lan`).
 
 **If `Probe note:` says the probe uses loopback**
+
 - That’s expected for `bind=lan`: the gateway listens on `0.0.0.0` (all interfaces), and loopback should still connect locally.
 - For remote clients, use a real LAN IP (not `0.0.0.0`) plus the port, and ensure auth is configured.
 
@@ -225,8 +244,9 @@ the Gateway likely refused to bind.
 This means something is already listening on the gateway port.
 
 **Check:**
+
 ```bash
-moltbot gateway status
+openclaw gateway status
 ```
 
 It will show the listener(s) and likely causes (gateway already running, SSH tunnel).
@@ -234,7 +254,7 @@ If needed, stop the service or pick a different port.
 
 ### Extra Workspace Folders Detected
 
-If you upgraded from older installs, you might still have `~/moltbot` on disk.
+If you upgraded from older installs, you might still have `~/openclaw` on disk.
 Multiple workspace directories can cause confusing auth or state drift because
 only one workspace is active.
 
@@ -243,7 +263,7 @@ only one workspace is active.
 
 ### Main chat running in a sandbox workspace
 
-Symptoms: `pwd` or file tools show `~/.clawdbot/sandboxes/...` even though you
+Symptoms: `pwd` or file tools show `~/.openclaw/sandboxes/...` even though you
 expected the host workspace.
 
 **Why:** `agents.defaults.sandbox.mode: "non-main"` keys off `session.mainKey` (default `"main"`).
@@ -251,6 +271,7 @@ Group/channel sessions use their own keys, so they are treated as non-main and
 get sandbox workspaces.
 
 **Fix options:**
+
 - If you want host workspaces for an agent: set `agents.list[].sandbox.mode: "off"`.
 - If you want host workspace access inside sandbox: set `workspaceAccess: "rw"` for that agent.
 
@@ -259,6 +280,7 @@ get sandbox workspaces.
 The agent was interrupted mid-response.
 
 **Causes:**
+
 - User sent `stop`, `abort`, `esc`, `wait`, or `exit`
 - Timeout exceeded
 - Process crashed
@@ -267,14 +289,15 @@ The agent was interrupted mid-response.
 
 ### "Agent failed before reply: Unknown model: anthropic/claude-haiku-3-5"
 
-Moltbot intentionally rejects **older/insecure models** (especially those more
+OpenClaw intentionally rejects **older/insecure models** (especially those more
 vulnerable to prompt injection). If you see this error, the model name is no
 longer supported.
 
 **Fix:**
+
 - Pick a **latest** model for the provider and update your config or model alias.
-- If you’re unsure which models are available, run `moltbot models list` or
-  `moltbot models scan` and choose a supported one.
+- If you’re unsure which models are available, run `openclaw models list` or
+  `openclaw models scan` and choose a supported one.
 - Check gateway logs for the detailed failure reason.
 
 See also: [Models CLI](/cli/models) and [Model providers](/concepts/model-providers).
@@ -282,24 +305,28 @@ See also: [Models CLI](/cli/models) and [Model providers](/concepts/model-provid
 ### Messages Not Triggering
 
 **Check 1:** Is the sender allowlisted?
+
 ```bash
-moltbot status
+openclaw status
 ```
+
 Look for `AllowFrom: ...` in the output.
 
 **Check 2:** For group chats, is mention required?
+
 ```bash
 # The message must match mentionPatterns or explicit mentions; defaults live in channel groups/guilds.
 # Multi-agent: `agents.list[].groupChat.mentionPatterns` overrides global patterns.
 grep -n "agents\\|groupChat\\|mentionPatterns\\|channels\\.whatsapp\\.groups\\|channels\\.telegram\\.groups\\|channels\\.imessage\\.groups\\|channels\\.discord\\.guilds" \
-  "${CLAWDBOT_CONFIG_PATH:-$HOME/.clawdbot/moltbot.json}"
+  "${OPENCLAW_CONFIG_PATH:-$HOME/.openclaw/openclaw.json}"
 ```
 
 **Check 3:** Check the logs
+
 ```bash
-moltbot logs --follow
+openclaw logs --follow
 # or if you want quick filters:
-tail -f "$(ls -t /tmp/moltbot/moltbot-*.log | head -1)" | grep "blocked\\|skip\\|unauthorized"
+tail -f "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)" | grep "blocked\\|skip\\|unauthorized"
 ```
 
 ### Pairing Code Not Arriving
@@ -307,15 +334,17 @@ tail -f "$(ls -t /tmp/moltbot/moltbot-*.log | head -1)" | grep "blocked\\|skip\\
 If `dmPolicy` is `pairing`, unknown senders should receive a code and their message is ignored until approved.
 
 **Check 1:** Is a pending request already waiting?
+
 ```bash
-moltbot pairing list <channel>
+openclaw pairing list <channel>
 ```
 
 Pending DM pairing requests are capped at **3 per channel** by default. If the list is full, new requests won’t generate a code until one is approved or expires.
 
 **Check 2:** Did the request get created but no reply was sent?
+
 ```bash
-moltbot logs --follow | grep "pairing request"
+openclaw logs --follow | grep "pairing request"
 ```
 
 **Check 3:** Confirm `dmPolicy` isn’t `open`/`allowlist` for that channel.
@@ -325,24 +354,27 @@ moltbot logs --follow | grep "pairing request"
 Known issue: When you send an image with ONLY a mention (no other text), WhatsApp sometimes doesn't include the mention metadata.
 
 **Workaround:** Add some text with the mention:
-- ❌ `@clawd` + image
-- ✅ `@clawd check this` + image
+
+- ❌ `@openclaw` + image
+- ✅ `@openclaw check this` + image
 
 ### Session Not Resuming
 
 **Check 1:** Is the session file there?
+
 ```bash
-ls -la ~/.clawdbot/agents/<agentId>/sessions/
+ls -la ~/.openclaw/agents/<agentId>/sessions/
 ```
 
 **Check 2:** Is the reset window too short?
+
 ```json
 {
   "session": {
     "reset": {
       "mode": "daily",
       "atHour": 4,
-      "idleMinutes": 10080  // 7 days
+      "idleMinutes": 10080 // 7 days
     }
   }
 }
@@ -357,7 +389,7 @@ Default timeout is 30 minutes. For long tasks:
 ```json
 {
   "reply": {
-    "timeoutSeconds": 3600  // 1 hour
+    "timeoutSeconds": 3600 // 1 hour
   }
 }
 ```
@@ -368,54 +400,58 @@ Or use the `process` tool to background long commands.
 
 ```bash
 # Check local status (creds, sessions, queued events)
-moltbot status
+openclaw status
 # Probe the running gateway + channels (WA connect + Telegram + Discord APIs)
-moltbot status --deep
+openclaw status --deep
 
 # View recent connection events
-moltbot logs --limit 200 | grep "connection\\|disconnect\\|logout"
+openclaw logs --limit 200 | grep "connection\\|disconnect\\|logout"
 ```
 
 **Fix:** Usually reconnects automatically once the Gateway is running. If you’re stuck, restart the Gateway process (however you supervise it), or run it manually with verbose output:
 
 ```bash
-moltbot gateway --verbose
+openclaw gateway --verbose
 ```
 
 If you’re logged out / unlinked:
 
 ```bash
-moltbot channels logout
-trash "${CLAWDBOT_STATE_DIR:-$HOME/.clawdbot}/credentials" # if logout can't cleanly remove everything
-moltbot channels login --verbose       # re-scan QR
+openclaw channels logout
+trash "${OPENCLAW_STATE_DIR:-$HOME/.openclaw}/credentials" # if logout can't cleanly remove everything
+openclaw channels login --verbose       # re-scan QR
 ```
 
 ### Media Send Failing
 
 **Check 1:** Is the file path valid?
+
 ```bash
 ls -la /path/to/your/image.jpg
 ```
 
 **Check 2:** Is it too large?
+
 - Images: max 6MB
-- Audio/Video: max 16MB  
+- Audio/Video: max 16MB
 - Documents: max 100MB
 
 **Check 3:** Check media logs
+
 ```bash
-grep "media\\|fetch\\|download" "$(ls -t /tmp/moltbot/moltbot-*.log | head -1)" | tail -20
+grep "media\\|fetch\\|download" "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)" | tail -20
 ```
 
 ### High Memory Usage
 
-Moltbot keeps conversation history in memory.
+OpenClaw keeps conversation history in memory.
 
 **Fix:** Restart periodically or set session limits:
+
 ```json
 {
   "session": {
-    "historyLimit": 100  // Max messages to keep
+    "historyLimit": 100 // Max messages to keep
   }
 }
 ```
@@ -424,26 +460,28 @@ Moltbot keeps conversation history in memory.
 
 ### “Gateway won’t start — configuration invalid”
 
-Moltbot now refuses to start when the config contains unknown keys, malformed values, or invalid types.
+OpenClaw now refuses to start when the config contains unknown keys, malformed values, or invalid types.
 This is intentional for safety.
 
 Fix it with Doctor:
+
 ```bash
-moltbot doctor
-moltbot doctor --fix
+openclaw doctor
+openclaw doctor --fix
 ```
 
 Notes:
-- `moltbot doctor` reports every invalid entry.
-- `moltbot doctor --fix` applies migrations/repairs and rewrites the config.
-- Diagnostic commands like `moltbot logs`, `moltbot health`, `moltbot status`, `moltbot gateway status`, and `moltbot gateway probe` still run even if the config is invalid.
+
+- `openclaw doctor` reports every invalid entry.
+- `openclaw doctor --fix` applies migrations/repairs and rewrites the config.
+- Diagnostic commands like `openclaw logs`, `openclaw health`, `openclaw status`, `openclaw gateway status`, and `openclaw gateway probe` still run even if the config is invalid.
 
 ### “All models failed” — what should I check first?
 
 - **Credentials** present for the provider(s) being tried (auth profiles + env vars).
 - **Model routing**: confirm `agents.defaults.model.primary` and fallbacks are models you can access.
-- **Gateway logs** in `/tmp/moltbot/…` for the exact provider error.
-- **Model status**: use `/model status` (chat) or `moltbot models status` (CLI).
+- **Gateway logs** in `/tmp/openclaw/…` for the exact provider error.
+- **Model status**: use `/model status` (chat) or `openclaw models status` (CLI).
 
 ### I’m running on my personal WhatsApp number — why is self-chat weird?
 
@@ -455,9 +493,9 @@ Enable self-chat mode and allowlist your own number:
     whatsapp: {
       selfChatMode: true,
       dmPolicy: "allowlist",
-      allowFrom: ["+15555550123"]
-    }
-  }
+      allowFrom: ["+15555550123"],
+    },
+  },
 }
 ```
 
@@ -468,15 +506,15 @@ See [WhatsApp setup](/channels/whatsapp).
 Run the login command again and scan the QR code:
 
 ```bash
-moltbot channels login
+openclaw channels login
 ```
 
 ### Build errors on `main` — what’s the standard fix path?
 
-1) `git pull origin main && pnpm install`
-2) `moltbot doctor`
-3) Check GitHub issues or Discord
-4) Temporary workaround: check out an older commit
+1. `git pull origin main && pnpm install`
+2. `openclaw doctor`
+3. Check GitHub issues or Discord
+4. Temporary workaround: check out an older commit
 
 ### npm install fails (allow-build-scripts / missing tar or yargs). What now?
 
@@ -484,12 +522,13 @@ If you’re running from source, use the repo’s package manager: **pnpm** (pre
 The repo declares `packageManager: "pnpm@…"`.
 
 Typical recovery:
+
 ```bash
 git status   # ensure you’re in the repo root
 pnpm install
 pnpm build
-moltbot doctor
-moltbot gateway restart
+openclaw doctor
+openclaw gateway restart
 ```
 
 Why: pnpm is the configured package manager for this repo.
@@ -500,26 +539,30 @@ Use the **website installer** and select the install method with a flag. It
 upgrades in place and rewrites the gateway service to point at the new install.
 
 Switch **to git install**:
+
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git --no-onboard
+curl -fsSL https://openclaw.ai/install.sh | bash -s -- --install-method git --no-onboard
 ```
 
 Switch **to npm global**:
+
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash
+curl -fsSL https://openclaw.ai/install.sh | bash
 ```
 
 Notes:
+
 - The git flow only rebases if the repo is clean. Commit or stash changes first.
 - After switching, run:
   ```bash
-  moltbot doctor
-  moltbot gateway restart
+  openclaw doctor
+  openclaw gateway restart
   ```
 
 ### Telegram block streaming isn’t splitting text between tool calls. Why?
 
 Block streaming only sends **completed text blocks**. Common reasons you see a single message:
+
 - `agents.defaults.blockStreamingDefault` is still `"off"`.
 - `channels.telegram.blockStreaming` is set to `false`.
 - `channels.telegram.streamMode` is `partial` or `block` **and draft streaming is active**
@@ -528,9 +571,10 @@ Block streaming only sends **completed text blocks**. Common reasons you see a s
 - The model emits one large text block (no mid‑reply flush points).
 
 Fix checklist:
-1) Put block streaming settings under `agents.defaults`, not the root.
-2) Set `channels.telegram.streamMode: "off"` if you want real multi‑message block replies.
-3) Use smaller chunk/coalesce thresholds while debugging.
+
+1. Put block streaming settings under `agents.defaults`, not the root.
+2. Set `channels.telegram.streamMode: "off"` if you want real multi‑message block replies.
+3. Use smaller chunk/coalesce thresholds while debugging.
 
 See [Streaming](/concepts/streaming).
 
@@ -541,29 +585,31 @@ By default `channels.discord.groupPolicy` is **allowlist**, so guilds must be ex
 If you set `channels.discord.guilds.<guildId>.channels`, only the listed channels are allowed; omit it to allow all channels in the guild.
 
 Fix checklist:
-1) Set `channels.discord.groupPolicy: "open"` **or** add a guild allowlist entry (and optionally a channel allowlist).
-2) Use **numeric channel IDs** in `channels.discord.guilds.<guildId>.channels`.
-3) Put `requireMention: false` **under** `channels.discord.guilds` (global or per‑channel).
+
+1. Set `channels.discord.groupPolicy: "open"` **or** add a guild allowlist entry (and optionally a channel allowlist).
+2. Use **numeric channel IDs** in `channels.discord.guilds.<guildId>.channels`.
+3. Put `requireMention: false` **under** `channels.discord.guilds` (global or per‑channel).
    Top‑level `channels.discord.requireMention` is not a supported key.
-4) Ensure the bot has **Message Content Intent** and channel permissions.
-5) Run `moltbot channels status --probe` for audit hints.
+4. Ensure the bot has **Message Content Intent** and channel permissions.
+5. Run `openclaw channels status --probe` for audit hints.
 
 Docs: [Discord](/channels/discord), [Channels troubleshooting](/channels/troubleshooting).
 
 ### Cloud Code Assist API error: invalid tool schema (400). What now?
 
 This is almost always a **tool schema compatibility** issue. The Cloud Code Assist
-endpoint accepts a strict subset of JSON Schema. Moltbot scrubs/normalizes tool
+endpoint accepts a strict subset of JSON Schema. OpenClaw scrubs/normalizes tool
 schemas in current `main`, but the fix is not in the last release yet (as of
 January 13, 2026).
 
 Fix checklist:
-1) **Update Moltbot**:
+
+1. **Update OpenClaw**:
    - If you can run from source, pull `main` and restart the gateway.
    - Otherwise, wait for the next release that includes the schema scrubber.
-2) Avoid unsupported keywords like `anyOf/oneOf/allOf`, `patternProperties`,
+2. Avoid unsupported keywords like `anyOf/oneOf/allOf`, `patternProperties`,
    `additionalProperties`, `minLength`, `maxLength`, `format`, etc.
-3) If you define custom tools, keep the top‑level schema as `type: "object"` with
+3. If you define custom tools, keep the top‑level schema as `type: "object"` with
    `properties` and simple enums.
 
 See [Tools](/tools) and [TypeBox schemas](/concepts/typebox).
@@ -575,12 +621,13 @@ See [Tools](/tools) and [TypeBox schemas](/concepts/typebox).
 If the app disappears or shows "Abort trap 6" when you click "Allow" on a privacy prompt:
 
 **Fix 1: Reset TCC Cache**
+
 ```bash
 tccutil reset All bot.molt.mac.debug
 ```
 
 **Fix 2: Force New Bundle ID**
-If resetting doesn't work, change the `BUNDLE_ID` in [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) (e.g., add a `.test` suffix) and rebuild. This forces macOS to treat it as a new app.
+If resetting doesn't work, change the `BUNDLE_ID` in [`scripts/package-mac-app.sh`](https://github.com/openclaw/openclaw/blob/main/scripts/package-mac-app.sh) (e.g., add a `.test` suffix) and rebuild. This forces macOS to treat it as a new app.
 
 ### Gateway stuck on "Starting..."
 
@@ -588,18 +635,21 @@ The app connects to a local gateway on port `18789`. If it stays stuck:
 
 **Fix 1: Stop the supervisor (preferred)**
 If the gateway is supervised by launchd, killing the PID will just respawn it. Stop the supervisor first:
+
 ```bash
-moltbot gateway status
-moltbot gateway stop
-# Or: launchctl bootout gui/$UID/bot.molt.gateway (replace with bot.molt.<profile>; legacy com.clawdbot.* still works)
+openclaw gateway status
+openclaw gateway stop
+# Or: launchctl bootout gui/$UID/bot.molt.gateway (replace with bot.molt.<profile>; legacy com.openclaw.* still works)
 ```
 
 **Fix 2: Port is busy (find the listener)**
+
 ```bash
 lsof -nP -iTCP:18789 -sTCP:LISTEN
 ```
 
 If it’s an unsupervised process, try a graceful stop first, then escalate:
+
 ```bash
 kill -TERM <PID>
 sleep 1
@@ -607,10 +657,11 @@ kill -9 <PID> # last resort
 ```
 
 **Fix 3: Check the CLI install**
-Ensure the global `moltbot` CLI is installed and matches the app version:
+Ensure the global `openclaw` CLI is installed and matches the app version:
+
 ```bash
-moltbot --version
-npm install -g moltbot@<version>
+openclaw --version
+npm install -g openclaw@<version>
 ```
 
 ## Debug Mode
@@ -619,43 +670,43 @@ Get verbose logging:
 
 ```bash
 # Turn on trace logging in config:
-#   ${CLAWDBOT_CONFIG_PATH:-$HOME/.clawdbot/moltbot.json} -> { logging: { level: "trace" } }
+#   ${OPENCLAW_CONFIG_PATH:-$HOME/.openclaw/openclaw.json} -> { logging: { level: "trace" } }
 #
 # Then run verbose commands to mirror debug output to stdout:
-moltbot gateway --verbose
-moltbot channels login --verbose
+openclaw gateway --verbose
+openclaw channels login --verbose
 ```
 
 ## Log Locations
 
-| Log | Location |
-|-----|----------|
-| Gateway file logs (structured) | `/tmp/moltbot/moltbot-YYYY-MM-DD.log` (or `logging.file`) |
-| Gateway service logs (supervisor) | macOS: `$CLAWDBOT_STATE_DIR/logs/gateway.log` + `gateway.err.log` (default: `~/.clawdbot/logs/...`; profiles use `~/.clawdbot-<profile>/logs/...`)<br />Linux: `journalctl --user -u moltbot-gateway[-<profile>].service -n 200 --no-pager`<br />Windows: `schtasks /Query /TN "Moltbot Gateway (<profile>)" /V /FO LIST` |
-| Session files | `$CLAWDBOT_STATE_DIR/agents/<agentId>/sessions/` |
-| Media cache | `$CLAWDBOT_STATE_DIR/media/` |
-| Credentials | `$CLAWDBOT_STATE_DIR/credentials/` |
+| Log                               | Location                                                                                                                                                                                                                                                                                                                    |
+| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Gateway file logs (structured)    | `/tmp/openclaw/openclaw-YYYY-MM-DD.log` (or `logging.file`)                                                                                                                                                                                                                                                                 |
+| Gateway service logs (supervisor) | macOS: `$OPENCLAW_STATE_DIR/logs/gateway.log` + `gateway.err.log` (default: `~/.openclaw/logs/...`; profiles use `~/.openclaw-<profile>/logs/...`)<br />Linux: `journalctl --user -u openclaw-gateway[-<profile>].service -n 200 --no-pager`<br />Windows: `schtasks /Query /TN "OpenClaw Gateway (<profile>)" /V /FO LIST` |
+| Session files                     | `$OPENCLAW_STATE_DIR/agents/<agentId>/sessions/`                                                                                                                                                                                                                                                                            |
+| Media cache                       | `$OPENCLAW_STATE_DIR/media/`                                                                                                                                                                                                                                                                                                |
+| Credentials                       | `$OPENCLAW_STATE_DIR/credentials/`                                                                                                                                                                                                                                                                                          |
 
 ## Health Check
 
 ```bash
 # Supervisor + probe target + config paths
-moltbot gateway status
+openclaw gateway status
 # Include system-level scans (legacy/extra services, port listeners)
-moltbot gateway status --deep
+openclaw gateway status --deep
 
 # Is the gateway reachable?
-moltbot health --json
+openclaw health --json
 # If it fails, rerun with connection details:
-moltbot health --verbose
+openclaw health --verbose
 
 # Is something listening on the default port?
 lsof -nP -iTCP:18789 -sTCP:LISTEN
 
 # Recent activity (RPC log tail)
-moltbot logs --follow
+openclaw logs --follow
 # Fallback if RPC is down
-tail -20 /tmp/moltbot/moltbot-*.log
+tail -20 /tmp/openclaw/openclaw-*.log
 ```
 
 ## Reset Everything
@@ -663,30 +714,30 @@ tail -20 /tmp/moltbot/moltbot-*.log
 Nuclear option:
 
 ```bash
-moltbot gateway stop
+openclaw gateway stop
 # If you installed a service and want a clean install:
-# moltbot gateway uninstall
+# openclaw gateway uninstall
 
-trash "${CLAWDBOT_STATE_DIR:-$HOME/.clawdbot}"
-moltbot channels login         # re-pair WhatsApp
-moltbot gateway restart           # or: moltbot gateway
+trash "${OPENCLAW_STATE_DIR:-$HOME/.openclaw}"
+openclaw channels login         # re-pair WhatsApp
+openclaw gateway restart           # or: openclaw gateway
 ```
 
 ⚠️ This loses all sessions and requires re-pairing WhatsApp.
 
 ## Getting Help
 
-1. Check logs first: `/tmp/moltbot/` (default: `moltbot-YYYY-MM-DD.log`, or your configured `logging.file`)
+1. Check logs first: `/tmp/openclaw/` (default: `openclaw-YYYY-MM-DD.log`, or your configured `logging.file`)
 2. Search existing issues on GitHub
 3. Open a new issue with:
-   - Moltbot version
+   - OpenClaw version
    - Relevant log snippets
    - Steps to reproduce
    - Your config (redact secrets!)
 
 ---
 
-*"Have you tried turning it off and on again?"* — Every IT person ever
+_"Have you tried turning it off and on again?"_ — Every IT person ever
 
 🦞🔧
 
@@ -697,12 +748,14 @@ If you see `"Failed to start Chrome CDP on port 18800"`:
 **Most likely cause:** Snap-packaged Chromium on Ubuntu.
 
 **Quick fix:** Install Google Chrome instead:
+
 ```bash
 wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
 sudo dpkg -i google-chrome-stable_current_amd64.deb
 ```
 
 Then set in config:
+
 ```json
 {
   "browser": {