@gguf/pigbot 0.0.6 → 0.0.7

package/docs/channels/tlon.md

@@ -5,7 +5,7 @@ read_when:
 ---
 # Tlon (plugin)
 
-Tlon is a decentralized messenger built on Urbit. Moltbot connects to your Urbit ship and can
+Tlon is a decentralized messenger built on Urbit. OpenClaw connects to your Urbit ship and can
 respond to DMs and group chat messages. Group replies require an @ mention by default and can
 be further restricted via allowlists.
 
@@ -19,13 +19,13 @@ Tlon ships as a plugin and is not bundled with the core install.
 Install via CLI (npm registry):
 
 ```bash
-moltbot plugins install @moltbot/tlon
+openclaw plugins install @openclaw/tlon
 ```
 
 Local checkout (when running from a git repo):
 
 ```bash
-moltbot plugins install ./extensions/tlon
+openclaw plugins install ./extensions/tlon
 ```
 
 Details: [Plugins](/plugin)
@@ -121,7 +121,7 @@ Group authorization (restricted by default):
 
 ## Delivery targets (CLI/cron)
 
-Use these with `moltbot message send` or cron delivery:
+Use these with `openclaw message send` or cron delivery:
 
 - DM: `~sampel-palnet` or `dm/~sampel-palnet`
 - Group: `chat/~host-ship/channel` or `group:~host-ship/channel`
@@ -129,5 +129,5 @@ Use these with `moltbot message send` or cron delivery:
 ## Notes
 
 - Group replies require a mention (e.g. `~your-bot-ship`) to respond.
-- Thread replies: if the inbound message is in a thread, Moltbot replies in-thread.
+- Thread replies: if the inbound message is in a thread, OpenClaw replies in-thread.
 - Media: `sendMedia` falls back to text + URL (no native upload).

package/docs/channels/troubleshooting.md

@@ -9,8 +9,8 @@ read_when:
 Start with:
 
 ```bash
-moltbot doctor
-moltbot channels status --probe
+openclaw doctor
+openclaw channels status --probe
 ```
 
 `channels status --probe` prints warnings when it can detect common channel misconfigurations, and includes small live checks (credentials, some permissions/membership).

package/docs/channels/twitch.md

@@ -1,11 +1,11 @@
 ---
 summary: "Twitch chat bot configuration and setup"
 read_when:
-  - Setting up Twitch chat integration for Moltbot
+  - Setting up Twitch chat integration for OpenClaw
 ---
 # Twitch (plugin)
 
-Twitch chat support via IRC connection. Moltbot connects as a Twitch user (bot account) to receive and send messages in channels.
+Twitch chat support via IRC connection. OpenClaw connects as a Twitch user (bot account) to receive and send messages in channels.
 
 ## Plugin required
 
@@ -14,13 +14,13 @@ Twitch ships as a plugin and is not bundled with the core install.
 Install via CLI (npm registry):
 
 ```bash
-moltbot plugins install @moltbot/twitch
+openclaw plugins install @openclaw/twitch
 ```
 
 Local checkout (when running from a git repo):
 
 ```bash
-moltbot plugins install ./extensions/twitch
+openclaw plugins install ./extensions/twitch
 ```
 
 Details: [Plugins](/plugin)
@@ -34,7 +34,7 @@ Details: [Plugins](/plugin)
    - Copy the **Client ID** and **Access Token**
 3) Find your Twitch user ID: https://www.streamweasels.com/tools/convert-twitch-username-to-user-id/
 4) Configure the token:
-   - Env: `CLAWDBOT_TWITCH_ACCESS_TOKEN=...` (default account only)
+   - Env: `OPENCLAW_TWITCH_ACCESS_TOKEN=...` (default account only)
    - Or config: `channels.twitch.accessToken`
    - If both are set, config takes precedence (env fallback is default-account only).
 5) Start the gateway.
@@ -48,8 +48,8 @@ Minimal config:
   channels: {
     twitch: {
       enabled: true,
-      username: "moltbot",              // Bot's Twitch account
-      accessToken: "oauth:abc123...",    // OAuth Access Token (or use CLAWDBOT_TWITCH_ACCESS_TOKEN env var)
+      username: "openclaw",              // Bot's Twitch account
+      accessToken: "oauth:abc123...",    // OAuth Access Token (or use OPENCLAW_TWITCH_ACCESS_TOKEN env var)
       clientId: "xyz789...",             // Client ID from Token Generator
       channel: "vevisk",                 // Which Twitch channel's chat to join (required)
       allowFrom: ["123456789"]           // (recommended) Your Twitch user ID only - get it from https://www.streamweasels.com/tools/convert-twitch-username-to-user-id/
@@ -80,7 +80,7 @@ No manual app registration needed. Tokens expire after several hours.
 
 **Env var (default account only):**
 ```bash
-CLAWDBOT_TWITCH_ACCESS_TOKEN=oauth:abc123...
+OPENCLAW_TWITCH_ACCESS_TOKEN=oauth:abc123...
 ```
 
 **Or config:**
@@ -89,7 +89,7 @@ CLAWDBOT_TWITCH_ACCESS_TOKEN=oauth:abc123...
   channels: {
     twitch: {
       enabled: true,
-      username: "moltbot",
+      username: "openclaw",
       accessToken: "oauth:abc123...",
       clientId: "xyz789...",
       channel: "vevisk"
@@ -150,13 +150,13 @@ Example (one bot account in two channels):
     twitch: {
       accounts: {
         channel1: {
-          username: "moltbot",
+          username: "openclaw",
           accessToken: "oauth:abc123...",
           clientId: "xyz789...",
           channel: "vevisk"
         },
         channel2: {
-          username: "moltbot",
+          username: "openclaw",
           accessToken: "oauth:def456...",
           clientId: "uvw012...",
           channel: "secondchannel"
@@ -245,8 +245,8 @@ By default, `requireMention` is `true`. To disable and respond to all messages:
 First, run diagnostic commands:
 
 ```bash
-moltbot doctor
-moltbot channels status --probe
+openclaw doctor
+openclaw channels status --probe
 ```
 
 ### Bot doesn't respond to messages
@@ -305,7 +305,7 @@ Full example:
   channels: {
     twitch: {
       enabled: true,
-      username: "moltbot",
+      username: "openclaw",
       accessToken: "oauth:abc123...",
       clientId: "xyz789...",
       channel: "vevisk",

package/docs/channels/whatsapp.md

@@ -10,8 +10,8 @@ Status: WhatsApp Web via Baileys only. Gateway owns the session(s).
 
 ## Quick setup (beginner)
 1) Use a **separate phone number** if possible (recommended).
-2) Configure WhatsApp in `~/.clawdbot/moltbot.json`.
-3) Run `moltbot channels login` to scan the QR code (Linked Devices).
+2) Configure WhatsApp in `~/.openclaw/openclaw.json`.
+3) Run `openclaw channels login` to scan the QR code (Linked Devices).
 4) Start the gateway.
 
 Minimal config:
@@ -48,12 +48,12 @@ Disable with:
 
 ## Getting a phone number (two modes)
 
-WhatsApp requires a real mobile number for verification. VoIP and virtual numbers are usually blocked. There are two supported ways to run Moltbot on WhatsApp:
+WhatsApp requires a real mobile number for verification. VoIP and virtual numbers are usually blocked. There are two supported ways to run OpenClaw on WhatsApp:
 
 ### Dedicated number (recommended)
-Use a **separate phone number** for Moltbot. Best UX, clean routing, no self-chat quirks. Ideal setup: **spare/old Android phone + eSIM**. Leave it on Wi‑Fi and power, and link it via QR.
+Use a **separate phone number** for OpenClaw. Best UX, clean routing, no self-chat quirks. Ideal setup: **spare/old Android phone + eSIM**. Leave it on Wi‑Fi and power, and link it via QR.
 
-**WhatsApp Business:** You can use WhatsApp Business on the same device with a different number. Great for keeping your personal WhatsApp separate — install WhatsApp Business and register the Moltbot number there.
+**WhatsApp Business:** You can use WhatsApp Business on the same device with a different number. Great for keeping your personal WhatsApp separate — install WhatsApp Business and register the OpenClaw number there.
 
 **Sample config (dedicated number, single-user allowlist):**
 ```json5
@@ -69,10 +69,10 @@ Use a **separate phone number** for Moltbot. Best UX, clean routing, no self-cha
 
 **Pairing mode (optional):**
 If you want pairing instead of allowlist, set `channels.whatsapp.dmPolicy` to `pairing`. Unknown senders get a pairing code; approve with:
-`moltbot pairing approve whatsapp <code>`
+`openclaw pairing approve whatsapp <code>`
 
 ### Personal number (fallback)
-Quick fallback: run Moltbot on **your own number**. Message yourself (WhatsApp “Message yourself”) for testing so you don’t spam contacts. Expect to read verification codes on your main phone during setup and experiments. **Must enable self-chat mode.**
+Quick fallback: run OpenClaw on **your own number**. Message yourself (WhatsApp “Message yourself”) for testing so you don’t spam contacts. Expect to read verification codes on your main phone during setup and experiments. **Must enable self-chat mode.**
 When the wizard asks for your personal WhatsApp number, enter the phone you will message from (the owner/sender), not the assistant number.
 
 **Sample config (personal number, self-chat):**
@@ -86,7 +86,7 @@ When the wizard asks for your personal WhatsApp number, enter the phone you will
 }
 ```
 
-Self-chat replies default to `[{identity.name}]` when set (otherwise `[moltbot]`)
+Self-chat replies default to `[{identity.name}]` when set (otherwise `[openclaw]`)
 if `messages.responsePrefix` is unset. Set it explicitly to customize or disable
 the prefix (use `""` to remove it).
 
@@ -101,20 +101,20 @@ the prefix (use `""` to remove it).
 **Tip:** The number only needs to receive one verification SMS. After that, WhatsApp Web sessions persist via `creds.json`.
 
 ## Why Not Twilio?
-- Early Moltbot builds supported Twilio’s WhatsApp Business integration.
+- Early OpenClaw builds supported Twilio’s WhatsApp Business integration.
 - WhatsApp Business numbers are a poor fit for a personal assistant.
 - Meta enforces a 24‑hour reply window; if you haven’t responded in the last 24 hours, the business number can’t initiate new messages.
 - High-volume or “chatty” usage triggers aggressive blocking, because business accounts aren’t meant to send dozens of personal assistant messages.
 - Result: unreliable delivery and frequent blocks, so support was removed.
 
 ## Login + credentials
-- Login command: `moltbot channels login` (QR via Linked Devices).
-- Multi-account login: `moltbot channels login --account <id>` (`<id>` = `accountId`).
+- Login command: `openclaw channels login` (QR via Linked Devices).
+- Multi-account login: `openclaw channels login --account <id>` (`<id>` = `accountId`).
 - Default account (when `--account` is omitted): `default` if present, otherwise the first configured account id (sorted).
-- Credentials stored in `~/.clawdbot/credentials/whatsapp/<accountId>/creds.json`.
+- Credentials stored in `~/.openclaw/credentials/whatsapp/<accountId>/creds.json`.
 - Backup copy at `creds.json.bak` (restored on corruption).
-- Legacy compatibility: older installs stored Baileys files directly in `~/.clawdbot/credentials/`.
-- Logout: `moltbot channels logout` (or `--account <id>`) deletes WhatsApp auth state (but keeps shared `oauth.json`).
+- Legacy compatibility: older installs stored Baileys files directly in `~/.openclaw/credentials/`.
+- Logout: `openclaw channels logout` (or `--account <id>`) deletes WhatsApp auth state (but keeps shared `oauth.json`).
 - Logged-out socket => error instructs re-link.
 
 ## Inbound flow (DM + group)
@@ -123,12 +123,12 @@ the prefix (use `""` to remove it).
 - Status/broadcast chats are ignored.
 - Direct chats use E.164; groups use group JID.
 - **DM policy**: `channels.whatsapp.dmPolicy` controls direct chat access (default: `pairing`).
-  - Pairing: unknown senders get a pairing code (approve via `moltbot pairing approve whatsapp <code>`; codes expire after 1 hour).
+  - Pairing: unknown senders get a pairing code (approve via `openclaw pairing approve whatsapp <code>`; codes expire after 1 hour).
   - Open: requires `channels.whatsapp.allowFrom` to include `"*"`.
-  - Self messages are always allowed; “self-chat mode” still requires `channels.whatsapp.allowFrom` to include your own number.
+  - Your linked WhatsApp number is implicitly trusted, so self messages skip ⁠`channels.whatsapp.dmPolicy` and `channels.whatsapp.allowFrom` checks.
 
 ### Personal-number mode (fallback)
-If you run Moltbot on your **personal WhatsApp number**, enable `channels.whatsapp.selfChatMode` (see sample above).
+If you run OpenClaw on your **personal WhatsApp number**, enable `channels.whatsapp.selfChatMode` (see sample above).
 
 Behavior:
 - Outbound DMs never trigger pairing replies (prevents spamming contacts).
@@ -164,16 +164,16 @@ Notes:
 
 ## WhatsApp FAQ: sending messages + pairing
 
-**Will Moltbot message random contacts when I link WhatsApp?**  
-No. Default DM policy is **pairing**, so unknown senders only get a pairing code and their message is **not processed**. Moltbot only replies to chats it receives, or to sends you explicitly trigger (agent/CLI).
+**Will OpenClaw message random contacts when I link WhatsApp?**  
+No. Default DM policy is **pairing**, so unknown senders only get a pairing code and their message is **not processed**. OpenClaw only replies to chats it receives, or to sends you explicitly trigger (agent/CLI).
 
 **How does pairing work on WhatsApp?**  
 Pairing is a DM gate for unknown senders:
 - First DM from a new sender returns a short code (message is not processed).
-- Approve with: `moltbot pairing approve whatsapp <code>` (list with `moltbot pairing list whatsapp`).
+- Approve with: `openclaw pairing approve whatsapp <code>` (list with `openclaw pairing list whatsapp`).
 - Codes expire after 1 hour; pending requests are capped at 3 per channel.
 
-**Can multiple people use different Moltbots on one WhatsApp number?**  
+**Can multiple people use different OpenClaw instances on one WhatsApp number?**  
 Yes, by routing each sender to a different agent via `bindings` (peer `kind: "dm"`, sender E.164 like `+15551234567`). Replies still come from the **same WhatsApp account**, and direct chats collapse to each agent’s main session, so use **one agent per person**. DM access control (`dmPolicy`/`allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent).
 
 **Why do you ask for my phone number in the wizard?**  
@@ -284,12 +284,12 @@ WhatsApp can automatically send emoji reactions to incoming messages immediately
   - Caption only on first media item.
   - Media fetch supports HTTP(S) and local paths.
   - Animated GIFs: WhatsApp expects MP4 with `gifPlayback: true` for inline looping.
-    - CLI: `moltbot message send --media <mp4> --gif-playback`
+    - CLI: `openclaw message send --media <mp4> --gif-playback`
     - Gateway: `send` params include `gifPlayback: true`
 
 ## Voice notes (PTT audio)
 WhatsApp sends audio as **voice notes** (PTT bubble).
-- Best results: OGG/Opus. Moltbot rewrites `audio/ogg` to `audio/ogg; codecs=opus`.
+- Best results: OGG/Opus. OpenClaw rewrites `audio/ogg` to `audio/ogg; codecs=opus`.
 - `[[audio_as_voice]]` is ignored for WhatsApp (audio already ships as voice note).
 
 ## Media limits + optimization
@@ -344,18 +344,18 @@ WhatsApp sends audio as **voice notes** (PTT bubble).
 
 ## Logs + troubleshooting
 - Subsystems: `whatsapp/inbound`, `whatsapp/outbound`, `web-heartbeat`, `web-reconnect`.
-- Log file: `/tmp/moltbot/moltbot-YYYY-MM-DD.log` (configurable).
+- Log file: `/tmp/openclaw/openclaw-YYYY-MM-DD.log` (configurable).
 - Troubleshooting guide: [Gateway troubleshooting](/gateway/troubleshooting).
 
 ## Troubleshooting (quick)
 
 **Not linked / QR login required**
 - Symptom: `channels status` shows `linked: false` or warns “Not linked”.
-- Fix: run `moltbot channels login` on the gateway host and scan the QR (WhatsApp → Settings → Linked Devices).
+- Fix: run `openclaw channels login` on the gateway host and scan the QR (WhatsApp → Settings → Linked Devices).
 
 **Linked but disconnected / reconnect loop**
 - Symptom: `channels status` shows `running, disconnected` or warns “Linked but disconnected”.
-- Fix: `moltbot doctor` (or restart the gateway). If it persists, relink via `channels login` and inspect `moltbot logs --follow`.
+- Fix: `openclaw doctor` (or restart the gateway). If it persists, relink via `channels login` and inspect `openclaw logs --follow`.
 
 **Bun runtime**
 - Bun is **not recommended**. WhatsApp (Baileys) and Telegram are unreliable on Bun.

package/docs/channels/zalo.md

@@ -9,14 +9,14 @@ Status: experimental. Direct messages only; groups coming soon per Zalo docs.
 
 ## Plugin required
 Zalo ships as a plugin and is not bundled with the core install.
-- Install via CLI: `moltbot plugins install @moltbot/zalo`
+- Install via CLI: `openclaw plugins install @openclaw/zalo`
 - Or select **Zalo** during onboarding and confirm the install prompt
 - Details: [Plugins](/plugin)
 
 ## Quick setup (beginner)
 1) Install the Zalo plugin:
-   - From a source checkout: `moltbot plugins install ./extensions/zalo`
-   - From npm (if published): `moltbot plugins install @moltbot/zalo`
+   - From a source checkout: `openclaw plugins install ./extensions/zalo`
+   - From npm (if published): `openclaw plugins install @openclaw/zalo`
    - Or pick **Zalo** in onboarding and confirm the install prompt
 2) Set the token:
    - Env: `ZALO_BOT_TOKEN=...`
@@ -89,8 +89,8 @@ Multi-account support: use `channels.zalo.accounts` with per-account tokens and
 ### DM access
 - Default: `channels.zalo.dmPolicy = "pairing"`. Unknown senders receive a pairing code; messages are ignored until approved (codes expire after 1 hour).
 - Approve via:
-  - `moltbot pairing list zalo`
-  - `moltbot pairing approve zalo <CODE>`
+  - `openclaw pairing list zalo`
+  - `openclaw pairing approve zalo <CODE>`
 - Pairing is the default token exchange. Details: [Pairing](/start/pairing)
 - `channels.zalo.allowFrom` accepts numeric user IDs (no username lookup available).
 
@@ -124,14 +124,14 @@ Multi-account support: use `channels.zalo.accounts` with per-account tokens and
 
 ## Delivery targets (CLI/cron)
 - Use a chat id as the target.
-- Example: `moltbot message send --channel zalo --target 123456789 --message "hi"`.
+- Example: `openclaw message send --channel zalo --target 123456789 --message "hi"`.
 
 ## Troubleshooting
 
 **Bot doesn't respond:**
-- Check that the token is valid: `moltbot channels status --probe`
+- Check that the token is valid: `openclaw channels status --probe`
 - Verify the sender is approved (pairing or allowFrom)
-- Check gateway logs: `moltbot logs --follow`
+- Check gateway logs: `openclaw logs --follow`
 
 **Webhook not receiving events:**
 - Ensure webhook URL uses HTTPS

package/docs/channels/zalouser.md

@@ -1,7 +1,7 @@
 ---
 summary: "Zalo personal account support via zca-cli (QR login), capabilities, and configuration"
 read_when:
-  - Setting up Zalo Personal for Moltbot
+  - Setting up Zalo Personal for OpenClaw
   - Debugging Zalo Personal login or message flow
 ---
 # Zalo Personal (unofficial)
@@ -12,8 +12,8 @@ Status: experimental. This integration automates a **personal Zalo account** via
 
 ## Plugin required
 Zalo Personal ships as a plugin and is not bundled with the core install.
-- Install via CLI: `moltbot plugins install @moltbot/zalouser`
-- Or from a source checkout: `moltbot plugins install ./extensions/zalouser`
+- Install via CLI: `openclaw plugins install @openclaw/zalouser`
+- Or from a source checkout: `openclaw plugins install ./extensions/zalouser`
 - Details: [Plugins](/plugin)
 
 ## Prerequisite: zca-cli
@@ -25,7 +25,7 @@ The Gateway machine must have the `zca` binary available in `PATH`.
 ## Quick setup (beginner)
 1) Install the plugin (see above).
 2) Login (QR, on the Gateway machine):
-   - `moltbot channels login --channel zalouser`
+   - `openclaw channels login --channel zalouser`
    - Scan the QR code in the terminal with the Zalo mobile app.
 3) Enable the channel:
 
@@ -55,9 +55,9 @@ Channel id is `zalouser` to make it explicit this automates a **personal Zalo us
 Use the directory CLI to discover peers/groups and their IDs:
 
 ```bash
-moltbot directory self --channel zalouser
-moltbot directory peers list --channel zalouser --query "name"
-moltbot directory groups list --channel zalouser --query "work"
+openclaw directory self --channel zalouser
+openclaw directory peers list --channel zalouser --query "name"
+openclaw directory groups list --channel zalouser --query "work"
 ```
 
 ## Limits
@@ -69,8 +69,8 @@ moltbot directory groups list --channel zalouser --query "work"
 `channels.zalouser.allowFrom` accepts user IDs or names. The wizard resolves names to IDs via `zca friend find` when available.
 
 Approve via:
-- `moltbot pairing list zalouser`
-- `moltbot pairing approve zalouser <code>`
+- `openclaw pairing list zalouser`
+- `openclaw pairing approve zalouser <code>`
 
 ## Group access (optional)
 - Default: `channels.zalouser.groupPolicy = "open"` (groups allowed). Use `channels.defaults.groupPolicy` to override the default when unset.
@@ -79,7 +79,7 @@ Approve via:
   - `channels.zalouser.groups` (keys are group IDs or names)
 - Block all groups: `channels.zalouser.groupPolicy = "disabled"`.
 - The configure wizard can prompt for group allowlists.
-- On startup, Moltbot resolves group/user names in allowlists to IDs and logs the mapping; unresolved entries are kept as typed.
+- On startup, OpenClaw resolves group/user names in allowlists to IDs and logs the mapping; unresolved entries are kept as typed.
 
 Example:
 ```json5
@@ -119,5 +119,5 @@ Accounts map to zca profiles. Example:
 - Install zca-cli and ensure it’s on `PATH` for the Gateway process.
 
 **Login doesn’t stick:**
-- `moltbot channels status --probe`
-- Re-login: `moltbot channels logout --channel zalouser && moltbot channels login --channel zalouser`
+- `openclaw channels status --probe`
+- Re-login: `openclaw channels logout --channel zalouser && openclaw channels login --channel zalouser`

package/docs/cli/acp.md

@@ -7,7 +7,7 @@ read_when:
 
 # acp
 
-Run the ACP (Agent Client Protocol) bridge that talks to a Moltbot Gateway.
+Run the ACP (Agent Client Protocol) bridge that talks to a OpenClaw Gateway.
 
 This command speaks ACP over stdio for IDEs and forwards prompts to the Gateway
 over WebSocket. It keeps ACP sessions mapped to Gateway session keys.
@@ -15,19 +15,19 @@ over WebSocket. It keeps ACP sessions mapped to Gateway session keys.
 ## Usage
 
 ```bash
-moltbot acp
+openclaw acp
 
 # Remote Gateway
-moltbot acp --url wss://gateway-host:18789 --token <token>
+openclaw acp --url wss://gateway-host:18789 --token <token>
 
 # Attach to an existing session key
-moltbot acp --session agent:main:main
+openclaw acp --session agent:main:main
 
 # Attach by label (must already exist)
-moltbot acp --session-label "support inbox"
+openclaw acp --session-label "support inbox"
 
 # Reset the session key before the first prompt
-moltbot acp --session agent:main:main --reset-session
+openclaw acp --session agent:main:main --reset-session
 ```
 
 ## ACP client (debug)
@@ -36,35 +36,35 @@ Use the built-in ACP client to sanity-check the bridge without an IDE.
 It spawns the ACP bridge and lets you type prompts interactively.
 
 ```bash
-moltbot acp client
+openclaw acp client
 
 # Point the spawned bridge at a remote Gateway
-moltbot acp client --server-args --url wss://gateway-host:18789 --token <token>
+openclaw acp client --server-args --url wss://gateway-host:18789 --token <token>
 
-# Override the server command (default: moltbot)
-moltbot acp client --server "node" --server-args dist/entry.js acp --url ws://127.0.0.1:19001
+# Override the server command (default: openclaw)
+openclaw acp client --server "node" --server-args openclaw.mjs acp --url ws://127.0.0.1:19001
 ```
 
 ## How to use this
 
 Use ACP when an IDE (or other client) speaks Agent Client Protocol and you want
-it to drive a Moltbot Gateway session.
+it to drive a OpenClaw Gateway session.
 
 1. Ensure the Gateway is running (local or remote).
 2. Configure the Gateway target (config or flags).
-3. Point your IDE to run `moltbot acp` over stdio.
+3. Point your IDE to run `openclaw acp` over stdio.
 
 Example config (persisted):
 
 ```bash
-moltbot config set gateway.remote.url wss://gateway-host:18789
-moltbot config set gateway.remote.token <token>
+openclaw config set gateway.remote.url wss://gateway-host:18789
+openclaw config set gateway.remote.token <token>
 ```
 
 Example direct run (no config write):
 
 ```bash
-moltbot acp --url wss://gateway-host:18789 --token <token>
+openclaw acp --url wss://gateway-host:18789 --token <token>
 ```
 
 ## Selecting agents
@@ -74,9 +74,9 @@ ACP does not pick agents directly. It routes by the Gateway session key.
 Use agent-scoped session keys to target a specific agent:
 
 ```bash
-moltbot acp --session agent:main:main
-moltbot acp --session agent:design:main
-moltbot acp --session agent:qa:bug-123
+openclaw acp --session agent:main:main
+openclaw acp --session agent:design:main
+openclaw acp --session agent:qa:bug-123
 ```
 
 Each ACP session maps to a single Gateway session key. One agent can have many
@@ -90,9 +90,9 @@ Add a custom ACP agent in `~/.config/zed/settings.json` (or use Zed’s Settings
 ```json
 {
   "agent_servers": {
-    "Moltbot ACP": {
+    "OpenClaw ACP": {
       "type": "custom",
-      "command": "moltbot",
+      "command": "openclaw",
       "args": ["acp"],
       "env": {}
     }
@@ -105,9 +105,9 @@ To target a specific Gateway or agent:
 ```json
 {
   "agent_servers": {
-    "Moltbot ACP": {
+    "OpenClaw ACP": {
       "type": "custom",
-      "command": "moltbot",
+      "command": "openclaw",
       "args": [
         "acp",
         "--url", "wss://gateway-host:18789",
@@ -120,7 +120,7 @@ To target a specific Gateway or agent:
 }
 ```
 
-In Zed, open the Agent panel and select “Moltbot ACP” to start a thread.
+In Zed, open the Agent panel and select “OpenClaw ACP” to start a thread.
 
 ## Session mapping
 
@@ -160,7 +160,7 @@ Learn more about session keys at [/concepts/session](/concepts/session).
 ### `acp client` options
 
 - `--cwd <dir>`: working directory for the ACP session.
-- `--server <command>`: ACP server command (default: `moltbot`).
+- `--server <command>`: ACP server command (default: `openclaw`).
 - `--server-args <args...>`: extra arguments passed to the ACP server.
 - `--server-verbose`: enable verbose logging on the ACP server.
 - `--verbose, -v`: verbose client logging.

package/docs/cli/agent.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `moltbot agent` (send one agent turn via the Gateway)"
+summary: "CLI reference for `openclaw agent` (send one agent turn via the Gateway)"
 read_when:
   - You want to run one agent turn from scripts (optionally deliver reply)
 ---
 
-# `moltbot agent`
+# `openclaw agent`
 
 Run an agent turn via the Gateway (use `--local` for embedded).
 Use `--agent <id>` to target a configured agent directly.
@@ -15,8 +15,8 @@ Related:
 ## Examples
 
 ```bash
-moltbot agent --to +15555550123 --message "status update" --deliver
-moltbot agent --agent ops --message "Summarize logs"
-moltbot agent --session-id 1234 --message "Summarize inbox" --thinking medium
-moltbot agent --agent ops --message "Generate report" --deliver --reply-channel slack --reply-to "#reports"
+openclaw agent --to +15555550123 --message "status update" --deliver
+openclaw agent --agent ops --message "Summarize logs"
+openclaw agent --session-id 1234 --message "Summarize inbox" --thinking medium
+openclaw agent --agent ops --message "Generate report" --deliver --reply-channel slack --reply-to "#reports"
 ```

package/docs/cli/agents.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `moltbot agents` (list/add/delete/set identity)"
+summary: "CLI reference for `openclaw agents` (list/add/delete/set identity)"
 read_when:
   - You want multiple isolated agents (workspaces + routing + auth)
 ---
 
-# `moltbot agents`
+# `openclaw agents`
 
 Manage isolated agents (workspaces + auth + routing).
 
@@ -15,17 +15,17 @@ Related:
 ## Examples
 
 ```bash
-moltbot agents list
-moltbot agents add work --workspace ~/clawd-work
-moltbot agents set-identity --workspace ~/clawd --from-identity
-moltbot agents set-identity --agent main --avatar avatars/clawd.png
-moltbot agents delete work
+openclaw agents list
+openclaw agents add work --workspace ~/.openclaw/workspace-work
+openclaw agents set-identity --workspace ~/.openclaw/workspace --from-identity
+openclaw agents set-identity --agent main --avatar avatars/openclaw.png
+openclaw agents delete work
 ```
 
 ## Identity files
 
 Each agent workspace can include an `IDENTITY.md` at the workspace root:
-- Example path: `~/clawd/IDENTITY.md`
+- Example path: `~/.openclaw/workspace/IDENTITY.md`
 - `set-identity --from-identity` reads from the workspace root (or an explicit `--identity-file`)
 
 Avatar paths resolve relative to the workspace root.
@@ -41,13 +41,13 @@ Avatar paths resolve relative to the workspace root.
 Load from `IDENTITY.md`:
 
 ```bash
-moltbot agents set-identity --workspace ~/clawd --from-identity
+openclaw agents set-identity --workspace ~/.openclaw/workspace --from-identity
 ```
 
 Override fields explicitly:
 
 ```bash
-moltbot agents set-identity --agent main --name "Clawd" --emoji "🦞" --avatar avatars/clawd.png
+openclaw agents set-identity --agent main --name "OpenClaw" --emoji "🦞" --avatar avatars/openclaw.png
 ```
 
 Config sample:
@@ -59,10 +59,10 @@ Config sample:
       {
         id: "main",
         identity: {
-          name: "Clawd",
+          name: "OpenClaw",
           theme: "space lobster",
           emoji: "🦞",
-          avatar: "avatars/clawd.png"
+          avatar: "avatars/openclaw.png"
         }
       }
     ]