@takibeiy/moltbot_cn 2026.1.27 → 2026.2.1-beta.1

package/docs/install/installer.md

@@ -1,32 +1,33 @@
 ---
 summary: "How the installer scripts work (install.sh + install-cli.sh), flags, and automation"
 read_when:
-  - You want to understand `molt.bot/install.sh`
+  - You want to understand `openclaw.ai/install.sh`
   - You want to automate installs (CI / headless)
   - You want to install from a GitHub checkout
+title: "Installer Internals"
 ---
 
 # Installer internals
 
-Moltbot ships two installer scripts (served from `molt.bot`):
+OpenClaw ships two installer scripts (served from `openclaw.ai`):
 
-- `https://molt.bot/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout)
-- `https://molt.bot/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node)
- - `https://molt.bot/install.ps1` — Windows PowerShell installer (npm by default; optional git install)
+- `https://openclaw.ai/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout)
+- `https://openclaw.ai/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node)
+- `https://openclaw.ai/install.ps1` — Windows PowerShell installer (npm by default; optional git install)
 
 To see the current flags/behavior, run:
 
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash -s -- --help
+curl -fsSL https://openclaw.ai/install.sh | bash -s -- --help
 ```
 
 Windows (PowerShell) help:
 
 ```powershell
-& ([scriptblock]::Create((iwr -useb https://molt.bot/install.ps1))) -?
+& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1))) -?
 ```
 
-If the installer completes but `moltbot` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity).
+If the installer completes but `openclaw` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity).
 
 ## install.sh (recommended)
 
@@ -35,37 +36,37 @@ What it does (high level):
 - Detect OS (macOS / Linux / WSL).
 - Ensure Node.js **22+** (macOS via Homebrew; Linux via NodeSource).
 - Choose install method:
-  - `npm` (default): `npm install -g moltbot@latest`
+  - `npm` (default): `npm install -g openclaw@latest`
   - `git`: clone/build a source checkout and install a wrapper script
-- On Linux: avoid global npm permission errors by switching npm’s prefix to `~/.npm-global` when needed.
-- If upgrading an existing install: runs `moltbot doctor --non-interactive` (best effort).
-- For git installs: runs `moltbot doctor --non-interactive` after install/update (best effort).
+- On Linux: avoid global npm permission errors by switching npm's prefix to `~/.npm-global` when needed.
+- If upgrading an existing install: runs `openclaw doctor --non-interactive` (best effort).
+- For git installs: runs `openclaw doctor --non-interactive` after install/update (best effort).
 - Mitigates `sharp` native install gotchas by defaulting `SHARP_IGNORE_GLOBAL_LIBVIPS=1` (avoids building against system libvips).
 
-If you *want* `sharp` to link against a globally-installed libvips (or you’re debugging), set:
+If you _want_ `sharp` to link against a globally-installed libvips (or you’re debugging), set:
 
 ```bash
-SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://molt.bot/install.sh | bash
+SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://openclaw.ai/install.sh | bash
 ```
 
 ### Discoverability / “git install” prompt
 
-If you run the installer while **already inside a Moltbot source checkout** (detected via `package.json` + `pnpm-workspace.yaml`), it prompts:
+If you run the installer while **already inside a OpenClaw source checkout** (detected via `package.json` + `pnpm-workspace.yaml`), it prompts:
 
 - update and use this checkout (`git`)
 - or migrate to the global npm install (`npm`)
 
-In non-interactive contexts (no TTY / `--no-prompt`), you must pass `--install-method git|npm` (or set `CLAWDBOT_INSTALL_METHOD`), otherwise the script exits with code `2`.
+In non-interactive contexts (no TTY / `--no-prompt`), you must pass `--install-method git|npm` (or set `OPENCLAW_INSTALL_METHOD`), otherwise the script exits with code `2`.
 
 ### Why Git is needed
 
 Git is required for the `--install-method git` path (clone / pull).
 
-For `npm` installs, Git is *usually* not required, but some environments still end up needing it (e.g. when a package or dependency is fetched via a git URL). The installer currently ensures Git is present to avoid `spawn git ENOENT` surprises on fresh distros.
+For `npm` installs, Git is _usually_ not required, but some environments still end up needing it (e.g. when a package or dependency is fetched via a git URL). The installer currently ensures Git is present to avoid `spawn git ENOENT` surprises on fresh distros.
 
 ### Why npm hits `EACCES` on fresh Linux
 
-On some Linux setups (especially after installing Node via the system package manager or NodeSource), npm’s global prefix points at a root-owned location. Then `npm install -g ...` fails with `EACCES` / `mkdir` permission errors.
+On some Linux setups (especially after installing Node via the system package manager or NodeSource), npm's global prefix points at a root-owned location. Then `npm install -g ...` fails with `EACCES` / `mkdir` permission errors.
 
 `install.sh` mitigates this by switching the prefix to:
 
@@ -73,12 +74,12 @@ On some Linux setups (especially after installing Node via the system package ma
 
 ## install-cli.sh (non-root CLI installer)
 
-This script installs `moltbot` into a prefix (default: `~/.clawdbot`) and also installs a dedicated Node runtime under that prefix, so it can work on machines where you don’t want to touch the system Node/npm.
+This script installs `openclaw` into a prefix (default: `~/.openclaw`) and also installs a dedicated Node runtime under that prefix, so it can work on machines where you don’t want to touch the system Node/npm.
 
 Help:
 
 ```bash
-curl -fsSL https://molt.bot/install-cli.sh | bash -s -- --help
+curl -fsSL https://openclaw.ai/install-cli.sh | bash -s -- --help
 ```
 
 ## install.ps1 (Windows PowerShell)
@@ -87,28 +88,28 @@ What it does (high level):
 
 - Ensure Node.js **22+** (winget/Chocolatey/Scoop or manual).
 - Choose install method:
-  - `npm` (default): `npm install -g moltbot@latest`
+  - `npm` (default): `npm install -g openclaw@latest`
   - `git`: clone/build a source checkout and install a wrapper script
-- Runs `moltbot doctor --non-interactive` on upgrades and git installs (best effort).
+- Runs `openclaw doctor --non-interactive` on upgrades and git installs (best effort).
 
 Examples:
 
 ```powershell
-iwr -useb https://molt.bot/install.ps1 | iex
+iwr -useb https://openclaw.ai/install.ps1 | iex
 ```
 
 ```powershell
-iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git
+iwr -useb https://openclaw.ai/install.ps1 | iex -InstallMethod git
 ```
 
 ```powershell
-iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git -GitDir "C:\\moltbot"
+iwr -useb https://openclaw.ai/install.ps1 | iex -InstallMethod git -GitDir "C:\\openclaw"
 ```
 
 Environment variables:
 
-- `CLAWDBOT_INSTALL_METHOD=git|npm`
-- `CLAWDBOT_GIT_DIR=...`
+- `OPENCLAW_INSTALL_METHOD=git|npm`
+- `OPENCLAW_GIT_DIR=...`
 
 Git requirement:
 
@@ -118,5 +119,5 @@ Git for Windows link (`https://git-scm.com/download/win`) and exit.
 Common Windows issues:
 
 - **npm error spawn git / ENOENT**: install Git for Windows and reopen PowerShell, then rerun the installer.
-- **"moltbot" is not recognized**: your npm global bin folder is not on PATH. Most systems use
+- **"openclaw" is not recognized**: your npm global bin folder is not on PATH. Most systems use
   `%AppData%\\npm`. You can also run `npm config get prefix` and add `\\bin` to PATH, then reopen PowerShell.

package/docs/install/migrating.md

@@ -1,17 +1,19 @@
 ---
-summary: "Move (migrate) a Moltbot install from one machine to another"
+summary: "Move (migrate) a OpenClaw install from one machine to another"
 read_when:
-  - You are moving Moltbot to a new laptop/server
+  - You are moving OpenClaw to a new laptop/server
   - You want to preserve sessions, auth, and channel logins (WhatsApp, etc.)
+title: "Migration Guide"
 ---
-# Migrating Moltbot to a new machine
 
-This guide migrates a Moltbot Gateway from one machine to another **without redoing onboarding**.
+# Migrating OpenClaw to a new machine
+
+This guide migrates a OpenClaw Gateway from one machine to another **without redoing onboarding**.
 
 The migration is simple conceptually:
 
-- Copy the **state directory** (`$CLAWDBOT_STATE_DIR`, default: `~/.clawdbot/`) — this includes config, auth, sessions, and channel state.
-- Copy your **workspace** (`~/clawd/` by default) — this includes your agent files (memory, prompts, etc.).
+- Copy the **state directory** (`$OPENCLAW_STATE_DIR`, default: `~/.openclaw/`) — this includes config, auth, sessions, and channel state.
+- Copy your **workspace** (`~/.openclaw/workspace/` by default) — this includes your agent files (memory, prompts, etc.).
 
 But there are common footguns around **profiles**, **permissions**, and **partial copies**.
 
@@ -21,26 +23,26 @@ But there are common footguns around **profiles**, **permissions**, and **partia
 
 Most installs use the default:
 
-- **State dir:** `~/.clawdbot/`
+- **State dir:** `~/.openclaw/`
 
 But it may be different if you use:
 
-- `--profile <name>` (often becomes `~/.clawdbot-<profile>/`)
-- `CLAWDBOT_STATE_DIR=/some/path`
+- `--profile <name>` (often becomes `~/.openclaw-<profile>/`)
+- `OPENCLAW_STATE_DIR=/some/path`
 
 If you’re not sure, run on the **old** machine:
 
 ```bash
-moltbot status
+openclaw status
 ```
 
-Look for mentions of `CLAWDBOT_STATE_DIR` / profile in the output. If you run multiple gateways, repeat for each profile.
+Look for mentions of `OPENCLAW_STATE_DIR` / profile in the output. If you run multiple gateways, repeat for each profile.
 
 ### 2) Identify your workspace
 
 Common defaults:
 
-- `~/clawd/` (recommended workspace)
+- `~/.openclaw/workspace/` (recommended workspace)
 - a custom folder you created
 
 Your workspace is where files like `MEMORY.md`, `USER.md`, and `memory/*.md` live.
@@ -49,7 +51,7 @@ Your workspace is where files like `MEMORY.md`, `USER.md`, and `memory/*.md` liv
 
 If you copy **both** the state dir and workspace, you keep:
 
-- Gateway configuration (`moltbot.json`)
+- Gateway configuration (`openclaw.json`)
 - Auth profiles / API keys / OAuth tokens
 - Session history + agent state
 - Channel state (e.g. WhatsApp login/session)
@@ -61,7 +63,7 @@ If you copy **only** the workspace (e.g., via Git), you do **not** preserve:
 - credentials
 - channel logins
 
-Those live under `$CLAWDBOT_STATE_DIR`.
+Those live under `$OPENCLAW_STATE_DIR`.
 
 ## Migration steps (recommended)
 
@@ -70,7 +72,7 @@ Those live under `$CLAWDBOT_STATE_DIR`.
 On the **old** machine, stop the gateway first so files aren’t changing mid-copy:
 
 ```bash
-moltbot gateway stop
+openclaw gateway stop
 ```
 
 (Optional but recommended) archive the state dir and workspace:
@@ -78,27 +80,27 @@ moltbot gateway stop
 ```bash
 # Adjust paths if you use a profile or custom locations
 cd ~
-tar -czf moltbot-state.tgz .clawdbot
+tar -czf openclaw-state.tgz .openclaw
 
-tar -czf clawd-workspace.tgz clawd
+tar -czf openclaw-workspace.tgz .openclaw/workspace
 ```
 
-If you have multiple profiles/state dirs (e.g. `~/.clawdbot-main`, `~/.clawdbot-work`), archive each.
+If you have multiple profiles/state dirs (e.g. `~/.openclaw-main`, `~/.openclaw-work`), archive each.
 
-### Step 1 — Install Moltbot on the new machine
+### Step 1 — Install OpenClaw on the new machine
 
 On the **new** machine, install the CLI (and Node if needed):
 
 - See: [Install](/install)
 
-At this stage, it’s OK if onboarding creates a fresh `~/.clawdbot/` — you will overwrite it in the next step.
+At this stage, it’s OK if onboarding creates a fresh `~/.openclaw/` — you will overwrite it in the next step.
 
 ### Step 2 — Copy the state dir + workspace to the new machine
 
 Copy **both**:
 
-- `$CLAWDBOT_STATE_DIR` (default `~/.clawdbot/`)
-- your workspace (default `~/clawd/`)
+- `$OPENCLAW_STATE_DIR` (default `~/.openclaw/`)
+- your workspace (default `~/.openclaw/workspace/`)
 
 Common approaches:
 
@@ -108,7 +110,7 @@ Common approaches:
 
 After copying, ensure:
 
-- Hidden directories were included (e.g. `.clawdbot/`)
+- Hidden directories were included (e.g. `.openclaw/`)
 - File ownership is correct for the user running the gateway
 
 ### Step 3 — Run Doctor (migrations + service repair)
@@ -116,7 +118,7 @@ After copying, ensure:
 On the **new** machine:
 
 ```bash
-moltbot doctor
+openclaw doctor
 ```
 
 Doctor is the “safe boring” command. It repairs services, applies config migrations, and warns about mismatches.
@@ -124,15 +126,15 @@ Doctor is the “safe boring” command. It repairs services, applies config mig
 Then:
 
 ```bash
-moltbot gateway restart
-moltbot status
+openclaw gateway restart
+openclaw status
 ```
 
 ## Common footguns (and how to avoid them)
 
 ### Footgun: profile / state-dir mismatch
 
-If you ran the old gateway with a profile (or `CLAWDBOT_STATE_DIR`), and the new gateway uses a different one, you’ll see symptoms like:
+If you ran the old gateway with a profile (or `OPENCLAW_STATE_DIR`), and the new gateway uses a different one, you’ll see symptoms like:
 
 - config changes not taking effect
 - channels missing / logged out
@@ -141,17 +143,17 @@ If you ran the old gateway with a profile (or `CLAWDBOT_STATE_DIR`), and the new
 Fix: run the gateway/service using the **same** profile/state dir you migrated, then rerun:
 
 ```bash
-moltbot doctor
+openclaw doctor
 ```
 
-### Footgun: copying only `moltbot.json`
+### Footgun: copying only `openclaw.json`
 
-`moltbot.json` is not enough. Many providers store state under:
+`openclaw.json` is not enough. Many providers store state under:
 
-- `$CLAWDBOT_STATE_DIR/credentials/`
-- `$CLAWDBOT_STATE_DIR/agents/<agentId>/...`
+- `$OPENCLAW_STATE_DIR/credentials/`
+- `$OPENCLAW_STATE_DIR/agents/<agentId>/...`
 
-Always migrate the entire `$CLAWDBOT_STATE_DIR` folder.
+Always migrate the entire `$OPENCLAW_STATE_DIR` folder.
 
 ### Footgun: permissions / ownership
 
@@ -168,7 +170,7 @@ If you’re in remote mode, migrate the **gateway host**.
 
 ### Footgun: secrets in backups
 
-`$CLAWDBOT_STATE_DIR` contains secrets (API keys, OAuth tokens, WhatsApp creds). Treat backups like production secrets:
+`$OPENCLAW_STATE_DIR` contains secrets (API keys, OAuth tokens, WhatsApp creds). Treat backups like production secrets:
 
 - store encrypted
 - avoid sharing over insecure channels
@@ -178,7 +180,7 @@ If you’re in remote mode, migrate the **gateway host**.
 
 On the new machine, confirm:
 
-- `moltbot status` shows the gateway running
+- `openclaw status` shows the gateway running
 - Your channels are still connected (e.g. WhatsApp doesn’t require re-pair)
 - The dashboard opens and shows existing sessions
 - Your workspace files (memory, configs) are present
@@ -187,4 +189,4 @@ On the new machine, confirm:
 
 - [Doctor](/gateway/doctor)
 - [Gateway troubleshooting](/gateway/troubleshooting)
-- [Where does Moltbot store its data?](/help/faq#where-does-moltbot-store-its-data)
+- [Where does OpenClaw store its data?](/help/faq#where-does-openclaw-store-its-data)

package/docs/install/nix.md

@@ -1,37 +1,38 @@
 ---
-summary: "Install Moltbot declaratively with Nix"
+summary: "Install OpenClaw declaratively with Nix"
 read_when:
   - You want reproducible, rollback-able installs
   - You're already using Nix/NixOS/Home Manager
   - You want everything pinned and managed declaratively
+title: "Nix"
 ---
 
 # Nix Installation
 
-The recommended way to run Moltbot with Nix is via **[nix-moltbot](https://github.com/moltbot/nix-moltbot)** — a batteries-included Home Manager module.
+The recommended way to run OpenClaw with Nix is via **[nix-openclaw](https://github.com/openclaw/nix-openclaw)** — a batteries-included Home Manager module.
 
 ## Quick Start
 
 Paste this to your AI agent (Claude, Cursor, etc.):
 
 ```text
-I want to set up nix-moltbot on my Mac.
-Repository: github:moltbot/nix-moltbot
+I want to set up nix-openclaw on my Mac.
+Repository: github:openclaw/nix-openclaw
 
 What I need you to do:
 1. Check if Determinate Nix is installed (if not, install it)
-2. Create a local flake at ~/code/moltbot-local using templates/agent-first/flake.nix
+2. Create a local flake at ~/code/openclaw-local using templates/agent-first/flake.nix
 3. Help me create a Telegram bot (@BotFather) and get my chat ID (@userinfobot)
 4. Set up secrets (bot token, Anthropic key) - plain files at ~/.secrets/ is fine
 5. Fill in the template placeholders and run home-manager switch
 6. Verify: launchd running, bot responds to messages
 
-Reference the nix-moltbot README for module options.
+Reference the nix-openclaw README for module options.
 ```
 
-> **📦 Full guide: [github.com/moltbot/nix-moltbot](https://github.com/moltbot/nix-moltbot)**
+> **📦 Full guide: [github.com/openclaw/nix-openclaw](https://github.com/openclaw/nix-openclaw)**
 >
-> The nix-moltbot repo is the source of truth for Nix installation. This page is just a quick overview.
+> The nix-openclaw repo is the source of truth for Nix installation. This page is just a quick overview.
 
 ## What you get
 
@@ -44,28 +45,28 @@ Reference the nix-moltbot README for module options.
 
 ## Nix Mode Runtime Behavior
 
-When `CLAWDBOT_NIX_MODE=1` is set (automatic with nix-moltbot):
+When `OPENCLAW_NIX_MODE=1` is set (automatic with nix-openclaw):
 
-Moltbot supports a **Nix mode** that makes configuration deterministic and disables auto-install flows.
+OpenClaw supports a **Nix mode** that makes configuration deterministic and disables auto-install flows.
 Enable it by exporting:
 
 ```bash
-CLAWDBOT_NIX_MODE=1
+OPENCLAW_NIX_MODE=1
 ```
 
 On macOS, the GUI app does not automatically inherit shell env vars. You can
 also enable Nix mode via defaults:
 
 ```bash
-defaults write bot.molt.mac moltbot.nixMode -bool true
+defaults write bot.molt.mac openclaw.nixMode -bool true
 ```
 
 ### Config + state paths
 
-Moltbot reads JSON5 config from `CLAWDBOT_CONFIG_PATH` and stores mutable data in `CLAWDBOT_STATE_DIR`.
+OpenClaw reads JSON5 config from `OPENCLAW_CONFIG_PATH` and stores mutable data in `OPENCLAW_STATE_DIR`.
 
-- `CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`)
-- `CLAWDBOT_CONFIG_PATH` (default: `$CLAWDBOT_STATE_DIR/moltbot.json`)
+- `OPENCLAW_STATE_DIR` (default: `~/.openclaw`)
+- `OPENCLAW_CONFIG_PATH` (default: `$OPENCLAW_STATE_DIR/openclaw.json`)
 
 When running under Nix, set these explicitly to Nix-managed locations so runtime state and config
 stay out of the immutable store.
@@ -81,15 +82,15 @@ stay out of the immutable store.
 The macOS packaging flow expects a stable Info.plist template at:
 
 ```
-apps/macos/Sources/Moltbot/Resources/Info.plist
+apps/macos/Sources/OpenClaw/Resources/Info.plist
 ```
 
-[`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields
+[`scripts/package-mac-app.sh`](https://github.com/openclaw/openclaw/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields
 (bundle ID, version/build, Git SHA, Sparkle keys). This keeps the plist deterministic for SwiftPM
 packaging and Nix builds (which do not rely on a full Xcode toolchain).
 
 ## Related
 
-- [nix-moltbot](https://github.com/moltbot/nix-moltbot) — full setup guide
+- [nix-openclaw](https://github.com/openclaw/nix-openclaw) — full setup guide
 - [Wizard](/start/wizard) — non-Nix CLI setup
 - [Docker](/install/docker) — containerized setup

package/docs/install/node.md

@@ -2,16 +2,16 @@
 title: "Node.js + npm (PATH sanity)"
 summary: "Node.js + npm install sanity: versions, PATH, and global installs"
 read_when:
-  - "You installed Moltbot but `moltbot` is “command not found”"
+  - "You installed OpenClaw but `openclaw` is “command not found”"
   - "You’re setting up Node.js/npm on a new machine"
   - "npm install -g ... fails with permissions or PATH issues"
 ---
 
 # Node.js + npm (PATH sanity)
 
-Moltbot’s runtime baseline is **Node 22+**.
+OpenClaw’s runtime baseline is **Node 22+**.
 
-If you can run `npm install -g moltbot@latest` but later see `moltbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
+If you can run `npm install -g openclaw@latest` but later see `openclaw: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
 
 ## Quick diagnosis
 
@@ -24,17 +24,17 @@ npm prefix -g
 echo "$PATH"
 ```
 
-If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `moltbot`).
+If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `openclaw`).
 
 ## Fix: put npm’s global bin dir on PATH
 
-1) Find your global npm prefix:
+1. Find your global npm prefix:
 
 ```bash
 npm prefix -g
 ```
 
-2) Add the global npm bin directory to your shell startup file:
+2. Add the global npm bin directory to your shell startup file:
 
 - zsh: `~/.zshrc`
 - bash: `~/.bashrc`

package/docs/install/uninstall.md

@@ -1,14 +1,16 @@
 ---
-summary: "Uninstall Moltbot completely (CLI, service, state, workspace)"
+summary: "Uninstall OpenClaw completely (CLI, service, state, workspace)"
 read_when:
-  - You want to remove Moltbot from a machine
+  - You want to remove OpenClaw from a machine
   - The gateway service is still running after uninstall
+title: "Uninstall"
 ---
 
 # Uninstall
 
 Two paths:
-- **Easy path** if `moltbot` is still installed.
+
+- **Easy path** if `openclaw` is still installed.
 - **Manual service removal** if the CLI is gone but the service is still running.
 
 ## Easy path (CLI still installed)
@@ -16,110 +18,111 @@ Two paths:
 Recommended: use the built-in uninstaller:
 
 ```bash
-moltbot uninstall
+openclaw uninstall
 ```
 
 Non-interactive (automation / npx):
 
 ```bash
-moltbot uninstall --all --yes --non-interactive
-npx -y moltbot uninstall --all --yes --non-interactive
+openclaw uninstall --all --yes --non-interactive
+npx -y openclaw uninstall --all --yes --non-interactive
 ```
 
 Manual steps (same result):
 
-1) Stop the gateway service:
+1. Stop the gateway service:
 
 ```bash
-moltbot gateway stop
+openclaw gateway stop
 ```
 
-2) Uninstall the gateway service (launchd/systemd/schtasks):
+2. Uninstall the gateway service (launchd/systemd/schtasks):
 
 ```bash
-moltbot gateway uninstall
+openclaw gateway uninstall
 ```
 
-3) Delete state + config:
+3. Delete state + config:
 
 ```bash
-rm -rf "${CLAWDBOT_STATE_DIR:-$HOME/.clawdbot}"
+rm -rf "${OPENCLAW_STATE_DIR:-$HOME/.openclaw}"
 ```
 
-If you set `CLAWDBOT_CONFIG_PATH` to a custom location outside the state dir, delete that file too.
+If you set `OPENCLAW_CONFIG_PATH` to a custom location outside the state dir, delete that file too.
 
-4) Delete your workspace (optional, removes agent files):
+4. Delete your workspace (optional, removes agent files):
 
 ```bash
-rm -rf ~/clawd
+rm -rf ~/.openclaw/workspace
 ```
 
-5) Remove the CLI install (pick the one you used):
+5. Remove the CLI install (pick the one you used):
 
 ```bash
-npm rm -g moltbot
-pnpm remove -g moltbot
-bun remove -g moltbot
+npm rm -g openclaw
+pnpm remove -g openclaw
+bun remove -g openclaw
 ```
 
-6) If you installed the macOS app:
+6. If you installed the macOS app:
 
 ```bash
-rm -rf /Applications/Moltbot.app
+rm -rf /Applications/OpenClaw.app
 ```
 
 Notes:
-- If you used profiles (`--profile` / `CLAWDBOT_PROFILE`), repeat step 3 for each state dir (defaults are `~/.clawdbot-<profile>`).
+
+- If you used profiles (`--profile` / `OPENCLAW_PROFILE`), repeat step 3 for each state dir (defaults are `~/.openclaw-<profile>`).
 - In remote mode, the state dir lives on the **gateway host**, so run steps 1-4 there too.
 
 ## Manual service removal (CLI not installed)
 
-Use this if the gateway service keeps running but `moltbot` is missing.
+Use this if the gateway service keeps running but `openclaw` is missing.
 
 ### macOS (launchd)
 
-Default label is `bot.molt.gateway` (or `bot.molt.<profile>`; legacy `com.clawdbot.*` may still exist):
+Default label is `bot.molt.gateway` (or `bot.molt.<profile>`; legacy `com.openclaw.*` may still exist):
 
 ```bash
 launchctl bootout gui/$UID/bot.molt.gateway
 rm -f ~/Library/LaunchAgents/bot.molt.gateway.plist
 ```
 
-If you used a profile, replace the label and plist name with `bot.molt.<profile>`. Remove any legacy `com.clawdbot.*` plists if present.
+If you used a profile, replace the label and plist name with `bot.molt.<profile>`. Remove any legacy `com.openclaw.*` plists if present.
 
 ### Linux (systemd user unit)
 
-Default unit name is `moltbot-gateway.service` (or `moltbot-gateway-<profile>.service`):
+Default unit name is `openclaw-gateway.service` (or `openclaw-gateway-<profile>.service`):
 
 ```bash
-systemctl --user disable --now moltbot-gateway.service
-rm -f ~/.config/systemd/user/moltbot-gateway.service
+systemctl --user disable --now openclaw-gateway.service
+rm -f ~/.config/systemd/user/openclaw-gateway.service
 systemctl --user daemon-reload
 ```
 
 ### Windows (Scheduled Task)
 
-Default task name is `Moltbot Gateway` (or `Moltbot Gateway (<profile>)`).
+Default task name is `OpenClaw Gateway` (or `OpenClaw Gateway (<profile>)`).
 The task script lives under your state dir.
 
 ```powershell
-schtasks /Delete /F /TN "Moltbot Gateway"
-Remove-Item -Force "$env:USERPROFILE\.clawdbot\gateway.cmd"
+schtasks /Delete /F /TN "OpenClaw Gateway"
+Remove-Item -Force "$env:USERPROFILE\.openclaw\gateway.cmd"
 ```
 
-If you used a profile, delete the matching task name and `~\.clawdbot-<profile>\gateway.cmd`.
+If you used a profile, delete the matching task name and `~\.openclaw-<profile>\gateway.cmd`.
 
 ## Normal install vs source checkout
 
 ### Normal install (install.sh / npm / pnpm / bun)
 
-If you used `https://molt.bot/install.sh` or `install.ps1`, the CLI was installed with `npm install -g moltbot@latest`.
-Remove it with `npm rm -g moltbot` (or `pnpm remove -g` / `bun remove -g` if you installed that way).
+If you used `https://openclaw.ai/install.sh` or `install.ps1`, the CLI was installed with `npm install -g openclaw@latest`.
+Remove it with `npm rm -g openclaw` (or `pnpm remove -g` / `bun remove -g` if you installed that way).
 
 ### Source checkout (git clone)
 
-If you run from a repo checkout (`git clone` + `moltbot ...` / `bun run moltbot ...`):
+If you run from a repo checkout (`git clone` + `openclaw ...` / `bun run openclaw ...`):
 
-1) Uninstall the gateway service **before** deleting the repo (use the easy path above or manual service removal).
-2) Delete the repo directory.
-3) Remove state + workspace as shown above.
+1. Uninstall the gateway service **before** deleting the repo (use the easy path above or manual service removal).
+2. Delete the repo directory.
+3. Remove state + workspace as shown above.