refactor: rename clawdbot to moltbot with legacy compat

docs/cli/acp.md

@@ -7,7 +7,7 @@ read_when:
 
 # acp
 
-Run the ACP (Agent Client Protocol) bridge that talks to a Clawdbot Gateway.
+Run the ACP (Agent Client Protocol) bridge that talks to a Moltbot 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
-clawdbot acp
+moltbot acp
 
 # Remote Gateway
-clawdbot acp --url wss://gateway-host:18789 --token <token>
+moltbot acp --url wss://gateway-host:18789 --token <token>
 
 # Attach to an existing session key
-clawdbot acp --session agent:main:main
+moltbot acp --session agent:main:main
 
 # Attach by label (must already exist)
-clawdbot acp --session-label "support inbox"
+moltbot acp --session-label "support inbox"
 
 # Reset the session key before the first prompt
-clawdbot acp --session agent:main:main --reset-session
+moltbot 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
-clawdbot acp client
+moltbot acp client
 
 # Point the spawned bridge at a remote Gateway
-clawdbot acp client --server-args --url wss://gateway-host:18789 --token <token>
+moltbot acp client --server-args --url wss://gateway-host:18789 --token <token>
 
-# Override the server command (default: clawdbot)
-clawdbot acp client --server "node" --server-args dist/entry.js acp --url ws://127.0.0.1:19001
+# Override the server command (default: moltbot)
+moltbot acp client --server "node" --server-args dist/entry.js 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 Clawdbot Gateway session.
+it to drive a Moltbot 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 `clawdbot acp` over stdio.
+3. Point your IDE to run `moltbot acp` over stdio.
 
 Example config (persisted):
 
 ```bash
-clawdbot config set gateway.remote.url wss://gateway-host:18789
-clawdbot config set gateway.remote.token <token>
+moltbot config set gateway.remote.url wss://gateway-host:18789
+moltbot config set gateway.remote.token <token>
 ```
 
 Example direct run (no config write):
 
 ```bash
-clawdbot acp --url wss://gateway-host:18789 --token <token>
+moltbot 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
-clawdbot acp --session agent:main:main
-clawdbot acp --session agent:design:main
-clawdbot acp --session agent:qa:bug-123
+moltbot acp --session agent:main:main
+moltbot acp --session agent:design:main
+moltbot 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": {
-    "Clawdbot ACP": {
+    "Moltbot ACP": {
       "type": "custom",
-      "command": "clawdbot",
+      "command": "moltbot",
       "args": ["acp"],
       "env": {}
     }
@@ -105,9 +105,9 @@ To target a specific Gateway or agent:
 ```json
 {
   "agent_servers": {
-    "Clawdbot ACP": {
+    "Moltbot ACP": {
       "type": "custom",
-      "command": "clawdbot",
+      "command": "moltbot",
       "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 “Clawdbot ACP” to start a thread.
+In Zed, open the Agent panel and select “Moltbot 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: `clawdbot`).
+- `--server <command>`: ACP server command (default: `moltbot`).
 - `--server-args <args...>`: extra arguments passed to the ACP server.
 - `--server-verbose`: enable verbose logging on the ACP server.
 - `--verbose, -v`: verbose client logging.

docs/cli/agent.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `clawdbot agent` (send one agent turn via the Gateway)"
+summary: "CLI reference for `moltbot agent` (send one agent turn via the Gateway)"
 read_when:
   - You want to run one agent turn from scripts (optionally deliver reply)
 ---
 
-# `clawdbot agent`
+# `moltbot 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
-clawdbot agent --to +15555550123 --message "status update" --deliver
-clawdbot agent --agent ops --message "Summarize logs"
-clawdbot agent --session-id 1234 --message "Summarize inbox" --thinking medium
-clawdbot agent --agent ops --message "Generate report" --deliver --reply-channel slack --reply-to "#reports"
+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"
 ```

docs/cli/agents.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `clawdbot agents` (list/add/delete/set identity)"
+summary: "CLI reference for `moltbot agents` (list/add/delete/set identity)"
 read_when:
   - You want multiple isolated agents (workspaces + routing + auth)
 ---
 
-# `clawdbot agents`
+# `moltbot agents`
 
 Manage isolated agents (workspaces + auth + routing).
 
@@ -15,11 +15,11 @@ Related:
 ## Examples
 
 ```bash
-clawdbot agents list
-clawdbot agents add work --workspace ~/clawd-work
-clawdbot agents set-identity --workspace ~/clawd --from-identity
-clawdbot agents set-identity --agent main --avatar avatars/clawd.png
-clawdbot agents delete work
+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
 ```
 
 ## Identity files
@@ -41,13 +41,13 @@ Avatar paths resolve relative to the workspace root.
 Load from `IDENTITY.md`:
 
 ```bash
-clawdbot agents set-identity --workspace ~/clawd --from-identity
+moltbot agents set-identity --workspace ~/clawd --from-identity
 ```
 
 Override fields explicitly:
 
 ```bash
-clawdbot agents set-identity --agent main --name "Clawd" --emoji "🦞" --avatar avatars/clawd.png
+moltbot agents set-identity --agent main --name "Clawd" --emoji "🦞" --avatar avatars/clawd.png
 ```
 
 Config sample:

docs/cli/approvals.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot approvals` (exec approvals for gateway or node hosts)"
+summary: "CLI reference for `moltbot approvals` (exec approvals for gateway or node hosts)"
 read_when:
   - You want to edit exec approvals from the CLI
   - You need to manage allowlists on gateway or node hosts
 ---
 
-# `clawdbot approvals`
+# `moltbot approvals`
 
 Manage exec approvals for the **local host**, **gateway host**, or a **node host**.
 By default, commands target the local approvals file on disk. Use `--gateway` to target the gateway, or `--node` to target a specific node.
@@ -17,32 +17,32 @@ Related:
 ## Common commands
 
 ```bash
-clawdbot approvals get
-clawdbot approvals get --node <id|name|ip>
-clawdbot approvals get --gateway
+moltbot approvals get
+moltbot approvals get --node <id|name|ip>
+moltbot approvals get --gateway
 ```
 
 ## Replace approvals from a file
 
 ```bash
-clawdbot approvals set --file ./exec-approvals.json
-clawdbot approvals set --node <id|name|ip> --file ./exec-approvals.json
-clawdbot approvals set --gateway --file ./exec-approvals.json
+moltbot approvals set --file ./exec-approvals.json
+moltbot approvals set --node <id|name|ip> --file ./exec-approvals.json
+moltbot approvals set --gateway --file ./exec-approvals.json
 ```
 
 ## Allowlist helpers
 
 ```bash
-clawdbot approvals allowlist add "~/Projects/**/bin/rg"
-clawdbot approvals allowlist add --agent main --node <id|name|ip> "/usr/bin/uptime"
-clawdbot approvals allowlist add --agent "*" "/usr/bin/uname"
+moltbot approvals allowlist add "~/Projects/**/bin/rg"
+moltbot approvals allowlist add --agent main --node <id|name|ip> "/usr/bin/uptime"
+moltbot approvals allowlist add --agent "*" "/usr/bin/uname"
 
-clawdbot approvals allowlist remove "~/Projects/**/bin/rg"
+moltbot approvals allowlist remove "~/Projects/**/bin/rg"
 ```
 
 ## Notes
 
-- `--node` uses the same resolver as `clawdbot nodes` (id, name, ip, or id prefix).
+- `--node` uses the same resolver as `moltbot nodes` (id, name, ip, or id prefix).
 - `--agent` defaults to `"*"`, which applies to all agents.
 - The node host must advertise `system.execApprovals.get/set` (macOS app or headless node host).
 - Approvals files are stored per host at `~/.clawdbot/exec-approvals.json`.

docs/cli/browser.md

@@ -1,14 +1,14 @@
 ---
-summary: "CLI reference for `clawdbot browser` (profiles, tabs, actions, extension relay)"
+summary: "CLI reference for `moltbot browser` (profiles, tabs, actions, extension relay)"
 read_when:
-  - You use `clawdbot browser` and want examples for common tasks
+  - You use `moltbot browser` and want examples for common tasks
   - You want to control a browser running on another machine via a node host
   - You want to use the Chrome extension relay (attach/detach via toolbar button)
 ---
 
-# `clawdbot browser`
+# `moltbot browser`
 
-Manage Clawdbot’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
+Manage Moltbot’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
 
 Related:
 - Browser tool + API: [Browser tool](/tools/browser)
@@ -25,37 +25,37 @@ Related:
 ## Quick start (local)
 
 ```bash
-clawdbot browser --browser-profile chrome tabs
-clawdbot browser --browser-profile clawd start
-clawdbot browser --browser-profile clawd open https://example.com
-clawdbot browser --browser-profile clawd snapshot
+moltbot browser --browser-profile chrome tabs
+moltbot browser --browser-profile clawd start
+moltbot browser --browser-profile clawd open https://example.com
+moltbot browser --browser-profile clawd snapshot
 ```
 
 ## Profiles
 
 Profiles are named browser routing configs. In practice:
-- `clawd`: launches/attaches to a dedicated Clawdbot-managed Chrome instance (isolated user data dir).
+- `clawd`: launches/attaches to a dedicated Moltbot-managed Chrome instance (isolated user data dir).
 - `chrome`: controls your existing Chrome tab(s) via the Chrome extension relay.
 
 ```bash
-clawdbot browser profiles
-clawdbot browser create-profile --name work --color "#FF5A36"
-clawdbot browser delete-profile --name work
+moltbot browser profiles
+moltbot browser create-profile --name work --color "#FF5A36"
+moltbot browser delete-profile --name work
 ```
 
 Use a specific profile:
 
 ```bash
-clawdbot browser --browser-profile work tabs
+moltbot browser --browser-profile work tabs
 ```
 
 ## Tabs
 
 ```bash
-clawdbot browser tabs
-clawdbot browser open https://docs.molt.bot
-clawdbot browser focus <targetId>
-clawdbot browser close <targetId>
+moltbot browser tabs
+moltbot browser open https://docs.molt.bot
+moltbot browser focus <targetId>
+moltbot browser close <targetId>
 ```
 
 ## Snapshot / screenshot / actions
@@ -63,21 +63,21 @@ clawdbot browser close <targetId>
 Snapshot:
 
 ```bash
-clawdbot browser snapshot
+moltbot browser snapshot
 ```
 
 Screenshot:
 
 ```bash
-clawdbot browser screenshot
+moltbot browser screenshot
 ```
 
 Navigate/click/type (ref-based UI automation):
 
 ```bash
-clawdbot browser navigate https://example.com
-clawdbot browser click <ref>
-clawdbot browser type <ref> "hello"
+moltbot browser navigate https://example.com
+moltbot browser click <ref>
+moltbot browser type <ref> "hello"
 ```
 
 ## Chrome extension relay (attach via toolbar button)
@@ -87,8 +87,8 @@ This mode lets the agent control an existing Chrome tab that you attach manually
 Install the unpacked extension to a stable path:
 
 ```bash
-clawdbot browser extension install
-clawdbot browser extension path
+moltbot browser extension install
+moltbot browser extension path
 ```
 
 Then Chrome → `chrome://extensions` → enable “Developer mode” → “Load unpacked” → select the printed folder.

docs/cli/channels.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot channels` (accounts, status, login/logout, logs)"
+summary: "CLI reference for `moltbot channels` (accounts, status, login/logout, logs)"
 read_when:
   - You want to add/remove channel accounts (WhatsApp/Telegram/Discord/Google Chat/Slack/Mattermost (plugin)/Signal/iMessage)
   - You want to check channel status or tail channel logs
 ---
 
-# `clawdbot channels`
+# `moltbot channels`
 
 Manage chat channel accounts and their runtime status on the Gateway.
 
@@ -16,43 +16,43 @@ Related docs:
 ## Common commands
 
 ```bash
-clawdbot channels list
-clawdbot channels status
-clawdbot channels capabilities
-clawdbot channels capabilities --channel discord --target channel:123
-clawdbot channels resolve --channel slack "#general" "@jane"
-clawdbot channels logs --channel all
+moltbot channels list
+moltbot channels status
+moltbot channels capabilities
+moltbot channels capabilities --channel discord --target channel:123
+moltbot channels resolve --channel slack "#general" "@jane"
+moltbot channels logs --channel all
 ```
 
 ## Add / remove accounts
 
 ```bash
-clawdbot channels add --channel telegram --token <bot-token>
-clawdbot channels remove --channel telegram --delete
+moltbot channels add --channel telegram --token <bot-token>
+moltbot channels remove --channel telegram --delete
 ```
 
-Tip: `clawdbot channels add --help` shows per-channel flags (token, app token, signal-cli paths, etc).
+Tip: `moltbot channels add --help` shows per-channel flags (token, app token, signal-cli paths, etc).
 
 ## Login / logout (interactive)
 
 ```bash
-clawdbot channels login --channel whatsapp
-clawdbot channels logout --channel whatsapp
+moltbot channels login --channel whatsapp
+moltbot channels logout --channel whatsapp
 ```
 
 ## Troubleshooting
 
-- Run `clawdbot status --deep` for a broad probe.
-- Use `clawdbot doctor` for guided fixes.
-- `clawdbot channels list` prints `Claude: HTTP 403 ... user:profile` → usage snapshot needs the `user:profile` scope. Use `--no-usage`, or provide a claude.ai session key (`CLAUDE_WEB_SESSION_KEY` / `CLAUDE_WEB_COOKIE`), or re-auth via Claude Code CLI.
+- Run `moltbot status --deep` for a broad probe.
+- Use `moltbot doctor` for guided fixes.
+- `moltbot channels list` prints `Claude: HTTP 403 ... user:profile` → usage snapshot needs the `user:profile` scope. Use `--no-usage`, or provide a claude.ai session key (`CLAUDE_WEB_SESSION_KEY` / `CLAUDE_WEB_COOKIE`), or re-auth via Claude Code CLI.
 
 ## Capabilities probe
 
 Fetch provider capability hints (intents/scopes where available) plus static feature support:
 
 ```bash
-clawdbot channels capabilities
-clawdbot channels capabilities --channel discord --target channel:123
+moltbot channels capabilities
+moltbot channels capabilities --channel discord --target channel:123
 ```
 
 Notes:
@@ -65,9 +65,9 @@ Notes:
 Resolve channel/user names to IDs using the provider directory:
 
 ```bash
-clawdbot channels resolve --channel slack "#general" "@jane"
-clawdbot channels resolve --channel discord "My Server/#support" "@someone"
-clawdbot channels resolve --channel matrix "Project Room"
+moltbot channels resolve --channel slack "#general" "@jane"
+moltbot channels resolve --channel discord "My Server/#support" "@someone"
+moltbot channels resolve --channel matrix "Project Room"
 ```
 
 Notes:

docs/cli/config.md

@@ -1,22 +1,22 @@
 ---
-summary: "CLI reference for `clawdbot config` (get/set/unset config values)"
+summary: "CLI reference for `moltbot config` (get/set/unset config values)"
 read_when:
   - You want to read or edit config non-interactively
 ---
 
-# `clawdbot config`
+# `moltbot config`
 
 Config helpers: get/set/unset values by path. Run without a subcommand to open
-the configure wizard (same as `clawdbot configure`).
+the configure wizard (same as `moltbot configure`).
 
 ## Examples
 
 ```bash
-clawdbot config get browser.executablePath
-clawdbot config set browser.executablePath "/usr/bin/google-chrome"
-clawdbot config set agents.defaults.heartbeat.every "2h"
-clawdbot config set agents.list[0].tools.exec.node "node-id-or-name"
-clawdbot config unset tools.web.search.apiKey
+moltbot config get browser.executablePath
+moltbot config set browser.executablePath "/usr/bin/google-chrome"
+moltbot config set agents.defaults.heartbeat.every "2h"
+moltbot config set agents.list[0].tools.exec.node "node-id-or-name"
+moltbot config unset tools.web.search.apiKey
 ```
 
 ## Paths
@@ -24,15 +24,15 @@ clawdbot config unset tools.web.search.apiKey
 Paths use dot or bracket notation:
 
 ```bash
-clawdbot config get agents.defaults.workspace
-clawdbot config get agents.list[0].id
+moltbot config get agents.defaults.workspace
+moltbot config get agents.list[0].id
 ```
 
 Use the agent list index to target a specific agent:
 
 ```bash
-clawdbot config get agents.list
-clawdbot config set agents.list[1].tools.exec.node "node-id-or-name"
+moltbot config get agents.list
+moltbot config set agents.list[1].tools.exec.node "node-id-or-name"
 ```
 
 ## Values
@@ -41,9 +41,9 @@ Values are parsed as JSON5 when possible; otherwise they are treated as strings.
 Use `--json` to require JSON5 parsing.
 
 ```bash
-clawdbot config set agents.defaults.heartbeat.every "0m"
-clawdbot config set gateway.port 19001 --json
-clawdbot config set channels.whatsapp.groups '["*"]' --json
+moltbot config set agents.defaults.heartbeat.every "0m"
+moltbot config set gateway.port 19001 --json
+moltbot config set channels.whatsapp.groups '["*"]' --json
 ```
 
 Restart the gateway after edits.

docs/cli/configure.md

@@ -1,18 +1,18 @@
 ---
-summary: "CLI reference for `clawdbot configure` (interactive configuration prompts)"
+summary: "CLI reference for `moltbot configure` (interactive configuration prompts)"
 read_when:
   - You want to tweak credentials, devices, or agent defaults interactively
 ---
 
-# `clawdbot configure`
+# `moltbot configure`
 
 Interactive prompt to set up credentials, devices, and agent defaults.
 
 Note: The **Model** section now includes a multi-select for the
 `agents.defaults.models` allowlist (what shows up in `/model` and the model picker).
 
-Tip: `clawdbot config` without a subcommand opens the same wizard. Use
-`clawdbot config get|set|unset` for non-interactive edits.
+Tip: `moltbot config` without a subcommand opens the same wizard. Use
+`moltbot config get|set|unset` for non-interactive edits.
 
 Related:
 - Gateway configuration reference: [Configuration](/gateway/configuration)
@@ -25,6 +25,6 @@ Notes:
 ## Examples
 
 ```bash
-clawdbot configure
-clawdbot configure --section models --section channels
+moltbot configure
+moltbot configure --section models --section channels
 ```

docs/cli/cron.md

@@ -1,29 +1,29 @@
 ---
-summary: "CLI reference for `clawdbot cron` (schedule and run background jobs)"
+summary: "CLI reference for `moltbot cron` (schedule and run background jobs)"
 read_when:
   - You want scheduled jobs and wakeups
   - You’re debugging cron execution and logs
 ---
 
-# `clawdbot cron`
+# `moltbot cron`
 
 Manage cron jobs for the Gateway scheduler.
 
 Related:
 - Cron jobs: [Cron jobs](/automation/cron-jobs)
 
-Tip: run `clawdbot cron --help` for the full command surface.
+Tip: run `moltbot cron --help` for the full command surface.
 
 ## Common edits
 
 Update delivery settings without changing the message:
 
 ```bash
-clawdbot cron edit <job-id> --deliver --channel telegram --to "123456789"
+moltbot cron edit <job-id> --deliver --channel telegram --to "123456789"
 ```
 
 Disable delivery for an isolated job:
 
 ```bash
-clawdbot cron edit <job-id> --no-deliver
+moltbot cron edit <job-id> --no-deliver
 ```

docs/cli/dashboard.md

@@ -1,16 +1,16 @@
 ---
-summary: "CLI reference for `clawdbot dashboard` (open the Control UI)"
+summary: "CLI reference for `moltbot dashboard` (open the Control UI)"
 read_when:
   - You want to open the Control UI with your current token
   - You want to print the URL without launching a browser
 ---
 
-# `clawdbot dashboard`
+# `moltbot dashboard`
 
 Open the Control UI using your current auth.
 
 ```bash
-clawdbot dashboard
-clawdbot dashboard --no-open
+moltbot dashboard
+moltbot dashboard --no-open
 ```
 

docs/cli/devices.md

@@ -1,55 +1,55 @@
 ---
-summary: "CLI reference for `clawdbot devices` (device pairing + token rotation/revocation)"
+summary: "CLI reference for `moltbot devices` (device pairing + token rotation/revocation)"
 read_when:
   - You are approving device pairing requests
   - You need to rotate or revoke device tokens
 ---
 
-# `clawdbot devices`
+# `moltbot devices`
 
 Manage device pairing requests and device-scoped tokens.
 
 ## Commands
 
-### `clawdbot devices list`
+### `moltbot devices list`
 
 List pending pairing requests and paired devices.
 
 ```
-clawdbot devices list
-clawdbot devices list --json
+moltbot devices list
+moltbot devices list --json
 ```
 
-### `clawdbot devices approve <requestId>`
+### `moltbot devices approve <requestId>`
 
 Approve a pending device pairing request.
 
 ```
-clawdbot devices approve <requestId>
+moltbot devices approve <requestId>
 ```
 
-### `clawdbot devices reject <requestId>`
+### `moltbot devices reject <requestId>`
 
 Reject a pending device pairing request.
 
 ```
-clawdbot devices reject <requestId>
+moltbot devices reject <requestId>
 ```
 
-### `clawdbot devices rotate --device <id> --role <role> [--scope <scope...>]`
+### `moltbot devices rotate --device <id> --role <role> [--scope <scope...>]`
 
 Rotate a device token for a specific role (optionally updating scopes).
 
 ```
-clawdbot devices rotate --device <deviceId> --role operator --scope operator.read --scope operator.write
+moltbot devices rotate --device <deviceId> --role operator --scope operator.read --scope operator.write
 ```
 
-### `clawdbot devices revoke --device <id> --role <role>`
+### `moltbot devices revoke --device <id> --role <role>`
 
 Revoke a device token for a specific role.
 
 ```
-clawdbot devices revoke --device <deviceId> --role node
+moltbot devices revoke --device <deviceId> --role node
 ```
 
 ## Common options

docs/cli/directory.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot directory` (self, peers, groups)"
+summary: "CLI reference for `moltbot directory` (self, peers, groups)"
 read_when:
   - You want to look up contacts/groups/self ids for a channel
   - You are developing a channel directory adapter
 ---
 
-# `clawdbot directory`
+# `moltbot directory`
 
 Directory lookups for channels that support it (contacts/peers, groups, and “me”).
 
@@ -15,15 +15,15 @@ Directory lookups for channels that support it (contacts/peers, groups, and “m
 - `--json`: output JSON
 
 ## Notes
-- `directory` is meant to help you find IDs you can paste into other commands (especially `clawdbot message send --target ...`).
+- `directory` is meant to help you find IDs you can paste into other commands (especially `moltbot message send --target ...`).
 - For many channels, results are config-backed (allowlists / configured groups) rather than a live provider directory.
 - Default output is `id` (and sometimes `name`) separated by a tab; use `--json` for scripting.
 
 ## Using results with `message send`
 
 ```bash
-clawdbot directory peers list --channel slack --query "U0"
-clawdbot message send --channel slack --target user:U012ABCDEF --message "hello"
+moltbot directory peers list --channel slack --query "U0"
+moltbot message send --channel slack --target user:U012ABCDEF --message "hello"
 ```
 
 ## ID formats (by channel)
@@ -40,21 +40,21 @@ clawdbot message send --channel slack --target user:U012ABCDEF --message "hello"
 ## Self (“me”)
 
 ```bash
-clawdbot directory self --channel zalouser
+moltbot directory self --channel zalouser
 ```
 
 ## Peers (contacts/users)
 
 ```bash
-clawdbot directory peers list --channel zalouser
-clawdbot directory peers list --channel zalouser --query "name"
-clawdbot directory peers list --channel zalouser --limit 50
+moltbot directory peers list --channel zalouser
+moltbot directory peers list --channel zalouser --query "name"
+moltbot directory peers list --channel zalouser --limit 50
 ```
 
 ## Groups
 
 ```bash
-clawdbot directory groups list --channel zalouser
-clawdbot directory groups list --channel zalouser --query "work"
-clawdbot directory groups members --channel zalouser --group-id <id>
+moltbot directory groups list --channel zalouser
+moltbot directory groups list --channel zalouser --query "work"
+moltbot directory groups members --channel zalouser --group-id <id>
 ```

docs/cli/dns.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot dns` (wide-area discovery helpers)"
+summary: "CLI reference for `moltbot dns` (wide-area discovery helpers)"
 read_when:
   - You want wide-area discovery (DNS-SD) via Tailscale + CoreDNS
-  - You’re setting up split DNS for clawdbot.internal
+  - You’re setting up split DNS for moltbot.internal
 ---
 
-# `clawdbot dns`
+# `moltbot dns`
 
 DNS helpers for wide-area discovery (Tailscale + CoreDNS). Currently focused on macOS + Homebrew CoreDNS.
 
@@ -16,7 +16,7 @@ Related:
 ## Setup
 
 ```bash
-clawdbot dns setup
-clawdbot dns setup --apply
+moltbot dns setup
+moltbot dns setup --apply
 ```
 

docs/cli/docs.md

@@ -1,15 +1,15 @@
 ---
-summary: "CLI reference for `clawdbot docs` (search the live docs index)"
+summary: "CLI reference for `moltbot docs` (search the live docs index)"
 read_when:
-  - You want to search the live Clawdbot docs from the terminal
+  - You want to search the live Moltbot docs from the terminal
 ---
 
-# `clawdbot docs`
+# `moltbot docs`
 
 Search the live docs index.
 
 ```bash
-clawdbot docs browser extension
-clawdbot docs sandbox allowHostControl
+moltbot docs browser extension
+moltbot docs sandbox allowHostControl
 ```
 

docs/cli/doctor.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot doctor` (health checks + guided repairs)"
+summary: "CLI reference for `moltbot doctor` (health checks + guided repairs)"
 read_when:
   - You have connectivity/auth issues and want guided fixes
   - You updated and want a sanity check
 ---
 
-# `clawdbot doctor`
+# `moltbot doctor`
 
 Health checks + quick fixes for the gateway and channels.
 
@@ -16,14 +16,14 @@ Related:
 ## Examples
 
 ```bash
-clawdbot doctor
-clawdbot doctor --repair
-clawdbot doctor --deep
+moltbot doctor
+moltbot doctor --repair
+moltbot doctor --deep
 ```
 
 Notes:
 - Interactive prompts (like keychain/OAuth fixes) only run when stdin is a TTY and `--non-interactive` is **not** set. Headless runs (cron, Telegram, no terminal) will skip prompts.
-- `--fix` (alias for `--repair`) writes a backup to `~/.clawdbot/clawdbot.json.bak` and drops unknown config keys, listing each removal.
+- `--fix` (alias for `--repair`) writes a backup to `~/.clawdbot/moltbot.json.bak` and drops unknown config keys, listing each removal.
 
 ## macOS: `launchctl` env overrides
 

docs/cli/gateway.md

@@ -1,5 +1,5 @@
 ---
-summary: "Clawdbot Gateway CLI (`clawdbot gateway`) — run, query, and discover gateways"
+summary: "Moltbot Gateway CLI (`moltbot gateway`) — run, query, and discover gateways"
 read_when:
   - Running the Gateway from the CLI (dev or servers)
   - Debugging Gateway auth, bind modes, and connectivity
@@ -8,9 +8,9 @@ read_when:
 
 # Gateway CLI
 
-The Gateway is Clawdbot’s WebSocket server (channels, nodes, sessions, hooks).
+The Gateway is Moltbot’s WebSocket server (channels, nodes, sessions, hooks).
 
-Subcommands in this page live under `clawdbot gateway …`.
+Subcommands in this page live under `moltbot gateway …`.
 
 Related docs:
 - [/gateway/bonjour](/gateway/bonjour)
@@ -22,17 +22,17 @@ Related docs:
 Run a local Gateway process:
 
 ```bash
-clawdbot gateway
+moltbot gateway
 ```
 
 Foreground alias:
 
 ```bash
-clawdbot gateway run
+moltbot gateway run
 ```
 
 Notes:
-- By default, the Gateway refuses to start unless `gateway.mode=local` is set in `~/.clawdbot/clawdbot.json`. Use `--allow-unconfigured` for ad-hoc/dev runs.
+- By default, the Gateway refuses to start unless `gateway.mode=local` is set in `~/.clawdbot/moltbot.json`. Use `--allow-unconfigured` for ad-hoc/dev runs.
 - Binding beyond loopback without auth is blocked (safety guardrail).
 - `SIGUSR1` triggers an in-process restart when authorized (enable `commands.restart` or use the gateway tool/config apply/update).
 - `SIGINT`/`SIGTERM` handlers stop the gateway process, but they don’t restore any custom terminal state. If you wrap the CLI with a TUI or raw-mode input, restore the terminal before exit.
@@ -76,7 +76,7 @@ Shared options (where supported):
 ### `gateway health`
 
 ```bash
-clawdbot gateway health --url ws://127.0.0.1:18789
+moltbot gateway health --url ws://127.0.0.1:18789
 ```
 
 ### `gateway status`
@@ -84,8 +84,8 @@ clawdbot gateway health --url ws://127.0.0.1:18789
 `gateway status` shows the Gateway service (launchd/systemd/schtasks) plus an optional RPC probe.
 
 ```bash
-clawdbot gateway status
-clawdbot gateway status --json
+moltbot gateway status
+moltbot gateway status --json
 ```
 
 Options:
@@ -105,8 +105,8 @@ Options:
 If multiple gateways are reachable, it prints all of them. Multiple gateways are supported when you use isolated profiles/ports (e.g., a rescue bot), but most installs still run a single gateway.
 
 ```bash
-clawdbot gateway probe
-clawdbot gateway probe --json
+moltbot gateway probe
+moltbot gateway probe --json
 ```
 
 #### Remote over SSH (Mac app parity)
@@ -116,7 +116,7 @@ The macOS app “Remote over SSH” mode uses a local port-forward so the remote
 CLI equivalent:
 
 ```bash
-clawdbot gateway probe --ssh user@gateway-host
+moltbot gateway probe --ssh user@gateway-host
 ```
 
 Options:
@@ -133,18 +133,18 @@ Config (optional, used as defaults):
 Low-level RPC helper.
 
 ```bash
-clawdbot gateway call status
-clawdbot gateway call logs.tail --params '{"sinceMs": 60000}'
+moltbot gateway call status
+moltbot gateway call logs.tail --params '{"sinceMs": 60000}'
 ```
 
 ## Manage the Gateway service
 
 ```bash
-clawdbot gateway install
-clawdbot gateway start
-clawdbot gateway stop
-clawdbot gateway restart
-clawdbot gateway uninstall
+moltbot gateway install
+moltbot gateway start
+moltbot gateway stop
+moltbot gateway restart
+moltbot gateway uninstall
 ```
 
 Notes:
@@ -153,10 +153,10 @@ Notes:
 
 ## Discover gateways (Bonjour)
 
-`gateway discover` scans for Gateway beacons (`_clawdbot-gw._tcp`).
+`gateway discover` scans for Gateway beacons (`_moltbot-gw._tcp`).
 
 - Multicast DNS-SD: `local.`
-- Unicast DNS-SD (Wide-Area Bonjour): `clawdbot.internal.` (requires split DNS + DNS server; see [/gateway/bonjour](/gateway/bonjour))
+- Unicast DNS-SD (Wide-Area Bonjour): `moltbot.internal.` (requires split DNS + DNS server; see [/gateway/bonjour](/gateway/bonjour))
 
 Only gateways with Bonjour discovery enabled (default) advertise the beacon.
 
@@ -172,7 +172,7 @@ Wide-Area discovery records include (TXT):
 ### `gateway discover`
 
 ```bash
-clawdbot gateway discover
+moltbot gateway discover
 ```
 
 Options:
@@ -182,6 +182,6 @@ Options:
 Examples:
 
 ```bash
-clawdbot gateway discover --timeout 4000
-clawdbot gateway discover --json | jq '.beacons[].wsUrl'
+moltbot gateway discover --timeout 4000
+moltbot gateway discover --json | jq '.beacons[].wsUrl'
 ```

docs/cli/health.md

@@ -1,17 +1,17 @@
 ---
-summary: "CLI reference for `clawdbot health` (gateway health endpoint via RPC)"
+summary: "CLI reference for `moltbot health` (gateway health endpoint via RPC)"
 read_when:
   - You want to quickly check the running Gateway’s health
 ---
 
-# `clawdbot health`
+# `moltbot health`
 
 Fetch health from the running Gateway.
 
 ```bash
-clawdbot health
-clawdbot health --json
-clawdbot health --verbose
+moltbot health
+moltbot health --json
+moltbot health --verbose
 ```
 
 Notes:

docs/cli/hooks.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot hooks` (agent hooks)"
+summary: "CLI reference for `moltbot hooks` (agent hooks)"
 read_when:
   - You want to manage agent hooks
   - You want to install or update hooks
 ---
 
-# `clawdbot hooks`
+# `moltbot hooks`
 
 Manage agent hooks (event-driven automations for commands like `/new`, `/reset`, and gateway startup).
 
@@ -16,7 +16,7 @@ Related:
 ## List All Hooks
 
 ```bash
-clawdbot hooks list
+moltbot hooks list
 ```
 
 List all discovered hooks from workspace, managed, and bundled directories.
@@ -41,7 +41,7 @@ Ready:
 **Example (verbose):**
 
 ```bash
-clawdbot hooks list --verbose
+moltbot hooks list --verbose
 ```
 
 Shows missing requirements for ineligible hooks.
@@ -49,7 +49,7 @@ Shows missing requirements for ineligible hooks.
 **Example (JSON):**
 
 ```bash
-clawdbot hooks list --json
+moltbot hooks list --json
 ```
 
 Returns structured JSON for programmatic use.
@@ -57,7 +57,7 @@ Returns structured JSON for programmatic use.
 ## Get Hook Information
 
 ```bash
-clawdbot hooks info <name>
+moltbot hooks info <name>
 ```
 
 Show detailed information about a specific hook.
@@ -71,7 +71,7 @@ Show detailed information about a specific hook.
 **Example:**
 
 ```bash
-clawdbot hooks info session-memory
+moltbot hooks info session-memory
 ```
 
 **Output:**
@@ -82,9 +82,9 @@ clawdbot hooks info session-memory
 Save session context to memory when /new command is issued
 
 Details:
-  Source: clawdbot-bundled
-  Path: /path/to/clawdbot/hooks/bundled/session-memory/HOOK.md
-  Handler: /path/to/clawdbot/hooks/bundled/session-memory/handler.ts
+  Source: moltbot-bundled
+  Path: /path/to/moltbot/hooks/bundled/session-memory/HOOK.md
+  Handler: /path/to/moltbot/hooks/bundled/session-memory/handler.ts
   Homepage: https://docs.molt.bot/hooks#session-memory
   Events: command:new
 
@@ -95,7 +95,7 @@ Requirements:
 ## Check Hooks Eligibility
 
 ```bash
-clawdbot hooks check
+moltbot hooks check
 ```
 
 Show summary of hook eligibility status (how many are ready vs. not ready).
@@ -116,12 +116,12 @@ Not ready: 0
 ## Enable a Hook
 
 ```bash
-clawdbot hooks enable <name>
+moltbot hooks enable <name>
 ```
 
 Enable a specific hook by adding it to your config (`~/.clawdbot/config.json`).
 
-**Note:** Hooks managed by plugins show `plugin:<id>` in `clawdbot hooks list` and
+**Note:** Hooks managed by plugins show `plugin:<id>` in `moltbot hooks list` and
 can’t be enabled/disabled here. Enable/disable the plugin instead.
 
 **Arguments:**
@@ -130,7 +130,7 @@ can’t be enabled/disabled here. Enable/disable the plugin instead.
 **Example:**
 
 ```bash
-clawdbot hooks enable session-memory
+moltbot hooks enable session-memory
 ```
 
 **Output:**
@@ -150,7 +150,7 @@ clawdbot hooks enable session-memory
 ## Disable a Hook
 
 ```bash
-clawdbot hooks disable <name>
+moltbot hooks disable <name>
 ```
 
 Disable a specific hook by updating your config.
@@ -161,7 +161,7 @@ Disable a specific hook by updating your config.
 **Example:**
 
 ```bash
-clawdbot hooks disable command-logger
+moltbot hooks disable command-logger
 ```
 
 **Output:**
@@ -176,7 +176,7 @@ clawdbot hooks disable command-logger
 ## Install Hooks
 
 ```bash
-clawdbot hooks install <path-or-spec>
+moltbot hooks install <path-or-spec>
 ```
 
 Install a hook pack from a local folder/archive or npm.
@@ -195,23 +195,23 @@ Install a hook pack from a local folder/archive or npm.
 
 ```bash
 # Local directory
-clawdbot hooks install ./my-hook-pack
+moltbot hooks install ./my-hook-pack
 
 # Local archive
-clawdbot hooks install ./my-hook-pack.zip
+moltbot hooks install ./my-hook-pack.zip
 
 # NPM package
-clawdbot hooks install @clawdbot/my-hook-pack
+moltbot hooks install @moltbot/my-hook-pack
 
 # Link a local directory without copying
-clawdbot hooks install -l ./my-hook-pack
+moltbot hooks install -l ./my-hook-pack
 ```
 
 ## Update Hooks
 
 ```bash
-clawdbot hooks update <id>
-clawdbot hooks update --all
+moltbot hooks update <id>
+moltbot hooks update --all
 ```
 
 Update installed hook packs (npm installs only).
@@ -229,7 +229,7 @@ Saves session context to memory when you issue `/new`.
 **Enable:**
 
 ```bash
-clawdbot hooks enable session-memory
+moltbot hooks enable session-memory
 ```
 
 **Output:** `~/clawd/memory/YYYY-MM-DD-slug.md`
@@ -243,7 +243,7 @@ Logs all command events to a centralized audit file.
 **Enable:**
 
 ```bash
-clawdbot hooks enable command-logger
+moltbot hooks enable command-logger
 ```
 
 **Output:** `~/.clawdbot/logs/commands.log`
@@ -270,7 +270,7 @@ Swaps injected `SOUL.md` content with `SOUL_EVIL.md` during a purge window or by
 **Enable:**
 
 ```bash
-clawdbot hooks enable soul-evil
+moltbot hooks enable soul-evil
 ```
 
 **See:** [SOUL Evil Hook](/hooks/soul-evil)
@@ -284,7 +284,7 @@ Runs `BOOT.md` when the gateway starts (after channels start).
 **Enable**:
 
 ```bash
-clawdbot hooks enable boot-md
+moltbot hooks enable boot-md
 ```
 
 **See:** [boot-md documentation](/hooks#boot-md)

docs/cli/index.md

@@ -1,5 +1,5 @@
 ---
-summary: "Clawdbot CLI reference for `clawdbot` commands, subcommands, and options"
+summary: "Moltbot CLI reference for `moltbot` commands, subcommands, and options"
 read_when:
   - Adding or modifying CLI commands or options
   - Documenting new command surfaces
@@ -56,7 +56,7 @@ This page describes the current CLI behavior. If commands change, update this do
 - `--dev`: isolate state under `~/.clawdbot-dev` and shift default ports.
 - `--profile <name>`: isolate state under `~/.clawdbot-<name>`.
 - `--no-color`: disable ANSI colors.
-- `--update`: shorthand for `clawdbot update` (source installs only).
+- `--update`: shorthand for `moltbot update` (source installs only).
 - `-V`, `--version`, `-v`: print version and exit.
 
 ## Output styling
@@ -69,7 +69,7 @@ This page describes the current CLI behavior. If commands change, update this do
 
 ## Color palette
 
-Clawdbot uses a lobster palette for CLI output.
+Moltbot uses a lobster palette for CLI output.
 
 - `accent` (#FF5A2D): headings, labels, primary highlights.
 - `accentBright` (#FF7A3D): command names, emphasis.
@@ -85,7 +85,7 @@ Palette source of truth: `src/terminal/palette.ts` (aka “lobster seam”).
 ## Command tree
 
 ```
-clawdbot [--dev] [--profile <name>] <command>
+moltbot [--dev] [--profile <name>] <command>
   setup
   onboard
   configure
@@ -236,23 +236,23 @@ clawdbot [--dev] [--profile <name>] <command>
   tui
 ```
 
-Note: plugins can add additional top-level commands (for example `clawdbot voicecall`).
+Note: plugins can add additional top-level commands (for example `moltbot voicecall`).
 
 ## Security
 
-- `clawdbot security audit` — audit config + local state for common security foot-guns.
-- `clawdbot security audit --deep` — best-effort live Gateway probe.
-- `clawdbot security audit --fix` — tighten safe defaults and chmod state/config.
+- `moltbot security audit` — audit config + local state for common security foot-guns.
+- `moltbot security audit --deep` — best-effort live Gateway probe.
+- `moltbot security audit --fix` — tighten safe defaults and chmod state/config.
 
 ## Plugins
 
 Manage extensions and their config:
 
-- `clawdbot plugins list` — discover plugins (use `--json` for machine output).
-- `clawdbot plugins info <id>` — show details for a plugin.
-- `clawdbot plugins install <path|.tgz|npm-spec>` — install a plugin (or add a plugin path to `plugins.load.paths`).
-- `clawdbot plugins enable <id>` / `disable <id>` — toggle `plugins.entries.<id>.enabled`.
-- `clawdbot plugins doctor` — report plugin load errors.
+- `moltbot plugins list` — discover plugins (use `--json` for machine output).
+- `moltbot plugins info <id>` — show details for a plugin.
+- `moltbot plugins install <path|.tgz|npm-spec>` — install a plugin (or add a plugin path to `plugins.load.paths`).
+- `moltbot plugins enable <id>` / `disable <id>` — toggle `plugins.entries.<id>.enabled`.
+- `moltbot plugins doctor` — report plugin load errors.
 
 Most plugin changes require a gateway restart. See [/plugin](/plugin).
 
@@ -260,9 +260,9 @@ Most plugin changes require a gateway restart. See [/plugin](/plugin).
 
 Vector search over `MEMORY.md` + `memory/*.md`:
 
-- `clawdbot memory status` — show index stats.
-- `clawdbot memory index` — reindex memory files.
-- `clawdbot memory search "<query>"` — semantic search over memory.
+- `moltbot memory status` — show index stats.
+- `moltbot memory index` — reindex memory files.
+- `moltbot memory search "<query>"` — semantic search over memory.
 
 ## Chat slash commands
 
@@ -335,7 +335,7 @@ Options:
 Interactive configuration wizard (models, channels, skills, gateway).
 
 ### `config`
-Non-interactive config helpers (get/set/unset). Running `clawdbot config` with no
+Non-interactive config helpers (get/set/unset). Running `moltbot config` with no
 subcommand launches the wizard.
 
 Subcommands:
@@ -359,8 +359,8 @@ Manage chat channel accounts (WhatsApp/Telegram/Discord/Google Chat/Slack/Matter
 
 Subcommands:
 - `channels list`: show configured channels and auth profiles.
-- `channels status`: check gateway reachability and channel health (`--probe` runs extra checks; use `clawdbot health` or `clawdbot status --deep` for gateway health probes).
-- Tip: `channels status` prints warnings with suggested fixes when it can detect common misconfigurations (then points you to `clawdbot doctor`).
+- `channels status`: check gateway reachability and channel health (`--probe` runs extra checks; use `moltbot health` or `moltbot status --deep` for gateway health probes).
+- Tip: `channels status` prints warnings with suggested fixes when it can detect common misconfigurations (then points you to `moltbot doctor`).
 - `channels logs`: show recent channel logs from the gateway log file.
 - `channels add`: wizard-style setup when no flags are passed; flags switch to non-interactive mode.
 - `channels remove`: disable by default; pass `--delete` to remove config entries without prompts.
@@ -394,11 +394,11 @@ More detail: [/concepts/oauth](/concepts/oauth)
 
 Examples:
 ```bash
-clawdbot channels add --channel telegram --account alerts --name "Alerts Bot" --token $TELEGRAM_BOT_TOKEN
-clawdbot channels add --channel discord --account work --name "Work Bot" --token $DISCORD_BOT_TOKEN
-clawdbot channels remove --channel discord --account work --delete
-clawdbot channels status --probe
-clawdbot status --deep
+moltbot channels add --channel telegram --account alerts --name "Alerts Bot" --token $TELEGRAM_BOT_TOKEN
+moltbot channels add --channel discord --account work --name "Work Bot" --token $DISCORD_BOT_TOKEN
+moltbot channels remove --channel discord --account work --delete
+moltbot channels status --probe
+moltbot status --deep
 ```
 
 ### `skills`
@@ -455,8 +455,8 @@ Subcommands:
 - `message event <list|create>`
 
 Examples:
-- `clawdbot message send --target +15555550123 --message "Hi"`
-- `clawdbot message poll --channel discord --target channel:123 --poll-question "Snack?" --poll-option Pizza --poll-option Sushi`
+- `moltbot message send --target +15555550123 --message "Hi"`
+- `moltbot message poll --channel discord --target channel:123 --poll-question "Snack?" --poll-option Pizza --poll-option Sushi`
 
 ### `agent`
 Run one agent turn via the Gateway (or `--local` embedded).
@@ -526,11 +526,11 @@ Notes:
 - Overview includes Gateway + node host service status when available.
 
 ### Usage tracking
-Clawdbot can surface provider usage/quota when OAuth/API creds are available.
+Moltbot can surface provider usage/quota when OAuth/API creds are available.
 
 Surfaces:
 - `/status` (adds a short provider usage line when available)
-- `clawdbot status --usage` (prints full provider breakdown)
+- `moltbot status --usage` (prints full provider breakdown)
 - macOS menu bar (Usage section under Context)
 
 Notes:
@@ -624,7 +624,7 @@ Subcommands:
 Notes:
 - `gateway status` probes the Gateway RPC by default using the service’s resolved port/config (override with `--url/--token/--password`).
 - `gateway status` supports `--no-probe`, `--deep`, and `--json` for scripting.
-- `gateway status` also surfaces legacy or extra gateway services when it can detect them (`--deep` adds system-level scans). Profile-named Clawdbot services are treated as first-class and aren't flagged as "extra".
+- `gateway status` also surfaces legacy or extra gateway services when it can detect them (`--deep` adds system-level scans). Profile-named Moltbot services are treated as first-class and aren't flagged as "extra".
 - `gateway status` prints which config path the CLI uses vs which config the service likely uses (service env), plus the resolved probe target URL.
 - `gateway install|uninstall|start|stop|restart` support `--json` for scripting (default output stays human-friendly).
 - `gateway install` defaults to Node runtime; bun is **not recommended** (WhatsApp/Telegram bugs).
@@ -639,11 +639,11 @@ Notes:
 
 Examples:
 ```bash
-clawdbot logs --follow
-clawdbot logs --limit 200
-clawdbot logs --plain
-clawdbot logs --json
-clawdbot logs --no-color
+moltbot logs --follow
+moltbot logs --limit 200
+moltbot logs --plain
+moltbot logs --json
+moltbot logs --no-color
 ```
 
 ### `gateway <subcommand>`
@@ -674,12 +674,12 @@ Preferred Anthropic auth (setup-token):
 
 ```bash
 claude setup-token
-clawdbot models auth setup-token --provider anthropic
-clawdbot models status
+moltbot models auth setup-token --provider anthropic
+moltbot models status
 ```
 
 ### `models` (root)
-`clawdbot models` is an alias for `models status`.
+`moltbot models` is an alias for `models status`.
 
 Root options:
 - `--status-json` (alias for `models status --json`)
@@ -807,7 +807,7 @@ All `cron` commands accept `--url`, `--token`, `--timeout`, `--expect-final`.
 ## Node host
 
 `node` runs a **headless node host** or manages it as a background service. See
-[`clawdbot node`](/cli/node).
+[`moltbot node`](/cli/node).
 
 Subcommands:
 - `node run --host <gateway-host> --port 18789`
@@ -856,7 +856,7 @@ Location:
 
 ## Browser
 
-Browser control CLI (dedicated Chrome/Brave/Edge/Chromium). See [`clawdbot browser`](/cli/browser) and the [Browser tool](/tools/browser).
+Browser control CLI (dedicated Chrome/Brave/Edge/Chromium). See [`moltbot browser`](/cli/browser) and the [Browser tool](/tools/browser).
 
 Common options:
 - `--url`, `--token`, `--timeout`, `--json`

docs/cli/logs.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot logs` (tail gateway logs via RPC)"
+summary: "CLI reference for `moltbot logs` (tail gateway logs via RPC)"
 read_when:
   - You need to tail Gateway logs remotely (without SSH)
   - You want JSON log lines for tooling
 ---
 
-# `clawdbot logs`
+# `moltbot logs`
 
 Tail Gateway file logs over RPC (works in remote mode).
 
@@ -15,9 +15,9 @@ Related:
 ## Examples
 
 ```bash
-clawdbot logs
-clawdbot logs --follow
-clawdbot logs --json
-clawdbot logs --limit 500
+moltbot logs
+moltbot logs --follow
+moltbot logs --json
+moltbot logs --limit 500
 ```
 

docs/cli/memory.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot memory` (status/index/search)"
+summary: "CLI reference for `moltbot memory` (status/index/search)"
 read_when:
   - You want to index or search semantic memory
   - You’re debugging memory availability or indexing
 ---
 
-# `clawdbot memory`
+# `moltbot memory`
 
 Manage semantic memory indexing and search.
 Provided by the active memory plugin (default: `memory-core`; set `plugins.slots.memory = "none"` to disable).
@@ -17,15 +17,15 @@ Related:
 ## Examples
 
 ```bash
-clawdbot memory status
-clawdbot memory status --deep
-clawdbot memory status --deep --index
-clawdbot memory status --deep --index --verbose
-clawdbot memory index
-clawdbot memory index --verbose
-clawdbot memory search "release checklist"
-clawdbot memory status --agent main
-clawdbot memory index --agent main --verbose
+moltbot memory status
+moltbot memory status --deep
+moltbot memory status --deep --index
+moltbot memory status --deep --index --verbose
+moltbot memory index
+moltbot memory index --verbose
+moltbot memory search "release checklist"
+moltbot memory status --agent main
+moltbot memory index --agent main --verbose
 ```
 
 ## Options

docs/cli/message.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot message` (send + channel actions)"
+summary: "CLI reference for `moltbot message` (send + channel actions)"
 read_when:
   - Adding or modifying message CLI actions
   - Changing outbound channel behavior
 ---
 
-# `clawdbot message`
+# `moltbot message`
 
 Single outbound command for sending messages and channel actions
 (Discord/Google Chat/Slack/Mattermost (plugin)/Telegram/WhatsApp/Signal/iMessage/MS Teams).
@@ -13,7 +13,7 @@ Single outbound command for sending messages and channel actions
 ## Usage
 
 ```
-clawdbot message <subcommand> [flags]
+moltbot message <subcommand> [flags]
 ```
 
 Channel selection:
@@ -34,7 +34,7 @@ Target formats (`--target`):
 
 Name lookup:
 - For supported providers (Discord/Slack/etc), channel names like `Help` or `#help` are resolved via the directory cache.
-- On cache miss, Clawdbot will attempt a live directory lookup when the provider supports it.
+- On cache miss, Moltbot will attempt a live directory lookup when the provider supports it.
 
 ## Common flags
 
@@ -181,13 +181,13 @@ Name lookup:
 
 Send a Discord reply:
 ```
-clawdbot message send --channel discord \
+moltbot message send --channel discord \
   --target channel:123 --message "hi" --reply-to 456
 ```
 
 Create a Discord poll:
 ```
-clawdbot message poll --channel discord \
+moltbot message poll --channel discord \
   --target channel:123 \
   --poll-question "Snack?" \
   --poll-option Pizza --poll-option Sushi \
@@ -196,13 +196,13 @@ clawdbot message poll --channel discord \
 
 Send a Teams proactive message:
 ```
-clawdbot message send --channel msteams \
+moltbot message send --channel msteams \
   --target conversation:19:abc@thread.tacv2 --message "hi"
 ```
 
 Create a Teams poll:
 ```
-clawdbot message poll --channel msteams \
+moltbot message poll --channel msteams \
   --target conversation:19:abc@thread.tacv2 \
   --poll-question "Lunch?" \
   --poll-option Pizza --poll-option Sushi
@@ -210,19 +210,19 @@ clawdbot message poll --channel msteams \
 
 React in Slack:
 ```
-clawdbot message react --channel slack \
+moltbot message react --channel slack \
   --target C123 --message-id 456 --emoji "✅"
 ```
 
 React in a Signal group:
 ```
-clawdbot message react --channel signal \
+moltbot message react --channel signal \
   --target signal:group:abc123 --message-id 1737630212345 \
   --emoji "✅" --target-author-uuid 123e4567-e89b-12d3-a456-426614174000
 ```
 
 Send Telegram inline buttons:
 ```
-clawdbot message send --channel telegram --target @mychat --message "Choose:" \
+moltbot message send --channel telegram --target @mychat --message "Choose:" \
   --buttons '[ [{"text":"Yes","callback_data":"cmd:yes"}], [{"text":"No","callback_data":"cmd:no"}] ]'
 ```

docs/cli/models.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot models` (status/list/set/scan, aliases, fallbacks, auth)"
+summary: "CLI reference for `moltbot models` (status/list/set/scan, aliases, fallbacks, auth)"
 read_when:
   - You want to change default models or view provider auth status
   - You want to scan available models/providers and debug auth profiles
 ---
 
-# `clawdbot models`
+# `moltbot models`
 
 Model discovery, scanning, and configuration (default model, fallbacks, auth profiles).
 
@@ -16,13 +16,13 @@ Related:
 ## Common commands
 
 ```bash
-clawdbot models status
-clawdbot models list
-clawdbot models set <model-or-alias>
-clawdbot models scan
+moltbot models status
+moltbot models list
+moltbot models set <model-or-alias>
+moltbot models scan
 ```
 
-`clawdbot models status` shows the resolved default/fallbacks plus an auth overview.
+`moltbot models status` shows the resolved default/fallbacks plus an auth overview.
 When provider usage snapshots are available, the OAuth/token status section includes
 provider usage headers.
 Add `--probe` to run live auth probes against each configured provider profile.
@@ -31,7 +31,7 @@ Probes are real requests (may consume tokens and trigger rate limits).
 Notes:
 - `models set <model-or-alias>` accepts `provider/model` or an alias.
 - Model refs are parsed by splitting on the **first** `/`. If the model ID includes `/` (OpenRouter-style), include the provider prefix (example: `openrouter/moonshotai/kimi-k2`).
-- If you omit the provider, Clawdbot treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
+- If you omit the provider, Moltbot treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
 
 ### `models status`
 Options:
@@ -48,20 +48,20 @@ Options:
 ## Aliases + fallbacks
 
 ```bash
-clawdbot models aliases list
-clawdbot models fallbacks list
+moltbot models aliases list
+moltbot models fallbacks list
 ```
 
 ## Auth profiles
 
 ```bash
-clawdbot models auth add
-clawdbot models auth login --provider <id>
-clawdbot models auth setup-token
-clawdbot models auth paste-token
+moltbot models auth add
+moltbot models auth login --provider <id>
+moltbot models auth setup-token
+moltbot models auth paste-token
 ```
 `models auth login` runs a provider plugin’s auth flow (OAuth/API key). Use
-`clawdbot plugins list` to see which providers are installed.
+`moltbot plugins list` to see which providers are installed.
 
 Notes:
 - `setup-token` prompts for a setup-token value (generate it with `claude setup-token` on any machine).

docs/cli/node.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot node` (headless node host)"
+summary: "CLI reference for `moltbot node` (headless node host)"
 read_when:
   - Running the headless node host
   - Pairing a non-macOS node for system.run
 ---
 
-# `clawdbot node`
+# `moltbot node`
 
 Run a **headless node host** that connects to the Gateway WebSocket and exposes
 `system.run` / `system.which` on this machine.
@@ -44,7 +44,7 @@ Disable it on the node if needed:
 ## Run (foreground)
 
 ```bash
-clawdbot node run --host <gateway-host> --port 18789
+moltbot node run --host <gateway-host> --port 18789
 ```
 
 Options:
@@ -60,7 +60,7 @@ Options:
 Install a headless node host as a user service.
 
 ```bash
-clawdbot node install --host <gateway-host> --port 18789
+moltbot node install --host <gateway-host> --port 18789
 ```
 
 Options:
@@ -76,13 +76,13 @@ Options:
 Manage the service:
 
 ```bash
-clawdbot node status
-clawdbot node stop
-clawdbot node restart
-clawdbot node uninstall
+moltbot node status
+moltbot node stop
+moltbot node restart
+moltbot node uninstall
 ```
 
-Use `clawdbot node run` for a foreground node host (no service).
+Use `moltbot node run` for a foreground node host (no service).
 
 Service commands accept `--json` for machine-readable output.
 
@@ -92,8 +92,8 @@ The first connection creates a pending node pair request on the Gateway.
 Approve it via:
 
 ```bash
-clawdbot nodes pending
-clawdbot nodes approve <requestId>
+moltbot nodes pending
+moltbot nodes approve <requestId>
 ```
 
 The node host stores its node id, token, display name, and gateway connection info in
@@ -105,4 +105,4 @@ The node host stores its node id, token, display name, and gateway connection in
 
 - `~/.clawdbot/exec-approvals.json`
 - [Exec approvals](/tools/exec-approvals)
-- `clawdbot approvals --node <id|name|ip>` (edit from the Gateway)
+- `moltbot approvals --node <id|name|ip>` (edit from the Gateway)

docs/cli/nodes.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot nodes` (list/status/approve/invoke, camera/canvas/screen)"
+summary: "CLI reference for `moltbot nodes` (list/status/approve/invoke, camera/canvas/screen)"
 read_when:
   - You’re managing paired nodes (cameras, screen, canvas)
   - You need to approve requests or invoke node commands
 ---
 
-# `clawdbot nodes`
+# `moltbot nodes`
 
 Manage paired nodes (devices) and invoke node capabilities.
 
@@ -20,14 +20,14 @@ Common options:
 ## Common commands
 
 ```bash
-clawdbot nodes list
-clawdbot nodes list --connected
-clawdbot nodes list --last-connected 24h
-clawdbot nodes pending
-clawdbot nodes approve <requestId>
-clawdbot nodes status
-clawdbot nodes status --connected
-clawdbot nodes status --last-connected 24h
+moltbot nodes list
+moltbot nodes list --connected
+moltbot nodes list --last-connected 24h
+moltbot nodes pending
+moltbot nodes approve <requestId>
+moltbot nodes status
+moltbot nodes status --connected
+moltbot nodes status --last-connected 24h
 ```
 
 `nodes list` prints pending/paired tables. Paired rows include the most recent connect age (Last Connect).
@@ -37,10 +37,10 @@ filter to nodes that connected within a duration (e.g. `24h`, `7d`).
 ## Invoke / run
 
 ```bash
-clawdbot nodes invoke --node <id|name|ip> --command <command> --params <json>
-clawdbot nodes run --node <id|name|ip> <command...>
-clawdbot nodes run --raw "git status"
-clawdbot nodes run --agent main --node <id|name|ip> --raw "git status"
+moltbot nodes invoke --node <id|name|ip> --command <command> --params <json>
+moltbot nodes run --node <id|name|ip> <command...>
+moltbot nodes run --raw "git status"
+moltbot nodes run --agent main --node <id|name|ip> --raw "git status"
 ```
 
 Invoke flags:

docs/cli/onboard.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `clawdbot onboard` (interactive onboarding wizard)"
+summary: "CLI reference for `moltbot onboard` (interactive onboarding wizard)"
 read_when:
   - You want guided setup for gateway, workspace, auth, channels, and skills
 ---
 
-# `clawdbot onboard`
+# `moltbot onboard`
 
 Interactive onboarding wizard (local or remote Gateway setup).
 
@@ -14,13 +14,13 @@ Related:
 ## Examples
 
 ```bash
-clawdbot onboard
-clawdbot onboard --flow quickstart
-clawdbot onboard --flow manual
-clawdbot onboard --mode remote --remote-url ws://gateway-host:18789
+moltbot onboard
+moltbot onboard --flow quickstart
+moltbot onboard --flow manual
+moltbot onboard --mode remote --remote-url ws://gateway-host:18789
 ```
 
 Flow notes:
 - `quickstart`: minimal prompts, auto-generates a gateway token.
 - `manual`: full prompts for port/bind/auth (alias of `advanced`).
-- Fastest first chat: `clawdbot dashboard` (Control UI, no channel setup).
+- Fastest first chat: `moltbot dashboard` (Control UI, no channel setup).

docs/cli/pairing.md

@@ -1,10 +1,10 @@
 ---
-summary: "CLI reference for `clawdbot pairing` (approve/list pairing requests)"
+summary: "CLI reference for `moltbot pairing` (approve/list pairing requests)"
 read_when:
   - You’re using pairing-mode DMs and need to approve senders
 ---
 
-# `clawdbot pairing`
+# `moltbot pairing`
 
 Approve or inspect DM pairing requests (for channels that support pairing).
 
@@ -14,7 +14,7 @@ Related:
 ## Commands
 
 ```bash
-clawdbot pairing list whatsapp
-clawdbot pairing approve whatsapp <code> --notify
+moltbot pairing list whatsapp
+moltbot pairing approve whatsapp <code> --notify
 ```
 

docs/cli/plugins.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot plugins` (list, install, enable/disable, doctor)"
+summary: "CLI reference for `moltbot plugins` (list, install, enable/disable, doctor)"
 read_when:
   - You want to install or manage in-process Gateway plugins
   - You want to debug plugin load failures
 ---
 
-# `clawdbot plugins`
+# `moltbot plugins`
 
 Manage Gateway plugins/extensions (loaded in-process).
 
@@ -17,26 +17,26 @@ Related:
 ## Commands
 
 ```bash
-clawdbot plugins list
-clawdbot plugins info <id>
-clawdbot plugins enable <id>
-clawdbot plugins disable <id>
-clawdbot plugins doctor
-clawdbot plugins update <id>
-clawdbot plugins update --all
+moltbot plugins list
+moltbot plugins info <id>
+moltbot plugins enable <id>
+moltbot plugins disable <id>
+moltbot plugins doctor
+moltbot plugins update <id>
+moltbot plugins update --all
 ```
 
-Bundled plugins ship with Clawdbot but start disabled. Use `plugins enable` to
+Bundled plugins ship with Moltbot but start disabled. Use `plugins enable` to
 activate them.
 
-All plugins must ship a `clawdbot.plugin.json` file with an inline JSON Schema
+All plugins must ship a `moltbot.plugin.json` file with an inline JSON Schema
 (`configSchema`, even if empty). Missing/invalid manifests or schemas prevent
 the plugin from loading and fail config validation.
 
 ### Install
 
 ```bash
-clawdbot plugins install <path-or-spec>
+moltbot plugins install <path-or-spec>
 ```
 
 Security note: treat plugin installs like running code. Prefer pinned versions.
@@ -46,15 +46,15 @@ Supported archives: `.zip`, `.tgz`, `.tar.gz`, `.tar`.
 Use `--link` to avoid copying a local directory (adds to `plugins.load.paths`):
 
 ```bash
-clawdbot plugins install -l ./my-plugin
+moltbot plugins install -l ./my-plugin
 ```
 
 ### Update
 
 ```bash
-clawdbot plugins update <id>
-clawdbot plugins update --all
-clawdbot plugins update <id> --dry-run
+moltbot plugins update <id>
+moltbot plugins update --all
+moltbot plugins update <id> --dry-run
 ```
 
 Updates only apply to plugins installed from npm (tracked in `plugins.installs`).

docs/cli/reset.md

@@ -1,17 +1,17 @@
 ---
-summary: "CLI reference for `clawdbot reset` (reset local state/config)"
+summary: "CLI reference for `moltbot reset` (reset local state/config)"
 read_when:
   - You want to wipe local state while keeping the CLI installed
   - You want a dry-run of what would be removed
 ---
 
-# `clawdbot reset`
+# `moltbot reset`
 
 Reset local config/state (keeps the CLI installed).
 
 ```bash
-clawdbot reset
-clawdbot reset --dry-run
-clawdbot reset --scope config+creds+sessions --yes --non-interactive
+moltbot reset
+moltbot reset --dry-run
+moltbot reset --scope config+creds+sessions --yes --non-interactive
 ```
 

docs/cli/sandbox.md

@@ -11,29 +11,29 @@ Manage Docker-based sandbox containers for isolated agent execution.
 
 ## Overview
 
-Clawdbot can run agents in isolated Docker containers for security. The `sandbox` commands help you manage these containers, especially after updates or configuration changes.
+Moltbot can run agents in isolated Docker containers for security. The `sandbox` commands help you manage these containers, especially after updates or configuration changes.
 
 ## Commands
 
-### `clawdbot sandbox explain`
+### `moltbot sandbox explain`
 
 Inspect the **effective** sandbox mode/scope/workspace access, sandbox tool policy, and elevated gates (with fix-it config key paths).
 
 ```bash
-clawdbot sandbox explain
-clawdbot sandbox explain --session agent:main:main
-clawdbot sandbox explain --agent work
-clawdbot sandbox explain --json
+moltbot sandbox explain
+moltbot sandbox explain --session agent:main:main
+moltbot sandbox explain --agent work
+moltbot sandbox explain --json
 ```
 
-### `clawdbot sandbox list`
+### `moltbot sandbox list`
 
 List all sandbox containers with their status and configuration.
 
 ```bash
-clawdbot sandbox list
-clawdbot sandbox list --browser  # List only browser containers
-clawdbot sandbox list --json     # JSON output
+moltbot sandbox list
+moltbot sandbox list --browser  # List only browser containers
+moltbot sandbox list --json     # JSON output
 ```
 
 **Output includes:**
@@ -43,16 +43,16 @@ clawdbot sandbox list --json     # JSON output
 - Idle time (time since last use)
 - Associated session/agent
 
-### `clawdbot sandbox recreate`
+### `moltbot sandbox recreate`
 
 Remove sandbox containers to force recreation with updated images/config.
 
 ```bash
-clawdbot sandbox recreate --all                # Recreate all containers
-clawdbot sandbox recreate --session main       # Specific session
-clawdbot sandbox recreate --agent mybot        # Specific agent
-clawdbot sandbox recreate --browser            # Only browser containers
-clawdbot sandbox recreate --all --force        # Skip confirmation
+moltbot sandbox recreate --all                # Recreate all containers
+moltbot sandbox recreate --session main       # Specific session
+moltbot sandbox recreate --agent mybot        # Specific agent
+moltbot sandbox recreate --browser            # Only browser containers
+moltbot sandbox recreate --all --force        # Skip confirmation
 ```
 
 **Options:**
@@ -70,14 +70,14 @@ clawdbot sandbox recreate --all --force        # Skip confirmation
 
 ```bash
 # Pull new image
-docker pull clawdbot-sandbox:latest
-docker tag clawdbot-sandbox:latest clawdbot-sandbox:bookworm-slim
+docker pull moltbot-sandbox:latest
+docker tag moltbot-sandbox:latest moltbot-sandbox:bookworm-slim
 
 # Update config to use new image
 # Edit config: agents.defaults.sandbox.docker.image (or agents.list[].sandbox.docker.image)
 
 # Recreate containers
-clawdbot sandbox recreate --all
+moltbot sandbox recreate --all
 ```
 
 ### After changing sandbox configuration
@@ -86,15 +86,15 @@ clawdbot sandbox recreate --all
 # Edit config: agents.defaults.sandbox.* (or agents.list[].sandbox.*)
 
 # Recreate to apply new config
-clawdbot sandbox recreate --all
+moltbot sandbox recreate --all
 ```
 
 ### After changing setupCommand
 
 ```bash
-clawdbot sandbox recreate --all
+moltbot sandbox recreate --all
 # or just one agent:
-clawdbot sandbox recreate --agent family
+moltbot sandbox recreate --agent family
 ```
 
 
@@ -102,7 +102,7 @@ clawdbot sandbox recreate --agent family
 
 ```bash
 # Update only one agent's containers
-clawdbot sandbox recreate --agent alfred
+moltbot sandbox recreate --agent alfred
 ```
 
 ## Why is this needed?
@@ -112,14 +112,14 @@ clawdbot sandbox recreate --agent alfred
 - Containers are only pruned after 24h of inactivity
 - Regularly-used agents keep old containers running indefinitely
 
-**Solution:** Use `clawdbot sandbox recreate` to force removal of old containers. They'll be recreated automatically with current settings when next needed.
+**Solution:** Use `moltbot sandbox recreate` to force removal of old containers. They'll be recreated automatically with current settings when next needed.
 
-Tip: prefer `clawdbot sandbox recreate` over manual `docker rm`. It uses the
+Tip: prefer `moltbot sandbox recreate` over manual `docker rm`. It uses the
 Gateway’s container naming and avoids mismatches when scope/session keys change.
 
 ## Configuration
 
-Sandbox settings live in `~/.clawdbot/clawdbot.json` under `agents.defaults.sandbox` (per-agent overrides go in `agents.list[].sandbox`):
+Sandbox settings live in `~/.clawdbot/moltbot.json` under `agents.defaults.sandbox` (per-agent overrides go in `agents.list[].sandbox`):
 
 ```jsonc
 {
@@ -129,8 +129,8 @@ Sandbox settings live in `~/.clawdbot/clawdbot.json` under `agents.defaults.sand
         "mode": "all",                    // off, non-main, all
         "scope": "agent",                 // session, agent, shared
         "docker": {
-          "image": "clawdbot-sandbox:bookworm-slim",
-          "containerPrefix": "clawdbot-sbx-"
+          "image": "moltbot-sandbox:bookworm-slim",
+          "containerPrefix": "moltbot-sbx-"
           // ... more Docker options
         },
         "prune": {

docs/cli/security.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot security` (audit and fix common security footguns)"
+summary: "CLI reference for `moltbot security` (audit and fix common security footguns)"
 read_when:
   - You want to run a quick security audit on config/state
   - You want to apply safe “fix” suggestions (chmod, tighten defaults)
 ---
 
-# `clawdbot security`
+# `moltbot security`
 
 Security tools (audit + optional fixes).
 
@@ -15,9 +15,9 @@ Related:
 ## Audit
 
 ```bash
-clawdbot security audit
-clawdbot security audit --deep
-clawdbot security audit --fix
+moltbot security audit
+moltbot security audit --deep
+moltbot security audit --fix
 ```
 
 The audit warns when multiple DM senders share the main session and recommends `session.dmScope="per-channel-peer"` for shared inboxes.

docs/cli/sessions.md

@@ -1,16 +1,16 @@
 ---
-summary: "CLI reference for `clawdbot sessions` (list stored sessions + usage)"
+summary: "CLI reference for `moltbot sessions` (list stored sessions + usage)"
 read_when:
   - You want to list stored sessions and see recent activity
 ---
 
-# `clawdbot sessions`
+# `moltbot sessions`
 
 List stored conversation sessions.
 
 ```bash
-clawdbot sessions
-clawdbot sessions --active 120
-clawdbot sessions --json
+moltbot sessions
+moltbot sessions --active 120
+moltbot sessions --json
 ```
 

docs/cli/setup.md

@@ -1,13 +1,13 @@
 ---
-summary: "CLI reference for `clawdbot setup` (initialize config + workspace)"
+summary: "CLI reference for `moltbot setup` (initialize config + workspace)"
 read_when:
   - You’re doing first-run setup without the full onboarding wizard
   - You want to set the default workspace path
 ---
 
-# `clawdbot setup`
+# `moltbot setup`
 
-Initialize `~/.clawdbot/clawdbot.json` and the agent workspace.
+Initialize `~/.clawdbot/moltbot.json` and the agent workspace.
 
 Related:
 - Getting started: [Getting started](/start/getting-started)
@@ -16,13 +16,13 @@ Related:
 ## Examples
 
 ```bash
-clawdbot setup
-clawdbot setup --workspace ~/clawd
+moltbot setup
+moltbot setup --workspace ~/clawd
 ```
 
 To run the wizard via setup:
 
 ```bash
-clawdbot setup --wizard
+moltbot setup --wizard
 ```
 

docs/cli/skills.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot skills` (list/info/check) and skill eligibility"
+summary: "CLI reference for `moltbot skills` (list/info/check) and skill eligibility"
 read_when:
   - You want to see which skills are available and ready to run
   - You want to debug missing binaries/env/config for skills
 ---
 
-# `clawdbot skills`
+# `moltbot skills`
 
 Inspect skills (bundled + workspace + managed overrides) and see what’s eligible vs missing requirements.
 
@@ -17,9 +17,9 @@ Related:
 ## Commands
 
 ```bash
-clawdbot skills list
-clawdbot skills list --eligible
-clawdbot skills info <name>
-clawdbot skills check
+moltbot skills list
+moltbot skills list --eligible
+moltbot skills info <name>
+moltbot skills check
 ```
 

docs/cli/status.md

@@ -1,19 +1,19 @@
 ---
-summary: "CLI reference for `clawdbot status` (diagnostics, probes, usage snapshots)"
+summary: "CLI reference for `moltbot status` (diagnostics, probes, usage snapshots)"
 read_when:
   - You want a quick diagnosis of channel health + recent session recipients
   - You want a pasteable “all” status for debugging
 ---
 
-# `clawdbot status`
+# `moltbot status`
 
 Diagnostics for channels + sessions.
 
 ```bash
-clawdbot status
-clawdbot status --all
-clawdbot status --deep
-clawdbot status --usage
+moltbot status
+moltbot status --all
+moltbot status --deep
+moltbot status --usage
 ```
 
 Notes:
@@ -21,4 +21,4 @@ Notes:
 - Output includes per-agent session stores when multiple agents are configured.
 - Overview includes Gateway + node host service install/runtime status when available.
 - Overview includes update channel + git SHA (for source checkouts).
-- Update info surfaces in the Overview; if an update is available, status prints a hint to run `clawdbot update` (see [Updating](/install/updating)).
+- Update info surfaces in the Overview; if an update is available, status prints a hint to run `moltbot update` (see [Updating](/install/updating)).

docs/cli/system.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `clawdbot system` (system events, heartbeat, presence)"
+summary: "CLI reference for `moltbot system` (system events, heartbeat, presence)"
 read_when:
   - You want to enqueue a system event without creating a cron job
   - You need to enable or disable heartbeats
   - You want to inspect system presence entries
 ---
 
-# `clawdbot system`
+# `moltbot system`
 
 System-level helpers for the Gateway: enqueue system events, control heartbeats,
 and view presence.
@@ -14,10 +14,10 @@ and view presence.
 ## Common commands
 
 ```bash
-clawdbot system event --text "Check for urgent follow-ups" --mode now
-clawdbot system heartbeat enable
-clawdbot system heartbeat last
-clawdbot system presence
+moltbot system event --text "Check for urgent follow-ups" --mode now
+moltbot system heartbeat enable
+moltbot system heartbeat last
+moltbot system presence
 ```
 
 ## `system event`

docs/cli/tui.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot tui` (terminal UI connected to the Gateway)"
+summary: "CLI reference for `moltbot tui` (terminal UI connected to the Gateway)"
 read_when:
   - You want a terminal UI for the Gateway (remote-friendly)
   - You want to pass url/token/session from scripts
 ---
 
-# `clawdbot tui`
+# `moltbot tui`
 
 Open the terminal UI connected to the Gateway.
 
@@ -15,8 +15,8 @@ Related:
 ## Examples
 
 ```bash
-clawdbot tui
-clawdbot tui --url ws://127.0.0.1:18789 --token <token>
-clawdbot tui --session main --deliver
+moltbot tui
+moltbot tui --url ws://127.0.0.1:18789 --token <token>
+moltbot tui --session main --deliver
 ```
 

docs/cli/uninstall.md

@@ -1,17 +1,17 @@
 ---
-summary: "CLI reference for `clawdbot uninstall` (remove gateway service + local data)"
+summary: "CLI reference for `moltbot uninstall` (remove gateway service + local data)"
 read_when:
   - You want to remove the gateway service and/or local state
   - You want a dry-run first
 ---
 
-# `clawdbot uninstall`
+# `moltbot uninstall`
 
 Uninstall the gateway service + local data (CLI remains).
 
 ```bash
-clawdbot uninstall
-clawdbot uninstall --all --yes
-clawdbot uninstall --dry-run
+moltbot uninstall
+moltbot uninstall --all --yes
+moltbot uninstall --dry-run
 ```
 

docs/cli/update.md

@@ -1,28 +1,28 @@
 ---
-summary: "CLI reference for `clawdbot update` (safe-ish source update + gateway auto-restart)"
+summary: "CLI reference for `moltbot update` (safe-ish source update + gateway auto-restart)"
 read_when:
   - You want to update a source checkout safely
   - You need to understand `--update` shorthand behavior
 ---
 
-# `clawdbot update`
+# `moltbot update`
 
-Safely update Clawdbot and switch between stable/beta/dev channels.
+Safely update Moltbot and switch between stable/beta/dev channels.
 
 If you installed via **npm/pnpm** (global install, no git metadata), updates happen via the package manager flow in [Updating](/install/updating).
 
 ## Usage
 
 ```bash
-clawdbot update
-clawdbot update status
-clawdbot update wizard
-clawdbot update --channel beta
-clawdbot update --channel dev
-clawdbot update --tag beta
-clawdbot update --no-restart
-clawdbot update --json
-clawdbot --update
+moltbot update
+moltbot update status
+moltbot update wizard
+moltbot update --channel beta
+moltbot update --channel dev
+moltbot update --tag beta
+moltbot update --no-restart
+moltbot update --json
+moltbot --update
 ```
 
 ## Options
@@ -40,9 +40,9 @@ Note: downgrades require confirmation because older versions can break configura
 Show the active update channel + git tag/branch/SHA (for source checkouts), plus update availability.
 
 ```bash
-clawdbot update status
-clawdbot update status --json
-clawdbot update status --timeout 10
+moltbot update status
+moltbot update status --json
+moltbot update status --timeout 10
 ```
 
 Options:
@@ -57,10 +57,10 @@ offers to create one.
 
 ## What it does
 
-When you switch channels explicitly (`--channel ...`), Clawdbot also keeps the
+When you switch channels explicitly (`--channel ...`), Moltbot also keeps the
 install method aligned:
 
-- `dev` → ensures a git checkout (default: `~/clawdbot`, override with `CLAWDBOT_GIT_DIR`),
+- `dev` → ensures a git checkout (default: `~/moltbot`, override with `CLAWDBOT_GIT_DIR`),
   updates it, and installs the global CLI from that checkout.
 - `stable`/`beta` → installs from npm using the matching dist-tag.
 
@@ -81,16 +81,16 @@ High-level:
 5. Rebases onto the selected commit (dev only).
 6. Installs deps (pnpm preferred; npm fallback).
 7. Builds + builds the Control UI.
-8. Runs `clawdbot doctor` as the final “safe update” check.
+8. Runs `moltbot doctor` as the final “safe update” check.
 9. Syncs plugins to the active channel (dev uses bundled extensions; stable/beta uses npm) and updates npm-installed plugins.
 
 ## `--update` shorthand
 
-`clawdbot --update` rewrites to `clawdbot update` (useful for shells and launcher scripts).
+`moltbot --update` rewrites to `moltbot update` (useful for shells and launcher scripts).
 
 ## See also
 
-- `clawdbot doctor` (offers to run update first on git checkouts)
+- `moltbot doctor` (offers to run update first on git checkouts)
 - [Development channels](/install/development-channels)
 - [Updating](/install/updating)
 - [CLI reference](/cli)

docs/cli/voicecall.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot voicecall` (voice-call plugin command surface)"
+summary: "CLI reference for `moltbot voicecall` (voice-call plugin command surface)"
 read_when:
   - You use the voice-call plugin and want the CLI entry points
   - You want quick examples for `voicecall call|continue|status|tail|expose`
 ---
 
-# `clawdbot voicecall`
+# `moltbot voicecall`
 
 `voicecall` is a plugin-provided command. It only appears if the voice-call plugin is installed and enabled.
 
@@ -15,18 +15,18 @@ Primary doc:
 ## Common commands
 
 ```bash
-clawdbot voicecall status --call-id <id>
-clawdbot voicecall call --to "+15555550123" --message "Hello" --mode notify
-clawdbot voicecall continue --call-id <id> --message "Any questions?"
-clawdbot voicecall end --call-id <id>
+moltbot voicecall status --call-id <id>
+moltbot voicecall call --to "+15555550123" --message "Hello" --mode notify
+moltbot voicecall continue --call-id <id> --message "Any questions?"
+moltbot voicecall end --call-id <id>
 ```
 
 ## Exposing webhooks (Tailscale)
 
 ```bash
-clawdbot voicecall expose --mode serve
-clawdbot voicecall expose --mode funnel
-clawdbot voicecall unexpose
+moltbot voicecall expose --mode serve
+moltbot voicecall expose --mode funnel
+moltbot voicecall unexpose
 ```
 
 Security note: only expose the webhook endpoint to networks you trust. Prefer Tailscale Serve over Funnel when possible.

docs/cli/webhooks.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `clawdbot webhooks` (webhook helpers + Gmail Pub/Sub)"
+summary: "CLI reference for `moltbot webhooks` (webhook helpers + Gmail Pub/Sub)"
 read_when:
-  - You want to wire Gmail Pub/Sub events into Clawdbot
+  - You want to wire Gmail Pub/Sub events into Moltbot
   - You want webhook helper commands
 ---
 
-# `clawdbot webhooks`
+# `moltbot webhooks`
 
 Webhook helpers and integrations (Gmail Pub/Sub, webhook helpers).
 
@@ -16,8 +16,8 @@ Related:
 ## Gmail
 
 ```bash
-clawdbot webhooks gmail setup --account you@example.com
-clawdbot webhooks gmail run
+moltbot webhooks gmail setup --account you@example.com
+moltbot webhooks gmail run
 ```
 
 See [Gmail Pub/Sub documentation](/automation/gmail-pubsub) for details.