refactor: rename clawdbot to moltbot with legacy compat

2026-04-19 06:17:27 +00:00 · 2026-01-27 12:19:58 +00:00
parent 83460df96f
commit 6d16a658e5
1839 changed files with 11250 additions and 11199 deletions
--- a/docs/channels/bluebubbles.md
+++ b/docs/channels/bluebubbles.md
@@ -12,7 +12,7 @@ Status: bundled plugin that talks to the BlueBubbles macOS server over HTTP. **R
 ## Overview
 - Runs on macOS via the BlueBubbles helper app ([bluebubbles.app](https://bluebubbles.app)).
 - Recommended/tested: macOS Sequoia (15). macOS Tahoe (26) works; edit is currently broken on Tahoe, and group icon updates may report success but not sync.
- Clawdbot talks to it through its REST API (`GET /api/v1/ping`, `POST /message/text`, `POST /chat/:id/*`).
+- Moltbot talks to it through its REST API (`GET /api/v1/ping`, `POST /message/text`, `POST /chat/:id/*`).
 - Incoming messages arrive via webhooks; outgoing replies, typing indicators, read receipts, and tapbacks are REST calls.
 - Attachments and stickers are ingested as inbound media (and surfaced to the agent when possible).
 - Pairing/allowlist works the same way as other channels (`/start/pairing` etc) with `channels.bluebubbles.allowFrom` + pairing codes.
@@ -22,7 +22,7 @@ Status: bundled plugin that talks to the BlueBubbles macOS server over HTTP. **R
 ## Quick start
 1. Install the BlueBubbles server on your Mac (follow the instructions at [bluebubbles.app/install](https://bluebubbles.app/install)).
 2. In the BlueBubbles config, enable the web API and set a password.
-3. Run `clawdbot onboard` and select BlueBubbles, or configure manually:
+3. Run `moltbot onboard` and select BlueBubbles, or configure manually:
   ```json5
   {
     channels: {
@@ -41,7 +41,7 @@ Status: bundled plugin that talks to the BlueBubbles macOS server over HTTP. **R
 ## Onboarding
 BlueBubbles is available in the interactive setup wizard:
 ```
-clawdbot onboard
+moltbot onboard
 ```

 The wizard prompts for:
@@ -53,7 +53,7 @@ The wizard prompts for:

 You can also add BlueBubbles via CLI:
 ```
-clawdbot channels add bluebubbles --http-url http://192.168.1.100:1234 --password <password>
+moltbot channels add bluebubbles --http-url http://192.168.1.100:1234 --password <password>
 ```

 ## Access control (DMs + groups)
@@ -61,8 +61,8 @@ DMs:
 - Default: `channels.bluebubbles.dmPolicy = "pairing"`.
 - Unknown senders receive a pairing code; messages are ignored until approved (codes expire after 1 hour).
 - Approve via:
-  - `clawdbot pairing list bluebubbles`
-  - `clawdbot pairing approve bluebubbles <CODE>`
+  - `moltbot pairing list bluebubbles`
+  - `moltbot pairing approve bluebubbles <CODE>`
 - Pairing is the default token exchange. Details: [Pairing](/start/pairing)

 Groups:
@@ -99,7 +99,7 @@ Per-group configuration:
 ## Typing + read receipts
 - **Typing indicators**: Sent automatically before and during response generation.
 - **Read receipts**: Controlled by `channels.bluebubbles.sendReadReceipts` (default: `true`).
- **Typing indicators**: Clawdbot sends typing start events; BlueBubbles clears typing automatically on send or timeout (manual stop via DELETE is unreliable).
+- **Typing indicators**: Moltbot sends typing start events; BlueBubbles clears typing automatically on send or timeout (manual stop via DELETE is unreliable).

 ```json5
 {
@@ -151,7 +151,7 @@ Available actions:
  - Voice memos: set `asVoice: true` with **MP3** or **CAF** audio to send as an iMessage voice message. BlueBubbles converts MP3 → CAF when sending voice memos.

 ### Message IDs (short vs full)
-Clawdbot may surface *short* message IDs (e.g., `1`, `2`) to save tokens.
+Moltbot may surface *short* message IDs (e.g., `1`, `2`) to save tokens.
 - `MessageSid` / `ReplyToId` can be short IDs.
 - `MessageSidFull` / `ReplyToIdFull` contain the provider full IDs.
 - Short IDs are in-memory; they can expire on restart or cache eviction.
@@ -213,7 +213,7 @@ Prefer `chat_guid` for stable routing:
 - `chat_id:123`
 - `chat_identifier:...`
 - Direct handles: `+15555550123`, `user@example.com`
-  - If a direct handle does not have an existing DM chat, Clawdbot will create one via `POST /api/v1/chat/new`. This requires the BlueBubbles Private API to be enabled.
+  - If a direct handle does not have an existing DM chat, Moltbot will create one via `POST /api/v1/chat/new`. This requires the BlueBubbles Private API to be enabled.

 ## Security
 - Webhook requests are authenticated by comparing `guid`/`password` query params or headers against `channels.bluebubbles.password`. Requests from `localhost` are also accepted.
@@ -223,11 +223,11 @@ Prefer `chat_guid` for stable routing:

 ## Troubleshooting
 - If typing/read events stop working, check the BlueBubbles webhook logs and verify the gateway path matches `channels.bluebubbles.webhookPath`.
- Pairing codes expire after one hour; use `clawdbot pairing list bluebubbles` and `clawdbot pairing approve bluebubbles <code>`.
+- Pairing codes expire after one hour; use `moltbot pairing list bluebubbles` and `moltbot pairing approve bluebubbles <code>`.
 - Reactions require the BlueBubbles private API (`POST /api/v1/message/react`); ensure the server version exposes it.
 - Edit/unsend require macOS 13+ and a compatible BlueBubbles server version. On macOS 26 (Tahoe), edit is currently broken due to private API changes.
 - Group icon updates can be flaky on macOS 26 (Tahoe): the API may return success but the new icon does not sync.
- Clawdbot auto-hides known-broken actions based on the BlueBubbles server's macOS version. If edit still appears on macOS 26 (Tahoe), disable it manually with `channels.bluebubbles.actions.edit=false`.
- For status/health info: `clawdbot status --all` or `clawdbot status --deep`.
+- Moltbot auto-hides known-broken actions based on the BlueBubbles server's macOS version. If edit still appears on macOS 26 (Tahoe), disable it manually with `channels.bluebubbles.actions.edit=false`.
+- For status/health info: `moltbot status --all` or `moltbot status --deep`.

 For general channel workflow reference, see [Channels](/channels) and the [Plugins](/plugins) guide.
--- a/docs/channels/discord.md
+++ b/docs/channels/discord.md
@@ -11,7 +11,7 @@ Status: ready for DM and guild text channels via the official Discord bot gatewa
 ## Quick setup (beginner)
 1) Create a Discord bot and copy the bot token.
 2) In the Discord app settings, enable **Message Content Intent** (and **Server Members Intent** if you plan to use allowlists or name lookups).
-3) Set the token for Clawdbot:
+3) Set the token for Moltbot:
   - Env: `DISCORD_BOT_TOKEN=...`
   - Or config: `channels.discord.token: "..."`.
   - If both are set, config takes precedence (env fallback is default-account only).
@@ -32,7 +32,7 @@ Minimal config:
 ```

 ## Goals
- Talk to Clawdbot via Discord DMs or guild channels.
+- Talk to Moltbot via Discord DMs or guild channels.
 - Direct chats collapse into the agent's main session (default `agent:main:main`); guild channels stay isolated as `agent:<agentId>:discord:channel:<channelId>` (display names use `discord:<guildSlug>#<channelSlug>`).
 - Group DMs are ignored by default; enable via `channels.discord.dm.groupEnabled` and optionally restrict by `channels.discord.dm.groupChannels`.
 - Keep routing deterministic: replies always go back to the channel they arrived on.
@@ -40,12 +40,12 @@ Minimal config:
 ## How it works
 1. Create a Discord application → Bot, enable the intents you need (DMs + guild messages + message content), and grab the bot token.
 2. Invite the bot to your server with the permissions required to read/send messages where you want to use it.
-3. Configure Clawdbot with `channels.discord.token` (or `DISCORD_BOT_TOKEN` as a fallback).
+3. Configure Moltbot with `channels.discord.token` (or `DISCORD_BOT_TOKEN` as a fallback).
 4. Run the gateway; it auto-starts the Discord channel when a token is available (config first, env fallback) and `channels.discord.enabled` is not `false`.
   - If you prefer env vars, set `DISCORD_BOT_TOKEN` (a config block is optional).
 5. Direct chats: use `user:<id>` (or a `<@id>` mention) when delivering; all turns land in the shared `main` session. Bare numeric IDs are ambiguous and rejected.
 6. Guild channels: use `channel:<channelId>` for delivery. Mentions are required by default and can be set per guild or per channel.
-7. Direct chats: secure by default via `channels.discord.dm.policy` (default: `"pairing"`). Unknown senders get a pairing code (expires after 1 hour); approve via `clawdbot pairing approve discord <code>`.
+7. Direct chats: secure by default via `channels.discord.dm.policy` (default: `"pairing"`). Unknown senders get a pairing code (expires after 1 hour); approve via `moltbot pairing approve discord <code>`.
   - To keep old “open to anyone” behavior: set `channels.discord.dm.policy="open"` and `channels.discord.dm.allowFrom=["*"]`.
   - To hard-allowlist: set `channels.discord.dm.policy="allowlist"` and list senders in `channels.discord.dm.allowFrom`.
   - To ignore all DMs: set `channels.discord.dm.enabled=false` or `channels.discord.dm.policy="disabled"`.
@@ -75,7 +75,7 @@ Disable with:

 ## How to create your own bot

-This is the “Discord Developer Portal” setup for running Clawdbot in a server (guild) channel like `#help`.
+This is the “Discord Developer Portal” setup for running Moltbot in a server (guild) channel like `#help`.

 ### 1) Create the Discord app + bot user
 1. Discord Developer Portal → **Applications** → **New Application**
@@ -83,7 +83,7 @@ This is the “Discord Developer Portal” setup for running Clawdbot in a serve
   - **Bot** → **Add Bot**
   - Copy the **Bot Token** (this is what you put in `DISCORD_BOT_TOKEN`)

-### 2) Enable the gateway intents Clawdbot needs
+### 2) Enable the gateway intents Moltbot needs
 Discord blocks “privileged intents” unless you explicitly enable them.

 In **Bot** → **Privileged Gateway Intents**, enable:
@@ -113,7 +113,7 @@ Avoid **Administrator** unless you’re debugging and fully trust the bot.
 Copy the generated URL, open it, pick your server, and install the bot.

 ### 4) Get the ids (guild/user/channel)
-Discord uses numeric ids everywhere; Clawdbot config prefers ids.
+Discord uses numeric ids everywhere; Moltbot config prefers ids.

 1. Discord (desktop/web) → **User Settings** → **Advanced** → enable **Developer Mode**
 2. Right-click:
@@ -121,7 +121,7 @@ Discord uses numeric ids everywhere; Clawdbot config prefers ids.
   - Channel (e.g. `#help`) → **Copy Channel ID**
   - Your user → **Copy User ID**

-### 5) Configure Clawdbot
+### 5) Configure Moltbot

 #### Token
 Set the bot token via env var (recommended on servers):
@@ -187,7 +187,7 @@ Notes:
 3. If nothing happens: check **Troubleshooting** below.

 ### Troubleshooting
- First: run `clawdbot doctor` and `clawdbot channels status --probe` (actionable warnings + quick audits).
+- First: run `moltbot doctor` and `moltbot channels status --probe` (actionable warnings + quick audits).
 - **“Used disallowed intents”**: enable **Message Content Intent** (and likely **Server Members Intent**) in the Developer Portal, then restart the gateway.
 - **Bot connects but never replies in a guild channel**:
  - Missing **Message Content Intent**, or
@@ -375,13 +375,13 @@ Allowlist matching notes:
 - When `guilds.<id>.channels` is omitted, all channels in the allowlisted guild are allowed.
 - To allow **no channels**, set `channels.discord.groupPolicy: "disabled"` (or keep an empty allowlist).
 - The configure wizard accepts `Guild/Channel` names (public + private) and resolves them to IDs when possible.
- On startup, Clawdbot resolves channel/user names in allowlists to IDs (when the bot can search members)
+- On startup, Moltbot resolves channel/user names in allowlists to IDs (when the bot can search members)
  and logs the mapping; unresolved entries are kept as typed.

 Native command notes:
- The registered commands mirror Clawdbot’s chat commands.
+- The registered commands mirror Moltbot’s chat commands.
 - Native commands honor the same allowlists as DMs/guild messages (`channels.discord.dm.allowFrom`, `channels.discord.guilds`, per-channel rules).
- Slash commands may still be visible in Discord UI to users who aren’t allowlisted; Clawdbot enforces allowlists on execution and replies “not authorized”.
+- Slash commands may still be visible in Discord UI to users who aren’t allowlisted; Moltbot enforces allowlists on execution and replies “not authorized”.

 ## Tool actions
 The agent can call `discord` with actions like:
@@ -401,4 +401,4 @@ Emoji can be unicode (e.g., `✅`) or custom emoji syntax like `<:party_blob:123
 ## Safety & ops
 - Treat the bot token like a password; prefer the `DISCORD_BOT_TOKEN` env var on supervised hosts or lock down the config file permissions.
 - Only grant the bot permissions it needs (typically Read/Send Messages).
- If the bot is stuck or rate limited, restart the gateway (`clawdbot gateway --force`) after confirming no other processes own the Discord session.
+- If the bot is stuck or rate limited, restart the gateway (`moltbot gateway --force`) after confirming no other processes own the Discord session.
--- a/docs/channels/googlechat.md
+++ b/docs/channels/googlechat.md
@@ -13,7 +13,7 @@ Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only).
   - Enable the API if it is not already enabled.
 2) Create a **Service Account**:
   - Press **Create Credentials** > **Service Account**.
-   - Name it whatever you want (e.g., `clawdbot-chat`).
+   - Name it whatever you want (e.g., `moltbot-chat`).
   - Leave permissions blank (press **Continue**).
   - Leave principals with access blank (press **Done**).
 3) Create and download the **JSON Key**:
@@ -24,14 +24,14 @@ Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only).
 4) Store the downloaded JSON file on your gateway host (e.g., `~/.clawdbot/googlechat-service-account.json`).
 5) Create a Google Chat app in the [Google Cloud Console Chat Configuration](https://console.cloud.google.com/apis/api/chat.googleapis.com/hangouts-chat):
   - Fill in the **Application info**:
-     - **App name**: (e.g. `Clawdbot`)
+     - **App name**: (e.g. `Moltbot`)
     - **Avatar URL**: (e.g. `https://molt.bot/logo.png`)
     - **Description**: (e.g. `Personal AI Assistant`)
   - Enable **Interactive features**.
   - Under **Functionality**, check **Join spaces and group conversations**.
   - Under **Connection settings**, select **HTTP endpoint URL**.
   - Under **Triggers**, select **Use a common HTTP endpoint URL for all triggers** and set it to your gateway's public URL followed by `/googlechat`.
-     - *Tip: Run `clawdbot status` to find your gateway's public URL.*
+     - *Tip: Run `moltbot status` to find your gateway's public URL.*
   - Under **Visibility**, check **Make this Chat app available to specific people and groups in &lt;Your Domain&gt;**.
   - Enter your email address (e.g. `user@example.com`) in the text box.
   - Click **Save** at the bottom.
@@ -40,7 +40,7 @@ Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only).
   - Look for the **App status** section (usually near the top or bottom after saving).
   - Change the status to **Live - available to users**.
   - Click **Save** again.
-7) Configure Clawdbot with the service account path + webhook audience:
+7) Configure Moltbot with the service account path + webhook audience:
   - Env: `GOOGLE_CHAT_SERVICE_ACCOUNT_FILE=/path/to/service-account.json`
   - Or config: `channels.googlechat.serviceAccountFile: "/path/to/service-account.json"`.
 8) Set the webhook audience type + value (matches your Chat app config).
@@ -57,7 +57,7 @@ Once the gateway is running and your email is added to the visibility list:
 6) Send "Hello" to trigger the assistant!

 ## Public URL (Webhook-only)
-Google Chat webhooks require a public HTTPS endpoint. For security, **only expose the `/googlechat` path** to the internet. Keep the Clawdbot dashboard and other sensitive endpoints on your private network.
+Google Chat webhooks require a public HTTPS endpoint. For security, **only expose the `/googlechat` path** to the internet. Keep the Moltbot dashboard and other sensitive endpoints on your private network.

 ### Option A: Tailscale Funnel (Recommended)
 Use Tailscale Serve for the private dashboard and Funnel for the public webhook path. This keeps `/` private while exposing only `/googlechat`.
@@ -112,7 +112,7 @@ your-domain.com {
    reverse_proxy /googlechat* localhost:18789
 }
 ```
-With this config, any request to `your-domain.com/` will be ignored or returned as 404, while `your-domain.com/googlechat` is safely routed to Clawdbot.
+With this config, any request to `your-domain.com/` will be ignored or returned as 404, while `your-domain.com/googlechat` is safely routed to Moltbot.

 ### Option C: Cloudflare Tunnel
 Configure your tunnel's ingress rules to only route the webhook path:
@@ -122,14 +122,14 @@ Configure your tunnel's ingress rules to only route the webhook path:
 ## How it works

 1. Google Chat sends webhook POSTs to the gateway. Each request includes an `Authorization: Bearer <token>` header.
-2. Clawdbot verifies the token against the configured `audienceType` + `audience`:
+2. Moltbot verifies the token against the configured `audienceType` + `audience`:
   - `audienceType: "app-url"` → audience is your HTTPS webhook URL.
   - `audienceType: "project-number"` → audience is the Cloud project number.
 3. Messages are routed by space:
   - DMs use session key `agent:<agentId>:googlechat:dm:<spaceId>`.
   - Spaces use session key `agent:<agentId>:googlechat:group:<spaceId>`.
 4. DM access is pairing by default. Unknown senders receive a pairing code; approve with:
-   - `clawdbot pairing approve googlechat <code>`
+   - `moltbot pairing approve googlechat <code>`
 5. Group spaces require @-mention by default. Use `botUser` if mention detection needs the app’s user name.

 ## Targets
@@ -187,32 +187,32 @@ status code: 405, reason phrase: HTTP error response: HTTP/1.1 405 Method Not Al
 This means the webhook handler isn't registered. Common causes:
 1. **Channel not configured**: The `channels.googlechat` section is missing from your config. Verify with:
   ```bash
-   clawdbot config get channels.googlechat
+   moltbot config get channels.googlechat
   ```
   If it returns "Config path not found", add the configuration (see [Config highlights](#config-highlights)).

 2. **Plugin not enabled**: Check plugin status:
   ```bash
-   clawdbot plugins list | grep googlechat
+   moltbot plugins list | grep googlechat
   ```
   If it shows "disabled", add `plugins.entries.googlechat.enabled: true` to your config.

 3. **Gateway not restarted**: After adding config, restart the gateway:
   ```bash
-   clawdbot gateway restart
+   moltbot gateway restart
   ```

 Verify the channel is running:
 ```bash
-clawdbot channels status
+moltbot channels status
 # Should show: Google Chat default: enabled, configured, ...
 ```

 ### Other issues
- Check `clawdbot channels status --probe` for auth errors or missing audience config.
+- Check `moltbot channels status --probe` for auth errors or missing audience config.
 - If no messages arrive, confirm the Chat app's webhook URL + event subscriptions.
 - If mention gating blocks replies, set `botUser` to the app's user resource name and verify `requireMention`.
- Use `clawdbot logs --follow` while sending a test message to see if requests reach the gateway.
+- Use `moltbot logs --follow` while sending a test message to see if requests reach the gateway.

 Related docs:
 - [Gateway configuration](/gateway/configuration)
--- a/docs/channels/imessage.md
+++ b/docs/channels/imessage.md
@@ -13,7 +13,7 @@ Status: external CLI integration. Gateway spawns `imsg rpc` (JSON-RPC over stdio
 1) Ensure Messages is signed in on this Mac.
 2) Install `imsg`:
   - `brew install steipete/tap/imsg`
-3) Configure Clawdbot with `channels.imessage.cliPath` and `channels.imessage.dbPath`.
+3) Configure Moltbot with `channels.imessage.cliPath` and `channels.imessage.dbPath`.
 4) Start the gateway and approve any macOS prompts (Automation + Full Disk Access).

 Minimal config:
@@ -47,7 +47,7 @@ Disable with:

 ## Requirements
 - macOS with Messages signed in.
- Full Disk Access for Clawdbot + `imsg` (Messages DB access).
+- Full Disk Access for Moltbot + `imsg` (Messages DB access).
 - Automation permission when sending.
 - `channels.imessage.cliPath` can point to any command that proxies stdin/stdout (for example, a wrapper script that SSHes to another Mac and runs `imsg rpc`).

@@ -103,7 +103,7 @@ Example config:
 For single-account setups, use flat options (`channels.imessage.cliPath`, `channels.imessage.dbPath`) instead of the `accounts` map.

 ### Remote/SSH variant (optional)
-If you want iMessage on another Mac, set `channels.imessage.cliPath` to a wrapper that runs `imsg` on the remote macOS host over SSH. Clawdbot only needs stdio.
+If you want iMessage on another Mac, set `channels.imessage.cliPath` to a wrapper that runs `imsg` on the remote macOS host over SSH. Moltbot only needs stdio.

 Example wrapper:
 ```bash
@@ -111,7 +111,7 @@ Example wrapper:
 exec ssh -T gateway-host imsg "$@"
 ```

-**Remote attachments:** When `cliPath` points to a remote host via SSH, attachment paths in the Messages database reference files on the remote machine. Clawdbot can automatically fetch these over SCP by setting `channels.imessage.remoteHost`:
+**Remote attachments:** When `cliPath` points to a remote host via SSH, attachment paths in the Messages database reference files on the remote machine. Moltbot can automatically fetch these over SCP by setting `channels.imessage.remoteHost`:

 ```json5
 {
@@ -125,7 +125,7 @@ exec ssh -T gateway-host imsg "$@"
 }
 ```

-If `remoteHost` is not set, Clawdbot attempts to auto-detect it by parsing the SSH command in your wrapper script. Explicit configuration is recommended for reliability.
+If `remoteHost` is not set, Moltbot attempts to auto-detect it by parsing the SSH command in your wrapper script. Explicit configuration is recommended for reliability.

 #### Remote Mac via Tailscale (example)
 If the Gateway runs on a Linux host/VM but iMessage must run on a Mac, Tailscale is the simplest bridge: the Gateway talks to the Mac over the tailnet, runs `imsg` via SSH, and SCPs attachments back.
@@ -134,7 +134,7 @@ Architecture:
 ```
 ┌──────────────────────────────┐          SSH (imsg rpc)          ┌──────────────────────────┐
 │ Gateway host (Linux/VM)      │──────────────────────────────────▶│ Mac with Messages + imsg │
-│ - clawdbot gateway           │          SCP (attachments)        │ - Messages signed in     │
+│ - moltbot gateway           │          SCP (attachments)        │ - Messages signed in     │
 │ - channels.imessage.cliPath  │◀──────────────────────────────────│ - Remote Login enabled   │
 └──────────────────────────────┘                                   └──────────────────────────┘
              ▲
@@ -169,15 +169,15 @@ Notes:
 - Use SSH keys so `ssh bot@mac-mini.tailnet-1234.ts.net` works without prompts.
 - `remoteHost` should match the SSH target so SCP can fetch attachments.

-Multi-account support: use `channels.imessage.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern. Don't commit `~/.clawdbot/clawdbot.json` (it often contains tokens).
+Multi-account support: use `channels.imessage.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern. Don't commit `~/.clawdbot/moltbot.json` (it often contains tokens).

 ## Access control (DMs + groups)
 DMs:
 - Default: `channels.imessage.dmPolicy = "pairing"`.
 - Unknown senders receive a pairing code; messages are ignored until approved (codes expire after 1 hour).
 - Approve via:
-  - `clawdbot pairing list imessage`
-  - `clawdbot pairing approve imessage <CODE>`
+  - `moltbot pairing list imessage`
+  - `moltbot pairing approve imessage <CODE>`
 - Pairing is the default token exchange for iMessage DMs. Details: [Pairing](/start/pairing)

 Groups:
@@ -193,7 +193,7 @@ Groups:
 ## Group-ish threads (`is_group=false`)
 Some iMessage threads can have multiple participants but still arrive with `is_group=false` depending on how Messages stores the chat identifier.

-If you explicitly configure a `chat_id` under `channels.imessage.groups`, Clawdbot treats that thread as a “group” for:
+If you explicitly configure a `chat_id` under `channels.imessage.groups`, Moltbot treats that thread as a “group” for:
 - session isolation (separate `agent:<agentId>:imessage:group:<chat_id>` session key)
 - group allowlisting / mention gating behavior

--- a/docs/channels/index.md
+++ b/docs/channels/index.md
@@ -1,12 +1,12 @@
 ---
-summary: "Messaging platforms Clawdbot can connect to"
+summary: "Messaging platforms Moltbot can connect to"
 read_when:
-  - You want to choose a chat channel for Clawdbot
+  - You want to choose a chat channel for Moltbot
  - You need a quick overview of supported messaging platforms
 ---
 # Chat Channels

-Clawdbot can talk to you on any chat app you already use. Each channel connects via the Gateway.
+Moltbot can talk to you on any chat app you already use. Each channel connects via the Gateway.
 Text is supported everywhere; media and reactions vary by channel.

 ## Supported channels
@@ -33,7 +33,7 @@ Text is supported everywhere; media and reactions vary by channel.

 ## Notes

- Channels can run simultaneously; configure multiple and Clawdbot will route per chat.
+- Channels can run simultaneously; configure multiple and Moltbot will route per chat.
 - Fastest setup is usually **Telegram** (simple bot token). WhatsApp requires QR pairing and
  stores more state on disk.
 - Group behavior varies by channel; see [Groups](/concepts/groups).
--- a/docs/channels/line.md
+++ b/docs/channels/line.md
@@ -1,14 +1,14 @@
 ---
 summary: "LINE Messaging API plugin setup, config, and usage"
 read_when:
-  - You want to connect Clawdbot to LINE
+  - You want to connect Moltbot to LINE
  - You need LINE webhook + credential setup
  - You want LINE-specific message options
 ---

 # LINE (plugin)

-LINE connects to Clawdbot via the LINE Messaging API. The plugin runs as a webhook
+LINE connects to Moltbot via the LINE Messaging API. The plugin runs as a webhook
 receiver on the gateway and uses your channel access token + channel secret for
 authentication.

@@ -21,13 +21,13 @@ are not supported.
 Install the LINE plugin:

 ```bash
-clawdbot plugins install @clawdbot/line
+moltbot plugins install @moltbot/line
 ```

 Local checkout (when running from a git repo):

 ```bash
-clawdbot plugins install ./extensions/line
+moltbot plugins install ./extensions/line
 ```

 ## Setup
@@ -106,8 +106,8 @@ Direct messages default to pairing. Unknown senders get a pairing code and their
 messages are ignored until approved.

 ```bash
-clawdbot pairing list line
-clawdbot pairing approve line <CODE>
+moltbot pairing list line
+moltbot pairing approve line <CODE>
 ```

 Allowlists and policies:
--- a/docs/channels/location.md
+++ b/docs/channels/location.md
@@ -7,7 +7,7 @@ read_when:

 # Channel location parsing

-Clawdbot normalizes shared locations from chat channels into:
+Moltbot normalizes shared locations from chat channels into:
 - human-readable text appended to the inbound body, and
 - structured fields in the auto-reply context payload.

--- a/docs/channels/matrix.md
+++ b/docs/channels/matrix.md
@@ -5,7 +5,7 @@ read_when:
 ---
 # Matrix (plugin)

-Matrix is an open, decentralized messaging protocol. Clawdbot connects as a Matrix **user**
+Matrix is an open, decentralized messaging protocol. Moltbot connects as a Matrix **user**
 on any homeserver, so you need a Matrix account for the bot. Once it is logged in, you can DM
 the bot directly or invite it to rooms (Matrix "groups"). Beeper is a valid client option too,
 but it requires E2EE to be enabled.
@@ -20,25 +20,25 @@ Matrix ships as a plugin and is not bundled with the core install.
 Install via CLI (npm registry):

 ```bash
-clawdbot plugins install @clawdbot/matrix
+moltbot plugins install @moltbot/matrix
 ```

 Local checkout (when running from a git repo):

 ```bash
-clawdbot plugins install ./extensions/matrix
+moltbot plugins install ./extensions/matrix
 ```

 If you choose Matrix during configure/onboarding and a git checkout is detected,
-Clawdbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.

 Details: [Plugins](/plugin)

 ## Setup

 1) Install the Matrix plugin:
-   - From npm: `clawdbot plugins install @clawdbot/matrix`
-   - From a local checkout: `clawdbot plugins install ./extensions/matrix`
+   - From npm: `moltbot plugins install @moltbot/matrix`
+   - From a local checkout: `moltbot plugins install ./extensions/matrix`
 2) Create a Matrix account on a homeserver:
   - Browse hosting options at [https://matrix.org/ecosystem/hosting/](https://matrix.org/ecosystem/hosting/)
   - Or host it yourself.
@@ -60,7 +60,7 @@ Details: [Plugins](/plugin)
   ```

   - Replace `matrix.example.org` with your homeserver URL.
-   - Or set `channels.matrix.userId` + `channels.matrix.password`: Clawdbot calls the same
+   - Or set `channels.matrix.userId` + `channels.matrix.password`: Moltbot calls the same
     login endpoint, stores the access token in `~/.clawdbot/credentials/matrix/credentials.json`,
     and reuses it on next start.
 4) Configure credentials:
@@ -113,10 +113,10 @@ Enable with `channels.matrix.encryption: true`:

 - If the crypto module loads, encrypted rooms are decrypted automatically.
 - Outbound media is encrypted when sending to encrypted rooms.
- On first connection, Clawdbot requests device verification from your other sessions.
+- On first connection, Moltbot requests device verification from your other sessions.
 - Verify the device in another Matrix client (Element, etc.) to enable key sharing.
 - If the crypto module cannot be loaded, E2EE is disabled and encrypted rooms will not decrypt;
-  Clawdbot logs a warning.
+  Moltbot logs a warning.
 - If you see missing crypto module errors (for example, `@matrix-org/matrix-sdk-crypto-nodejs-*`),
  allow build scripts for `@matrix-org/matrix-sdk-crypto-nodejs` and run
  `pnpm rebuild @matrix-org/matrix-sdk-crypto-nodejs` or fetch the binary with
@@ -142,8 +142,8 @@ Once verified, the bot can decrypt messages in encrypted rooms.

 - Default: `channels.matrix.dm.policy = "pairing"`. Unknown senders get a pairing code.
 - Approve via:
-  - `clawdbot pairing list matrix`
-  - `clawdbot pairing approve matrix <CODE>`
+  - `moltbot pairing list matrix`
+  - `moltbot pairing approve matrix <CODE>`
 - Public DMs: `channels.matrix.dm.policy="open"` plus `channels.matrix.dm.allowFrom=["*"]`.
 - `channels.matrix.dm.allowFrom` accepts user IDs or display names. The wizard resolves display names to user IDs when directory search is available.

@@ -172,7 +172,7 @@ Once verified, the bot can decrypt messages in encrypted rooms.
 - `groupAllowFrom` restricts which senders can trigger the bot in rooms (optional).
 - Per-room `users` allowlists can further restrict senders inside a specific room.
 - The configure wizard prompts for room allowlists (room IDs, aliases, or names) and resolves names when possible.
- On startup, Clawdbot resolves room/user names in allowlists to IDs and logs the mapping; unresolved entries are kept as typed.
+- On startup, Moltbot resolves room/user names in allowlists to IDs and logs the mapping; unresolved entries are kept as typed.
 - Invites are auto-joined by default; control with `channels.matrix.autoJoin` and `channels.matrix.autoJoinAllowlist`.
 - To allow **no rooms**, set `channels.matrix.groupPolicy: "disabled"` (or keep an empty allowlist).
 - Legacy key: `channels.matrix.rooms` (same shape as `groups`).
--- a/docs/channels/mattermost.md
+++ b/docs/channels/mattermost.md
@@ -1,5 +1,5 @@
 ---
-summary: "Mattermost bot setup and Clawdbot config"
+summary: "Mattermost bot setup and Moltbot config"
 read_when:
  - Setting up Mattermost
  - Debugging Mattermost routing
@@ -16,16 +16,16 @@ Mattermost ships as a plugin and is not bundled with the core install.

 Install via CLI (npm registry):
 ```bash
-clawdbot plugins install @clawdbot/mattermost
+moltbot plugins install @moltbot/mattermost
 ```

 Local checkout (when running from a git repo):
 ```bash
-clawdbot plugins install ./extensions/mattermost
+moltbot plugins install ./extensions/mattermost
 ```

 If you choose Mattermost during configure/onboarding and a git checkout is detected,
-Clawdbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.

 Details: [Plugins](/plugin)

@@ -33,7 +33,7 @@ Details: [Plugins](/plugin)
 1) Install the Mattermost plugin.
 2) Create a Mattermost bot account and copy the **bot token**.
 3) Copy the Mattermost **base URL** (e.g., `https://chat.example.com`).
-4) Configure Clawdbot and start the gateway.
+4) Configure Moltbot and start the gateway.

 Minimal config:
 ```json5
@@ -83,8 +83,8 @@ Notes:
 ## Access control (DMs)
 - Default: `channels.mattermost.dmPolicy = "pairing"` (unknown senders get a pairing code).
 - Approve via:
-  - `clawdbot pairing list mattermost`
-  - `clawdbot pairing approve mattermost <CODE>`
+  - `moltbot pairing list mattermost`
+  - `moltbot pairing approve mattermost <CODE>`
 - Public DMs: `channels.mattermost.dmPolicy="open"` plus `channels.mattermost.allowFrom=["*"]`.

 ## Channels (groups)
@@ -93,7 +93,7 @@ Notes:
 - Open channels: `channels.mattermost.groupPolicy="open"` (mention-gated).

 ## Targets for outbound delivery
-Use these target formats with `clawdbot message send` or cron/webhooks:
+Use these target formats with `moltbot message send` or cron/webhooks:

 - `channel:<id>` for a channel
 - `user:<id>` for a DM
--- a/docs/channels/msteams.md
+++ b/docs/channels/msteams.md
@@ -21,23 +21,23 @@ Explainable: keeps core installs lighter and lets MS Teams dependencies update i

 Install via CLI (npm registry):
 ```bash
-clawdbot plugins install @clawdbot/msteams
+moltbot plugins install @moltbot/msteams
 ```

 Local checkout (when running from a git repo):
 ```bash
-clawdbot plugins install ./extensions/msteams
+moltbot plugins install ./extensions/msteams
 ```

 If you choose Teams during configure/onboarding and a git checkout is detected,
-Clawdbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.

 Details: [Plugins](/plugin)

 ## Quick setup (beginner)
 1) Install the Microsoft Teams plugin.
 2) Create an **Azure Bot** (App ID + client secret + tenant ID).
-3) Configure Clawdbot with those credentials.
+3) Configure Moltbot with those credentials.
 4) Expose `/api/messages` (port 3978 by default) via a public URL or tunnel.
 5) Install the Teams app package and start the gateway.

@@ -58,7 +58,7 @@ Minimal config:
 Note: group chats are blocked by default (`channels.msteams.groupPolicy: "allowlist"`). To allow group replies, set `channels.msteams.groupAllowFrom` (or use `groupPolicy: "open"` to allow any member, mention-gated).

 ## Goals
- Talk to Clawdbot via Teams DMs, group chats, or channels.
+- Talk to Moltbot via Teams DMs, group chats, or channels.
 - Keep routing deterministic: replies always go back to the channel they arrived on.
 - Default to safe channel behavior (mentions required unless configured otherwise).

@@ -101,7 +101,7 @@ Example:
 - Keys can be team IDs or names; channel keys can be conversation IDs or names.
 - When `groupPolicy="allowlist"` and a teams allowlist is present, only listed teams/channels are accepted (mention‑gated).
 - The configure wizard accepts `Team/Channel` entries and stores them for you.
- On startup, Clawdbot resolves team/channel and user allowlist names to IDs (when Graph permissions allow)
+- On startup, Moltbot resolves team/channel and user allowlist names to IDs (when Graph permissions allow)
  and logs the mapping; unresolved entries are kept as typed.

 Example:
@@ -127,12 +127,12 @@ Example:
 2. Create an **Azure Bot** (App ID + secret + tenant ID).
 3. Build a **Teams app package** that references the bot and includes the RSC permissions below.
 4. Upload/install the Teams app into a team (or personal scope for DMs).
-5. Configure `msteams` in `~/.clawdbot/clawdbot.json` (or env vars) and start the gateway.
+5. Configure `msteams` in `~/.clawdbot/moltbot.json` (or env vars) and start the gateway.
 6. The gateway listens for Bot Framework webhook traffic on `/api/messages` by default.

 ## Azure Bot Setup (Prerequisites)

-Before configuring Clawdbot, you need to create an Azure Bot resource.
+Before configuring Moltbot, you need to create an Azure Bot resource.

 ### Step 1: Create Azure Bot

@@ -141,7 +141,7 @@ Before configuring Clawdbot, you need to create an Azure Bot resource.

   | Field | Value |
   |-------|-------|
-   | **Bot handle** | Your bot name, e.g., `clawdbot-msteams` (must be unique) |
+   | **Bot handle** | Your bot name, e.g., `moltbot-msteams` (must be unique) |
   | **Subscription** | Select your Azure subscription |
   | **Resource group** | Create new or use existing |
   | **Pricing tier** | **Free** for dev/testing |
@@ -218,8 +218,8 @@ This is often easier than hand-editing JSON manifests.

 ## Setup (minimal text-only)
 1. **Install the Microsoft Teams plugin**
-   - From npm: `clawdbot plugins install @clawdbot/msteams`
-   - From a local checkout: `clawdbot plugins install ./extensions/msteams`
+   - From npm: `moltbot plugins install @moltbot/msteams`
+   - From a local checkout: `moltbot plugins install ./extensions/msteams`

 2. **Bot registration**
   - Create an Azure Bot (see above) and note:
@@ -235,7 +235,7 @@ This is often easier than hand-editing JSON manifests.
   - Create icons: `outline.png` (32x32) and `color.png` (192x192).
   - Zip all three files together: `manifest.json`, `outline.png`, `color.png`.

-4. **Configure Clawdbot**
+4. **Configure Moltbot**
   ```json
   {
     "msteams": {
@@ -289,14 +289,14 @@ Minimal, valid example with the required fields. Replace IDs and URLs.
  "manifestVersion": "1.23",
  "version": "1.0.0",
  "id": "00000000-0000-0000-0000-000000000000",
-  "name": { "short": "Clawdbot" },
+  "name": { "short": "Moltbot" },
  "developer": {
    "name": "Your Org",
    "websiteUrl": "https://example.com",
    "privacyUrl": "https://example.com/privacy",
    "termsOfUseUrl": "https://example.com/terms"
  },
-  "description": { "short": "Clawdbot in Teams", "full": "Clawdbot in Teams" },
+  "description": { "short": "Moltbot in Teams", "full": "Moltbot in Teams" },
  "icons": { "outline": "outline.png", "color": "color.png" },
  "accentColor": "#5B6DEF",
  "bots": [
@@ -397,7 +397,7 @@ Teams delivers messages via HTTP webhook. If processing takes too long (e.g., sl
 - Teams retrying the message (causing duplicates)
 - Dropped replies

-Clawdbot handles this by returning quickly and sending replies proactively, but very slow responses may still cause issues.
+Moltbot handles this by returning quickly and sending replies proactively, but very slow responses may still cause issues.

 ### Formatting
 Teams markdown is more limited than Slack or Discord:
@@ -475,7 +475,7 @@ Teams recently introduced two channel UI styles over the same underlying data mo
 - **Channels/groups:** Attachments live in M365 storage (SharePoint/OneDrive). The webhook payload only includes an HTML stub, not the actual file bytes. **Graph API permissions are required** to download channel attachments.

 Without Graph permissions, channel messages with images will be received as text-only (the image content is not accessible to the bot).
-By default, Clawdbot only downloads media from Microsoft/Teams hostnames. Override with `channels.msteams.mediaAllowHosts` (use `["*"]` to allow any host).
+By default, Moltbot only downloads media from Microsoft/Teams hostnames. Override with `channels.msteams.mediaAllowHosts` (use `["*"]` to allow any host).

 ## Sending files in group chats

@@ -512,7 +512,7 @@ Bots don't have a personal OneDrive drive (the `/me/drive` Graph API endpoint do
   # Response includes: "id": "contoso.sharepoint.com,guid1,guid2"
   ```

-4. **Configure Clawdbot:**
+4. **Configure Moltbot:**
   ```json5
   {
     channels: {
@@ -544,12 +544,12 @@ Per-user sharing is more secure as only the chat participants can access the fil

 ### Files stored location

-Uploaded files are stored in a `/ClawdbotShared/` folder in the configured SharePoint site's default document library.
+Uploaded files are stored in a `/MoltbotShared/` folder in the configured SharePoint site's default document library.

 ## Polls (Adaptive Cards)
-Clawdbot sends Teams polls as Adaptive Cards (there is no native Teams poll API).
+Moltbot sends Teams polls as Adaptive Cards (there is no native Teams poll API).

- CLI: `clawdbot message poll --channel msteams --target conversation:<id> ...`
+- CLI: `moltbot message poll --channel msteams --target conversation:<id> ...`
 - Votes are recorded by the gateway in `~/.clawdbot/msteams-polls.json`.
 - The gateway must stay online to record votes.
 - Polls do not auto-post result summaries yet (inspect the store file if needed).
@@ -575,7 +575,7 @@ The `card` parameter accepts an Adaptive Card JSON object. When `card` is provid

 **CLI:**
 ```bash
-clawdbot message send --channel msteams \
+moltbot message send --channel msteams \
  --target "conversation:19:abc...@thread.tacv2" \
  --card '{"type":"AdaptiveCard","version":"1.5","body":[{"type":"TextBlock","text":"Hello!"}]}'
 ```
@@ -596,16 +596,16 @@ MSTeams targets use prefixes to distinguish between users and conversations:
 **CLI examples:**
 ```bash
 # Send to a user by ID
-clawdbot message send --channel msteams --target "user:40a1a0ed-..." --message "Hello"
+moltbot message send --channel msteams --target "user:40a1a0ed-..." --message "Hello"

 # Send to a user by display name (triggers Graph API lookup)
-clawdbot message send --channel msteams --target "user:John Smith" --message "Hello"
+moltbot message send --channel msteams --target "user:John Smith" --message "Hello"

 # Send to a group chat or channel
-clawdbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" --message "Hello"
+moltbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" --message "Hello"

 # Send an Adaptive Card to a conversation
-clawdbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" \
+moltbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" \
  --card '{"type":"AdaptiveCard","version":"1.5","body":[{"type":"TextBlock","text":"Hello"}]}'
 ```

--- a/docs/channels/nextcloud-talk.md
+++ b/docs/channels/nextcloud-talk.md
@@ -12,16 +12,16 @@ Nextcloud Talk ships as a plugin and is not bundled with the core install.

 Install via CLI (npm registry):
 ```bash
-clawdbot plugins install @clawdbot/nextcloud-talk
+moltbot plugins install @moltbot/nextcloud-talk
 ```

 Local checkout (when running from a git repo):
 ```bash
-clawdbot plugins install ./extensions/nextcloud-talk
+moltbot plugins install ./extensions/nextcloud-talk
 ```

 If you choose Nextcloud Talk during configure/onboarding and a git checkout is detected,
-Clawdbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.

 Details: [Plugins](/plugin)

@@ -29,10 +29,10 @@ Details: [Plugins](/plugin)
 1) Install the Nextcloud Talk plugin.
 2) On your Nextcloud server, create a bot:
   ```bash
-   ./occ talk:bot:install "Clawdbot" "<shared-secret>" "<webhook-url>" --feature reaction
+   ./occ talk:bot:install "Moltbot" "<shared-secret>" "<webhook-url>" --feature reaction
   ```
 3) Enable the bot in the target room settings.
-4) Configure Clawdbot:
+4) Configure Moltbot:
   - Config: `channels.nextcloud-talk.baseUrl` + `channels.nextcloud-talk.botSecret`
   - Or env: `NEXTCLOUD_TALK_BOT_SECRET` (default account only)
 5) Restart the gateway (or finish onboarding).
@@ -60,8 +60,8 @@ Minimal config:
 ## Access control (DMs)
 - Default: `channels.nextcloud-talk.dmPolicy = "pairing"`. Unknown senders get a pairing code.
 - Approve via:
-  - `clawdbot pairing list nextcloud-talk`
-  - `clawdbot pairing approve nextcloud-talk <CODE>`
+  - `moltbot pairing list nextcloud-talk`
+  - `moltbot pairing approve nextcloud-talk <CODE>`
 - Public DMs: `channels.nextcloud-talk.dmPolicy="open"` plus `channels.nextcloud-talk.allowFrom=["*"]`.

 ## Rooms (groups)
--- a/docs/channels/nostr.md
+++ b/docs/channels/nostr.md
@@ -1,20 +1,20 @@
 ---
 summary: "Nostr DM channel via NIP-04 encrypted messages"
 read_when:
-  - You want Clawdbot to receive DMs via Nostr
+  - You want Moltbot to receive DMs via Nostr
  - You're setting up decentralized messaging
 ---
 # Nostr

 **Status:** Optional plugin (disabled by default).

-Nostr is a decentralized protocol for social networking. This channel enables Clawdbot to receive and respond to encrypted direct messages (DMs) via NIP-04.
+Nostr is a decentralized protocol for social networking. This channel enables Moltbot to receive and respond to encrypted direct messages (DMs) via NIP-04.

 ## Install (on demand)

 ### Onboarding (recommended)

- The onboarding wizard (`clawdbot onboard`) and `clawdbot channels add` list optional channel plugins.
+- The onboarding wizard (`moltbot onboard`) and `moltbot channels add` list optional channel plugins.
 - Selecting Nostr prompts you to install the plugin on demand.

 Install defaults:
@@ -27,13 +27,13 @@ You can always override the choice in the prompt.
 ### Manual install

 ```bash
-clawdbot plugins install @clawdbot/nostr
+moltbot plugins install @moltbot/nostr
 ```

 Use a local checkout (dev workflows):

 ```bash
-clawdbot plugins install --link <path-to-clawdbot>/extensions/nostr
+moltbot plugins install --link <path-to-moltbot>/extensions/nostr
 ```

 Restart the Gateway after installing or enabling plugins.
@@ -91,14 +91,14 @@ Example:
    "nostr": {
      "privateKey": "${NOSTR_PRIVATE_KEY}",
      "profile": {
-        "name": "clawdbot",
-        "displayName": "Clawdbot",
+        "name": "moltbot",
+        "displayName": "Moltbot",
        "about": "Personal assistant DM bot",
        "picture": "https://example.com/avatar.png",
        "banner": "https://example.com/banner.png",
        "website": "https://example.com",
-        "nip05": "clawdbot@example.com",
-        "lud16": "clawdbot@example.com"
+        "nip05": "moltbot@example.com",
+        "lud16": "moltbot@example.com"
      }
    }
  }
--- a/docs/channels/signal.md
+++ b/docs/channels/signal.md
@@ -13,8 +13,8 @@ Status: external CLI integration. Gateway talks to `signal-cli` over HTTP JSON-R
 1) Use a **separate Signal number** for the bot (recommended).
 2) Install `signal-cli` (Java required).
 3) Link the bot device and start the daemon:
-   - `signal-cli link -n "Clawdbot"`
-4) Configure Clawdbot and start the gateway.
+   - `signal-cli link -n "Moltbot"`
+4) Configure Moltbot and start the gateway.

 Minimal config:
 ```json5
@@ -54,7 +54,7 @@ Disable with:
 ## Setup (fast path)
 1) Install `signal-cli` (Java required).
 2) Link a bot account:
-   - `signal-cli link -n "Clawdbot"` then scan the QR in Signal.
+   - `signal-cli link -n "Moltbot"` then scan the QR in Signal.
 3) Configure Signal and start the gateway.

 Example:
@@ -75,7 +75,7 @@ Example:
 Multi-account support: use `channels.signal.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern.

 ## External daemon mode (httpUrl)
-If you want to manage `signal-cli` yourself (slow JVM cold starts, container init, or shared CPUs), run the daemon separately and point Clawdbot at it:
+If you want to manage `signal-cli` yourself (slow JVM cold starts, container init, or shared CPUs), run the daemon separately and point Moltbot at it:

 ```json5
 {
@@ -88,15 +88,15 @@ If you want to manage `signal-cli` yourself (slow JVM cold starts, container ini
 }
 ```

-This skips auto-spawn and the startup wait inside Clawdbot. For slow starts when auto-spawning, set `channels.signal.startupTimeoutMs`.
+This skips auto-spawn and the startup wait inside Moltbot. For slow starts when auto-spawning, set `channels.signal.startupTimeoutMs`.

 ## Access control (DMs + groups)
 DMs:
 - Default: `channels.signal.dmPolicy = "pairing"`.
 - Unknown senders receive a pairing code; messages are ignored until approved (codes expire after 1 hour).
 - Approve via:
-  - `clawdbot pairing list signal`
-  - `clawdbot pairing approve signal <CODE>`
+  - `moltbot pairing list signal`
+  - `moltbot pairing approve signal <CODE>`
 - Pairing is the default token exchange for Signal DMs. Details: [Pairing](/start/pairing)
 - UUID-only senders (from `sourceUuid`) are stored as `uuid:<id>` in `channels.signal.allowFrom`.

@@ -118,8 +118,8 @@ Groups:
 - Group history context uses `channels.signal.historyLimit` (or `channels.signal.accounts.*.historyLimit`), falling back to `messages.groupChat.historyLimit`. Set `0` to disable (default 50).

 ## Typing + read receipts
- **Typing indicators**: Clawdbot sends typing signals via `signal-cli sendTyping` and refreshes them while a reply is running.
- **Read receipts**: when `channels.signal.sendReadReceipts` is true, Clawdbot forwards read receipts for allowed DMs.
+- **Typing indicators**: Moltbot sends typing signals via `signal-cli sendTyping` and refreshes them while a reply is running.
+- **Read receipts**: when `channels.signal.sendReadReceipts` is true, Moltbot forwards read receipts for allowed DMs.
 - Signal-cli does not expose read receipts for groups.

 ## Reactions (message tool)
--- a/docs/channels/slack.md
+++ b/docs/channels/slack.md
@@ -10,7 +10,7 @@ read_when: "Setting up Slack or debugging Slack socket/HTTP mode"
 ### Quick setup (beginner)
 1) Create a Slack app and enable **Socket Mode**.
 2) Create an **App Token** (`xapp-...`) and **Bot Token** (`xoxb-...`).
-3) Set tokens for Clawdbot and start the gateway.
+3) Set tokens for Moltbot and start the gateway.

 Minimal config:
 ```json5
@@ -45,7 +45,7 @@ Use the manifest below so scopes and events stay in sync.

 Multi-account support: use `channels.slack.accounts` with per-account tokens and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern.

-### Clawdbot config (minimal)
+### Moltbot config (minimal)

 Set tokens via env vars (recommended):
 - `SLACK_APP_TOKEN=xapp-...`
@@ -66,7 +66,7 @@ Or via config:
 ```

 ### User token (optional)
-Clawdbot can use a Slack user token (`xoxp-...`) for read operations (history,
+Moltbot can use a Slack user token (`xoxp-...`) for read operations (history,
 pins, reactions, emoji, member info). By default this stays read-only: reads
 prefer the user token when present, and writes still use the bot token unless
 you explicitly opt in. Even with `userTokenReadOnly: false`, the bot token stays
@@ -109,7 +109,7 @@ Example with userTokenReadOnly explicitly set (allow user token writes):
  search) prefer the user token when configured, otherwise the bot token.
 - Write operations (send/edit/delete messages, add/remove reactions, pin/unpin,
  file uploads) use the bot token by default. If `userTokenReadOnly: false` and
-  no bot token is available, Clawdbot falls back to the user token.
+  no bot token is available, Moltbot falls back to the user token.

 ### History context
 - `channels.slack.historyLimit` (or `channels.slack.accounts.*.historyLimit`) controls how many recent channel/group messages are wrapped into the prompt.
@@ -130,7 +130,7 @@ HTTP mode uses the Events API + Interactivity + Slash Commands with a shared req
 Example request URL:
 `https://gateway-host/slack/events`

-### Clawdbot config (minimal)
+### Moltbot config (minimal)
 ```json5
 {
  channels: {
@@ -155,12 +155,12 @@ user scopes if you plan to configure a user token.
 ```json
 {
  "display_information": {
-    "name": "Clawdbot",
-    "description": "Slack connector for Clawdbot"
+    "name": "Moltbot",
+    "description": "Slack connector for Moltbot"
  },
  "features": {
    "bot_user": {
-      "display_name": "Clawdbot",
+      "display_name": "Moltbot",
      "always_online": false
    },
    "app_home": {
@@ -170,7 +170,7 @@ user scopes if you plan to configure a user token.
    "slash_commands": [
      {
        "command": "/clawd",
-        "description": "Send a message to Clawdbot",
+        "description": "Send a message to Moltbot",
        "should_escape": false
      }
    ]
@@ -353,7 +353,7 @@ ack reaction after the bot replies.
 - Media uploads are capped by `channels.slack.mediaMaxMb` (default 20).

 ## Reply threading
-By default, Clawdbot replies in the main channel. Use `channels.slack.replyToMode` to control automatic threading:
+By default, Moltbot replies in the main channel. Use `channels.slack.replyToMode` to control automatic threading:

 | Mode | Behavior |
 | --- | --- |
@@ -439,13 +439,13 @@ For fine-grained control, use these tags in agent responses:
 - DMs share the `main` session (like WhatsApp/Telegram).
 - Channels map to `agent:<agentId>:slack:channel:<channelId>` sessions.
 - Slash commands use `agent:<agentId>:slack:slash:<userId>` sessions (prefix configurable via `channels.slack.slashCommand.sessionPrefix`).
- If Slack doesn’t provide `channel_type`, Clawdbot infers it from the channel ID prefix (`D`, `C`, `G`) and defaults to `channel` to keep session keys stable.
+- If Slack doesn’t provide `channel_type`, Moltbot infers it from the channel ID prefix (`D`, `C`, `G`) and defaults to `channel` to keep session keys stable.
 - Native command registration uses `commands.native` (global default `"auto"` → Slack off) and can be overridden per-workspace with `channels.slack.commands.native`. Text commands require standalone `/...` messages and can be disabled with `commands.text: false`. Slack slash commands are managed in the Slack app and are not removed automatically. Use `commands.useAccessGroups: false` to bypass access-group checks for commands.
 - Full command list + config: [Slash commands](/tools/slash-commands)

 ## DM security (pairing)
 - Default: `channels.slack.dm.policy="pairing"` — unknown DM senders get a pairing code (expires after 1 hour).
- Approve via: `clawdbot pairing approve slack <code>`.
+- Approve via: `moltbot pairing approve slack <code>`.
 - To allow anyone: set `channels.slack.dm.policy="open"` and `channels.slack.dm.allowFrom=["*"]`.
 - `channels.slack.dm.allowFrom` accepts user IDs, @handles, or emails (resolved at startup when tokens allow). The wizard accepts usernames and resolves them to ids during setup when tokens allow.

@@ -457,7 +457,7 @@ For fine-grained control, use these tags in agent responses:
   `channels.defaults.groupPolicy`, or a channel allowlist to lock it down.
 - The configure wizard accepts `#channel` names and resolves them to IDs when possible
   (public + private); if multiple matches exist, it prefers the active channel.
- - On startup, Clawdbot resolves channel/user names in allowlists to IDs (when tokens allow)
+ - On startup, Moltbot resolves channel/user names in allowlists to IDs (when tokens allow)
   and logs the mapping; unresolved entries are kept as typed.
 - To allow **no channels**, set `channels.slack.groupPolicy: "disabled"` (or keep an empty allowlist).

--- a/docs/channels/telegram.md
+++ b/docs/channels/telegram.md
@@ -101,10 +101,10 @@ group messages, so use admin if you need full visibility.
 - Outbound Telegram text uses `parse_mode: "HTML"` (Telegram’s supported tag subset).
 - Markdown-ish input is rendered into **Telegram-safe HTML** (bold/italic/strike/code/links); block elements are flattened to text with newlines/bullets.
 - Raw HTML from models is escaped to avoid Telegram parse errors.
- If Telegram rejects the HTML payload, Clawdbot retries the same message as plain text.
+- If Telegram rejects the HTML payload, Moltbot retries the same message as plain text.

 ## Commands (native + custom)
-Clawdbot registers native commands (like `/status`, `/reset`, `/model`) with Telegram’s bot menu on startup.
+Moltbot registers native commands (like `/status`, `/reset`, `/model`) with Telegram’s bot menu on startup.
 You can add custom commands to the menu via config:

 ```json5
@@ -128,7 +128,7 @@ You can add custom commands to the menu via config:
 More help: [Channel troubleshooting](/channels/troubleshooting).

 Notes:
- Custom commands are **menu entries only**; Clawdbot does not implement them unless you handle them elsewhere.
+- Custom commands are **menu entries only**; Moltbot does not implement them unless you handle them elsewhere.
 - Command names are normalized (leading `/` stripped, lowercased) and must match `a-z`, `0-9`, `_` (1–32 chars).
 - Custom commands **cannot override native commands**. Conflicts are ignored and logged.
 - If `commands.native` is disabled, only custom commands are registered (or cleared if none).
@@ -202,13 +202,13 @@ Forward any message from the group to `@userinfobot` or `@getidsbot` on Telegram

 **Tip:** For your own user ID, DM the bot and it will reply with your user ID (pairing message), or use `/whoami` once commands are enabled.

-**Privacy note:** `@userinfobot` is a third-party bot. If you prefer, add the bot to the group, send a message, and use `clawdbot logs --follow` to read `chat.id`, or use the Bot API `getUpdates`.
+**Privacy note:** `@userinfobot` is a third-party bot. If you prefer, add the bot to the group, send a message, and use `moltbot logs --follow` to read `chat.id`, or use the Bot API `getUpdates`.

 ## Config writes
 By default, Telegram is allowed to write config updates triggered by channel events or `/config set|unset`.

 This happens when:
- A group is upgraded to a supergroup and Telegram emits `migrate_to_chat_id` (chat ID changes). Clawdbot can migrate `channels.telegram.groups` automatically.
+- A group is upgraded to a supergroup and Telegram emits `migrate_to_chat_id` (chat ID changes). Moltbot can migrate `channels.telegram.groups` automatically.
 - You run `/config set` or `/config unset` in a Telegram chat (requires `commands.config: true`).

 Disable with:
@@ -219,7 +219,7 @@ Disable with:
 ```

 ## Topics (forum supergroups)
-Telegram forum topics include a `message_thread_id` per message. Clawdbot:
+Telegram forum topics include a `message_thread_id` per message. Moltbot:
 - Appends `:topic:<threadId>` to the Telegram group session key so each topic is isolated.
 - Sends typing indicators and replies with `message_thread_id` so responses stay in the topic.
 - General topic (thread id `1`) is special: message sends omit `message_thread_id` (Telegram rejects it), but typing indicators still include it.
@@ -227,7 +227,7 @@ Telegram forum topics include a `message_thread_id` per message. Clawdbot:
 - Topic-specific configuration is available under `channels.telegram.groups.<chatId>.topics.<threadId>` (skills, allowlists, auto-reply, system prompts, disable).
 - Topic configs inherit group settings (requireMention, allowlists, skills, prompts, enabled) unless overridden per topic.

-Private chats can include `message_thread_id` in some edge cases. Clawdbot keeps the DM session key unchanged, but still uses the thread id for replies/draft streaming when it is present.
+Private chats can include `message_thread_id` in some edge cases. Moltbot keeps the DM session key unchanged, but still uses the thread id for replies/draft streaming when it is present.

 ## Inline Buttons

@@ -310,15 +310,15 @@ Use the global setting when all Telegram bots/accounts should behave the same. U
 ### DM access
 - Default: `channels.telegram.dmPolicy = "pairing"`. Unknown senders receive a pairing code; messages are ignored until approved (codes expire after 1 hour).
 - Approve via:
-  - `clawdbot pairing list telegram`
-  - `clawdbot pairing approve telegram <CODE>`
+  - `moltbot pairing list telegram`
+  - `moltbot pairing approve telegram <CODE>`
 - Pairing is the default token exchange used for Telegram DMs. Details: [Pairing](/start/pairing)
 - `channels.telegram.allowFrom` accepts numeric user IDs (recommended) or `@username` entries. It is **not** the bot username; use the human sender’s ID. The wizard accepts `@username` and resolves it to the numeric ID when possible.

 #### Finding your Telegram user ID
 Safer (no third-party bot):
 1) Start the gateway and DM your bot.
-2) Run `clawdbot logs --follow` and look for `from.id`.
+2) Run `moltbot logs --follow` and look for `from.id`.

 Alternate (official Bot API):
 1) DM your bot.
@@ -363,7 +363,7 @@ Controlled by `channels.telegram.replyToMode`:

 ## Audio messages (voice vs file)
 Telegram distinguishes **voice notes** (round bubble) from **audio files** (metadata card).
-Clawdbot defaults to audio files for backward compatibility.
+Moltbot defaults to audio files for backward compatibility.

 To force a voice note bubble in agent replies, include this tag anywhere in the reply:
 - `[[audio_as_voice]]` — send audio as a voice note instead of a file.
@@ -385,11 +385,11 @@ For message tool sends, set `asVoice: true` with a voice-compatible audio `media

 ## Stickers

-Clawdbot supports receiving and sending Telegram stickers with intelligent caching.
+Moltbot supports receiving and sending Telegram stickers with intelligent caching.

 ### Receiving stickers

-When a user sends a sticker, Clawdbot handles it based on the sticker type:
+When a user sends a sticker, Moltbot handles it based on the sticker type:

 - **Static stickers (WEBP):** Downloaded and processed through vision. The sticker appears as a `<media:sticker>` placeholder in the message content.
 - **Animated stickers (TGS):** Skipped (Lottie format not supported for processing).
@@ -405,7 +405,7 @@ Template context field available when receiving stickers:

 ### Sticker cache

-Stickers are processed through the AI's vision capabilities to generate descriptions. Since the same stickers are often sent repeatedly, Clawdbot caches these descriptions to avoid redundant API calls.
+Stickers are processed through the AI's vision capabilities to generate descriptions. Since the same stickers are often sent repeatedly, Moltbot caches these descriptions to avoid redundant API calls.

 **How it works:**

@@ -512,7 +512,7 @@ The search uses fuzzy matching across description text, emoji characters, and se

 ## Streaming (drafts)
 Telegram can stream **draft bubbles** while the agent is generating a response.
-Clawdbot uses Bot API `sendMessageDraft` (not real messages) and then sends the
+Moltbot uses Bot API `sendMessageDraft` (not real messages) and then sends the
 final reply as a normal message.

 Requirements (Telegram Bot API 9.3+):
@@ -552,7 +552,7 @@ Outbound Telegram API calls retry on transient network/429 errors with exponenti
 ## Reaction notifications

 **How reactions work:**
-Telegram reactions arrive as **separate `message_reaction` events**, not as properties in message payloads. When a user adds a reaction, Clawdbot:
+Telegram reactions arrive as **separate `message_reaction` events**, not as properties in message payloads. When a user adds a reaction, Moltbot:

 1. Receives the `message_reaction` update from Telegram API
 2. Converts it to a **system event** with format: `"Telegram reaction added: {emoji} by {user} on msg {id}"`
@@ -588,28 +588,28 @@ The agent sees reactions as **system notifications** in the conversation history
 ```

 **Requirements:**
- Telegram bots must explicitly request `message_reaction` in `allowed_updates` (configured automatically by Clawdbot)
+- Telegram bots must explicitly request `message_reaction` in `allowed_updates` (configured automatically by Moltbot)
 - For webhook mode, reactions are included in the webhook `allowed_updates`
 - For polling mode, reactions are included in the `getUpdates` `allowed_updates`

 ## Delivery targets (CLI/cron)
 - Use a chat id (`123456789`) or a username (`@name`) as the target.
- Example: `clawdbot message send --channel telegram --target 123456789 --message "hi"`.
+- Example: `moltbot message send --channel telegram --target 123456789 --message "hi"`.

 ## Troubleshooting

 **Bot doesn’t respond to non-mention messages in a group:**
 - If you set `channels.telegram.groups.*.requireMention=false`, Telegram’s Bot API **privacy mode** must be disabled.
  - BotFather: `/setprivacy` → **Disable** (then remove + re-add the bot to the group)
- `clawdbot channels status` shows a warning when config expects unmentioned group messages.
- `clawdbot channels status --probe` can additionally check membership for explicit numeric group IDs (it can’t audit wildcard `"*"` rules).
+- `moltbot channels status` shows a warning when config expects unmentioned group messages.
+- `moltbot channels status --probe` can additionally check membership for explicit numeric group IDs (it can’t audit wildcard `"*"` rules).
 - Quick test: `/activation always` (session-only; use config for persistence)

 **Bot not seeing group messages at all:**
 - If `channels.telegram.groups` is set, the group must be listed or use `"*"`
 - Check Privacy Settings in @BotFather → "Group Privacy" should be **OFF**
 - Verify bot is actually a member (not just an admin with no read access)
- Check gateway logs: `clawdbot logs --follow` (look for "skipping group message")
+- Check gateway logs: `moltbot logs --follow` (look for "skipping group message")

 **Bot responds to mentions but not `/activation always`:**
 - The `/activation` command updates session state but doesn't persist to config
@@ -621,7 +621,7 @@ The agent sees reactions as **system notifications** in the conversation history

 **Long-polling aborts immediately on Node 22+ (often with proxies/custom fetch):**
 - Node 22+ is stricter about `AbortSignal` instances; foreign signals can abort `fetch` calls right away.
- Upgrade to a Clawdbot build that normalizes abort signals, or run the gateway on Node 20 until you can upgrade.
+- Upgrade to a Moltbot build that normalizes abort signals, or run the gateway on Node 20 until you can upgrade.

 **Bot starts, then silently stops responding (or logs `HttpError: Network request ... failed`):**
 - Some hosts resolve `api.telegram.org` to IPv6 first. If your server does not have working IPv6 egress, grammY can get stuck on IPv6-only requests.
--- a/docs/channels/tlon.md
+++ b/docs/channels/tlon.md
@@ -5,7 +5,7 @@ read_when:
 ---
 # Tlon (plugin)

-Tlon is a decentralized messenger built on Urbit. Clawdbot connects to your Urbit ship and can
+Tlon is a decentralized messenger built on Urbit. Moltbot 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
-clawdbot plugins install @clawdbot/tlon
+moltbot plugins install @moltbot/tlon
 ```

 Local checkout (when running from a git repo):

 ```bash
-clawdbot plugins install ./extensions/tlon
+moltbot plugins install ./extensions/tlon
 ```

 Details: [Plugins](/plugin)
@@ -121,7 +121,7 @@ Group authorization (restricted by default):

 ## Delivery targets (CLI/cron)

-Use these with `clawdbot message send` or cron delivery:
+Use these with `moltbot 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 `clawdbot 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, Clawdbot replies in-thread.
+- Thread replies: if the inbound message is in a thread, Moltbot replies in-thread.
 - Media: `sendMedia` falls back to text + URL (no native upload).
--- a/docs/channels/troubleshooting.md
+++ b/docs/channels/troubleshooting.md
@@ -9,8 +9,8 @@ read_when:
 Start with:

 ```bash
-clawdbot doctor
-clawdbot channels status --probe
+moltbot doctor
+moltbot channels status --probe
 ```

 `channels status --probe` prints warnings when it can detect common channel misconfigurations, and includes small live checks (credentials, some permissions/membership).
--- a/docs/channels/twitch.md
+++ b/docs/channels/twitch.md
@@ -1,11 +1,11 @@
 ---
 summary: "Twitch chat bot configuration and setup"
 read_when:
-  - Setting up Twitch chat integration for Clawdbot
+  - Setting up Twitch chat integration for Moltbot
 ---
 # Twitch (plugin)

-Twitch chat support via IRC connection. Clawdbot connects as a Twitch user (bot account) to receive and send messages in channels.
+Twitch chat support via IRC connection. Moltbot 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
-clawdbot plugins install @clawdbot/twitch
+moltbot plugins install @moltbot/twitch
 ```

 Local checkout (when running from a git repo):

 ```bash
-clawdbot plugins install ./extensions/twitch
+moltbot plugins install ./extensions/twitch
 ```

 Details: [Plugins](/plugin)
@@ -48,7 +48,7 @@ Minimal config:
  channels: {
    twitch: {
      enabled: true,
-      username: "clawdbot",              // Bot's Twitch account
+      username: "moltbot",              // Bot's Twitch account
      accessToken: "oauth:abc123...",    // OAuth Access Token (or use CLAWDBOT_TWITCH_ACCESS_TOKEN env var)
      clientId: "xyz789...",             // Client ID from Token Generator
      channel: "vevisk",                 // Which Twitch channel's chat to join (required)
@@ -89,7 +89,7 @@ CLAWDBOT_TWITCH_ACCESS_TOKEN=oauth:abc123...
  channels: {
    twitch: {
      enabled: true,
-      username: "clawdbot",
+      username: "moltbot",
      accessToken: "oauth:abc123...",
      clientId: "xyz789...",
      channel: "vevisk"
@@ -150,13 +150,13 @@ Example (one bot account in two channels):
    twitch: {
      accounts: {
        channel1: {
-          username: "clawdbot",
+          username: "moltbot",
          accessToken: "oauth:abc123...",
          clientId: "xyz789...",
          channel: "vevisk"
        },
        channel2: {
-          username: "clawdbot",
+          username: "moltbot",
          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
-clawdbot doctor
-clawdbot channels status --probe
+moltbot doctor
+moltbot channels status --probe
 ```

 ### Bot doesn't respond to messages
@@ -305,7 +305,7 @@ Full example:
  channels: {
    twitch: {
      enabled: true,
-      username: "clawdbot",
+      username: "moltbot",
      accessToken: "oauth:abc123...",
      clientId: "xyz789...",
      channel: "vevisk",
--- a/docs/channels/whatsapp.md
+++ b/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/clawdbot.json`.
-3) Run `clawdbot channels login` to scan the QR code (Linked Devices).
+2) Configure WhatsApp in `~/.clawdbot/moltbot.json`.
+3) Run `moltbot 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 Clawdbot on WhatsApp:
+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:

 ### Dedicated number (recommended)
-Use a **separate phone number** for Clawdbot. 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 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.

-**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 Clawdbot 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 Moltbot number there.

 **Sample config (dedicated number, single-user allowlist):**
 ```json5
@@ -69,10 +69,10 @@ Use a **separate phone number** for Clawdbot. Best UX, clean routing, no self-ch

 **Pairing mode (optional):**
 If you want pairing instead of allowlist, set `channels.whatsapp.dmPolicy` to `pairing`. Unknown senders get a pairing code; approve with:
-`clawdbot pairing approve whatsapp <code>`
+`moltbot pairing approve whatsapp <code>`

 ### Personal number (fallback)
-Quick fallback: run Clawdbot 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 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.**
 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 `[clawdbot]`)
+Self-chat replies default to `[{identity.name}]` when set (otherwise `[moltbot]`)
 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 Clawdbot builds supported Twilio’s WhatsApp Business integration.
+- Early Moltbot 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: `clawdbot channels login` (QR via Linked Devices).
- Multi-account login: `clawdbot channels login --account <id>` (`<id>` = `accountId`).
+- Login command: `moltbot channels login` (QR via Linked Devices).
+- Multi-account login: `moltbot 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`.
 - Backup copy at `creds.json.bak` (restored on corruption).
 - Legacy compatibility: older installs stored Baileys files directly in `~/.clawdbot/credentials/`.
- Logout: `clawdbot channels logout` (or `--account <id>`) deletes WhatsApp auth state (but keeps shared `oauth.json`).
+- Logout: `moltbot 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 `clawdbot pairing approve whatsapp <code>`; codes expire after 1 hour).
+  - Pairing: unknown senders get a pairing code (approve via `moltbot 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.

 ### Personal-number mode (fallback)
-If you run Clawdbot on your **personal WhatsApp number**, enable `channels.whatsapp.selfChatMode` (see sample above).
+If you run Moltbot 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 Clawdbot 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**. Clawdbot only replies to chats it receives, or to sends you explicitly trigger (agent/CLI).
+**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).

 **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: `clawdbot pairing approve whatsapp <code>` (list with `clawdbot pairing list whatsapp`).
+- Approve with: `moltbot pairing approve whatsapp <code>` (list with `moltbot pairing list whatsapp`).
 - Codes expire after 1 hour; pending requests are capped at 3 per channel.

-**Can multiple people use different Clawdbots on one WhatsApp number?**  
+**Can multiple people use different Moltbots 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: `clawdbot message send --media <mp4> --gif-playback`
+    - CLI: `moltbot 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. Clawdbot rewrites `audio/ogg` to `audio/ogg; codecs=opus`.
+- Best results: OGG/Opus. Moltbot 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/clawdbot/clawdbot-YYYY-MM-DD.log` (configurable).
+- Log file: `/tmp/moltbot/moltbot-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 `clawdbot channels login` on the gateway host and scan the QR (WhatsApp → Settings → Linked Devices).
+- Fix: run `moltbot 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: `clawdbot doctor` (or restart the gateway). If it persists, relink via `channels login` and inspect `clawdbot logs --follow`.
+- Fix: `moltbot doctor` (or restart the gateway). If it persists, relink via `channels login` and inspect `moltbot logs --follow`.

 **Bun runtime**
 - Bun is **not recommended**. WhatsApp (Baileys) and Telegram are unreliable on Bun.
--- a/docs/channels/zalo.md
+++ b/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: `clawdbot plugins install @clawdbot/zalo`
+- Install via CLI: `moltbot plugins install @moltbot/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: `clawdbot plugins install ./extensions/zalo`
-   - From npm (if published): `clawdbot plugins install @clawdbot/zalo`
+   - From a source checkout: `moltbot plugins install ./extensions/zalo`
+   - From npm (if published): `moltbot plugins install @moltbot/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:
-  - `clawdbot pairing list zalo`
-  - `clawdbot pairing approve zalo <CODE>`
+  - `moltbot pairing list zalo`
+  - `moltbot 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: `clawdbot message send --channel zalo --target 123456789 --message "hi"`.
+- Example: `moltbot message send --channel zalo --target 123456789 --message "hi"`.

 ## Troubleshooting

 **Bot doesn't respond:**
- Check that the token is valid: `clawdbot channels status --probe`
+- Check that the token is valid: `moltbot channels status --probe`
 - Verify the sender is approved (pairing or allowFrom)
- Check gateway logs: `clawdbot logs --follow`
+- Check gateway logs: `moltbot logs --follow`

 **Webhook not receiving events:**
 - Ensure webhook URL uses HTTPS
--- a/docs/channels/zalouser.md
+++ b/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 Clawdbot
+  - Setting up Zalo Personal for Moltbot
  - 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: `clawdbot plugins install @clawdbot/zalouser`
- Or from a source checkout: `clawdbot plugins install ./extensions/zalouser`
+- Install via CLI: `moltbot plugins install @moltbot/zalouser`
+- Or from a source checkout: `moltbot 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):
-   - `clawdbot channels login --channel zalouser`
+   - `moltbot 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
-clawdbot directory self --channel zalouser
-clawdbot directory peers list --channel zalouser --query "name"
-clawdbot directory groups list --channel zalouser --query "work"
+moltbot directory self --channel zalouser
+moltbot directory peers list --channel zalouser --query "name"
+moltbot directory groups list --channel zalouser --query "work"
 ```

 ## Limits
@@ -69,8 +69,8 @@ clawdbot 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:
- `clawdbot pairing list zalouser`
- `clawdbot pairing approve zalouser <code>`
+- `moltbot pairing list zalouser`
+- `moltbot 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, Clawdbot resolves group/user names in allowlists to IDs and logs the mapping; unresolved entries are kept as typed.
+- On startup, Moltbot 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:**
- `clawdbot channels status --probe`
- Re-login: `clawdbot channels logout --channel zalouser && clawdbot channels login --channel zalouser`
+- `moltbot channels status --probe`
+- Re-login: `moltbot channels logout --channel zalouser && moltbot channels login --channel zalouser`