@poolzin/pool-bot 1.28.0 → 2026.1.26

package/docs/logging.md

@@ -8,7 +8,7 @@ read_when:
 
 # Logging
 
-Pool Bot logs in two places:
+Clawdbot logs in two places:
 
 - **File logs** (JSON lines) written by the Gateway.
 - **Console output** shown in terminals and the Control UI.
@@ -20,16 +20,16 @@ levels and formats.
 
 By default, the Gateway writes a rolling log file under:
 
-`/tmp/moltbot/moltbot-YYYY-MM-DD.log`
+`/tmp/clawdbot/clawdbot-YYYY-MM-DD.log`
 
 The date uses the gateway host's local timezone.
 
-You can override this in `~/.clawdbot/moltbot.json`:
+You can override this in `~/.clawdbot/clawdbot.json`:
 
 ```json
 {
   "logging": {
-    "file": "/path/to/moltbot.log"
+    "file": "/path/to/clawdbot.log"
   }
 }
 ```
@@ -41,7 +41,7 @@ You can override this in `~/.clawdbot/moltbot.json`:
 Use the CLI to tail the gateway log file via RPC:
 
 ```bash
-moltbot logs --follow
+clawdbot logs --follow
 ```
 
 Output modes:
@@ -62,7 +62,7 @@ In JSON mode, the CLI emits `type`-tagged objects:
 If the Gateway is unreachable, the CLI prints a short hint to run:
 
 ```bash
-moltbot doctor
+clawdbot doctor
 ```
 
 ### Control UI (web)
@@ -75,7 +75,7 @@ See [/web/control-ui](/web/control-ui) for how to open it.
 To filter channel activity (WhatsApp/Telegram/etc), use:
 
 ```bash
-moltbot channels logs --channel whatsapp
+clawdbot channels logs --channel whatsapp
 ```
 
 ## Log formats
@@ -97,13 +97,13 @@ Console formatting is controlled by `logging.consoleStyle`.
 
 ## Configuring logging
 
-All logging configuration lives under `logging` in `~/.clawdbot/moltbot.json`.
+All logging configuration lives under `logging` in `~/.clawdbot/clawdbot.json`.
 
 ```json
 {
   "logging": {
     "level": "info",
-    "file": "/tmp/moltbot/moltbot-YYYY-MM-DD.log",
+    "file": "/tmp/clawdbot/clawdbot-YYYY-MM-DD.log",
     "consoleLevel": "info",
     "consoleStyle": "pretty",
     "redactSensitive": "tools",
@@ -151,7 +151,7 @@ diagnostics + the exporter plugin are enabled.
 
 - **OpenTelemetry (OTel)**: the data model + SDKs for traces, metrics, and logs.
 - **OTLP**: the wire protocol used to export OTel data to a collector/backend.
-- Pool Bot exports via **OTLP/HTTP (protobuf)** today.
+- Clawdbot exports via **OTLP/HTTP (protobuf)** today.
 
 ### Signals exported
 
@@ -237,7 +237,7 @@ works with any OpenTelemetry collector/backend that accepts OTLP/HTTP.
       "enabled": true,
       "endpoint": "http://otel-collector:4318",
       "protocol": "http/protobuf",
-      "serviceName": "moltbot-gateway",
+      "serviceName": "clawdbot-gateway",
       "traces": true,
       "metrics": true,
       "logs": true,
@@ -249,7 +249,7 @@ works with any OpenTelemetry collector/backend that accepts OTLP/HTTP.
 ```
 
 Notes:
-- You can also enable the plugin with `moltbot plugins enable diagnostics-otel`.
+- You can also enable the plugin with `clawdbot plugins enable diagnostics-otel`.
 - `protocol` currently supports `http/protobuf` only. `grpc` is ignored.
 - Metrics include token usage, cost, context size, run duration, and message-flow
   counters/histograms (webhooks, queueing, session state, queue depth/wait).
@@ -262,58 +262,58 @@ Notes:
 ### Exported metrics (names + types)
 
 Model usage:
-- `moltbot.tokens` (counter, attrs: `moltbot.token`, `moltbot.channel`,
-  `moltbot.provider`, `moltbot.model`)
-- `moltbot.cost.usd` (counter, attrs: `moltbot.channel`, `moltbot.provider`,
-  `moltbot.model`)
-- `moltbot.run.duration_ms` (histogram, attrs: `moltbot.channel`,
-  `moltbot.provider`, `moltbot.model`)
-- `moltbot.context.tokens` (histogram, attrs: `moltbot.context`,
-  `moltbot.channel`, `moltbot.provider`, `moltbot.model`)
+- `clawdbot.tokens` (counter, attrs: `clawdbot.token`, `clawdbot.channel`,
+  `clawdbot.provider`, `clawdbot.model`)
+- `clawdbot.cost.usd` (counter, attrs: `clawdbot.channel`, `clawdbot.provider`,
+  `clawdbot.model`)
+- `clawdbot.run.duration_ms` (histogram, attrs: `clawdbot.channel`,
+  `clawdbot.provider`, `clawdbot.model`)
+- `clawdbot.context.tokens` (histogram, attrs: `clawdbot.context`,
+  `clawdbot.channel`, `clawdbot.provider`, `clawdbot.model`)
 
 Message flow:
-- `moltbot.webhook.received` (counter, attrs: `moltbot.channel`,
-  `moltbot.webhook`)
-- `moltbot.webhook.error` (counter, attrs: `moltbot.channel`,
-  `moltbot.webhook`)
-- `moltbot.webhook.duration_ms` (histogram, attrs: `moltbot.channel`,
-  `moltbot.webhook`)
-- `moltbot.message.queued` (counter, attrs: `moltbot.channel`,
-  `moltbot.source`)
-- `moltbot.message.processed` (counter, attrs: `moltbot.channel`,
-  `moltbot.outcome`)
-- `moltbot.message.duration_ms` (histogram, attrs: `moltbot.channel`,
-  `moltbot.outcome`)
+- `clawdbot.webhook.received` (counter, attrs: `clawdbot.channel`,
+  `clawdbot.webhook`)
+- `clawdbot.webhook.error` (counter, attrs: `clawdbot.channel`,
+  `clawdbot.webhook`)
+- `clawdbot.webhook.duration_ms` (histogram, attrs: `clawdbot.channel`,
+  `clawdbot.webhook`)
+- `clawdbot.message.queued` (counter, attrs: `clawdbot.channel`,
+  `clawdbot.source`)
+- `clawdbot.message.processed` (counter, attrs: `clawdbot.channel`,
+  `clawdbot.outcome`)
+- `clawdbot.message.duration_ms` (histogram, attrs: `clawdbot.channel`,
+  `clawdbot.outcome`)
 
 Queues + sessions:
-- `moltbot.queue.lane.enqueue` (counter, attrs: `moltbot.lane`)
-- `moltbot.queue.lane.dequeue` (counter, attrs: `moltbot.lane`)
-- `moltbot.queue.depth` (histogram, attrs: `moltbot.lane` or
-  `moltbot.channel=heartbeat`)
-- `moltbot.queue.wait_ms` (histogram, attrs: `moltbot.lane`)
-- `moltbot.session.state` (counter, attrs: `moltbot.state`, `moltbot.reason`)
-- `moltbot.session.stuck` (counter, attrs: `moltbot.state`)
-- `moltbot.session.stuck_age_ms` (histogram, attrs: `moltbot.state`)
-- `moltbot.run.attempt` (counter, attrs: `moltbot.attempt`)
+- `clawdbot.queue.lane.enqueue` (counter, attrs: `clawdbot.lane`)
+- `clawdbot.queue.lane.dequeue` (counter, attrs: `clawdbot.lane`)
+- `clawdbot.queue.depth` (histogram, attrs: `clawdbot.lane` or
+  `clawdbot.channel=heartbeat`)
+- `clawdbot.queue.wait_ms` (histogram, attrs: `clawdbot.lane`)
+- `clawdbot.session.state` (counter, attrs: `clawdbot.state`, `clawdbot.reason`)
+- `clawdbot.session.stuck` (counter, attrs: `clawdbot.state`)
+- `clawdbot.session.stuck_age_ms` (histogram, attrs: `clawdbot.state`)
+- `clawdbot.run.attempt` (counter, attrs: `clawdbot.attempt`)
 
 ### Exported spans (names + key attributes)
 
-- `moltbot.model.usage`
-  - `moltbot.channel`, `moltbot.provider`, `moltbot.model`
-  - `moltbot.sessionKey`, `moltbot.sessionId`
-  - `moltbot.tokens.*` (input/output/cache_read/cache_write/total)
-- `moltbot.webhook.processed`
-  - `moltbot.channel`, `moltbot.webhook`, `moltbot.chatId`
-- `moltbot.webhook.error`
-  - `moltbot.channel`, `moltbot.webhook`, `moltbot.chatId`,
-    `moltbot.error`
-- `moltbot.message.processed`
-  - `moltbot.channel`, `moltbot.outcome`, `moltbot.chatId`,
-    `moltbot.messageId`, `moltbot.sessionKey`, `moltbot.sessionId`,
-    `moltbot.reason`
-- `moltbot.session.stuck`
-  - `moltbot.state`, `moltbot.ageMs`, `moltbot.queueDepth`,
-    `moltbot.sessionKey`, `moltbot.sessionId`
+- `clawdbot.model.usage`
+  - `clawdbot.channel`, `clawdbot.provider`, `clawdbot.model`
+  - `clawdbot.sessionKey`, `clawdbot.sessionId`
+  - `clawdbot.tokens.*` (input/output/cache_read/cache_write/total)
+- `clawdbot.webhook.processed`
+  - `clawdbot.channel`, `clawdbot.webhook`, `clawdbot.chatId`
+- `clawdbot.webhook.error`
+  - `clawdbot.channel`, `clawdbot.webhook`, `clawdbot.chatId`,
+    `clawdbot.error`
+- `clawdbot.message.processed`
+  - `clawdbot.channel`, `clawdbot.outcome`, `clawdbot.chatId`,
+    `clawdbot.messageId`, `clawdbot.sessionKey`, `clawdbot.sessionId`,
+    `clawdbot.reason`
+- `clawdbot.session.stuck`
+  - `clawdbot.state`, `clawdbot.ageMs`, `clawdbot.queueDepth`,
+    `clawdbot.sessionKey`, `clawdbot.sessionId`
 
 ### Sampling + flushing
 
@@ -337,7 +337,7 @@ Queues + sessions:
 
 ## Troubleshooting tips
 
-- **Gateway not reachable?** Run `moltbot doctor` first.
+- **Gateway not reachable?** Run `clawdbot doctor` first.
 - **Logs empty?** Check that the Gateway is running and writing to the file path
   in `logging.file`.
 - **Need more detail?** Set `logging.level` to `debug` or `trace` and retry.

package/docs/multi-agent-sandbox-tools.md

@@ -31,7 +31,7 @@ Credentials are **not** shared between agents. Never reuse `agentDir` across age
 If you want to share creds, copy `auth-profiles.json` into the other agent's `agentDir`.
 
 For how sandboxing behaves at runtime, see [Sandboxing](/gateway/sandboxing).
-For debugging “why is this blocked?”, see [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) and `moltbot sandbox explain`.
+For debugging “why is this blocked?”, see [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) and `clawdbot sandbox explain`.
 
 ---
 
@@ -225,7 +225,7 @@ Tool policies (global, agent, sandbox) support `group:*` entries that expand to
 - `group:automation`: `cron`, `gateway`
 - `group:messaging`: `message`
 - `group:nodes`: `nodes`
-- `group:moltbot`: all built-in Pool Bot tools (excludes provider plugins)
+- `group:clawdbot`: all built-in Clawdbot tools (excludes provider plugins)
 
 ### Elevated Mode
 `tools.elevated` is the global baseline (sender-based allowlist). `agents.list[].tools.elevated` can further restrict elevated for specific agents (both must allow).
@@ -278,7 +278,7 @@ Mitigation patterns:
 }
 ```
 
-Legacy `agent.*` configs are migrated by `moltbot doctor`; prefer `agents.defaults` + `agents.list` going forward.
+Legacy `agent.*` configs are migrated by `clawdbot doctor`; prefer `agents.defaults` + `agents.list` going forward.
 
 ---
 
@@ -331,12 +331,12 @@ After configuring multi-agent sandbox and tools:
 
 1. **Check agent resolution:**
    ```exec
-   moltbot agents list --bindings
+   clawdbot agents list --bindings
    ```
 
 2. **Verify sandbox containers:**
    ```exec
-   docker ps --filter "label=moltbot.sandbox=1"
+   docker ps --filter "label=clawdbot.sandbox=1"
    ```
 
 3. **Test tool restrictions:**

package/docs/network.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Network hub
 
-This hub links the core docs for how Pool Bot connects, pairs, and secures
+This hub links the core docs for how Clawdbot connects, pairs, and secures
 devices across localhost, LAN, and tailnet.
 
 ## Core model

package/docs/nodes/audio.md

@@ -6,7 +6,7 @@ read_when:
 # Audio / Voice Notes — 2026-01-17
 
 ## What works
-- **Media understanding (audio)**: If audio understanding is enabled (or auto‑detected), Pool Bot:
+- **Media understanding (audio)**: If audio understanding is enabled (or auto‑detected), Clawdbot:
   1) Locates the first audio attachment (local path or URL) and downloads it if needed.
   2) Enforces `maxBytes` before sending to each model entry.
   3) Runs the first eligible model entry in order (provider or CLI).
@@ -17,7 +17,7 @@ read_when:
 
 ## Auto-detection (default)
 If you **don’t configure models** and `tools.media.audio.enabled` is **not** set to `false`,
-Pool Bot auto-detects in this order and stops at the first working option:
+Clawdbot auto-detects in this order and stops at the first working option:
 
 1) **Local CLIs** (if installed)
    - `sherpa-onnx-offline` (requires `SHERPA_ONNX_MODEL_DIR` with encoder/decoder/joiner/tokens)

package/docs/nodes/camera.md

@@ -7,7 +7,7 @@ read_when:
 
 # Camera capture (agent)
 
-Pool Bot supports **camera capture** for agent workflows:
+Clawdbot supports **camera capture** for agent workflows:
 
 - **iOS node** (paired via Gateway): capture a **photo** (`jpg`) or **short video clip** (`mp4`, with optional audio) via `node.invoke`.
 - **Android node** (paired via Gateway): capture a **photo** (`jpg`) or **short video clip** (`mp4`, with optional audio) via `node.invoke`.
@@ -67,10 +67,10 @@ The easiest way to get attachments is via the CLI helper, which writes decoded m
 Examples:
 
 ```bash
-moltbot nodes camera snap --node <id>               # default: both front + back (2 MEDIA lines)
-moltbot nodes camera snap --node <id> --facing front
-moltbot nodes camera clip --node <id> --duration 3000
-moltbot nodes camera clip --node <id> --no-audio
+clawdbot nodes camera snap --node <id>               # default: both front + back (2 MEDIA lines)
+clawdbot nodes camera snap --node <id> --facing front
+clawdbot nodes camera clip --node <id> --duration 3000
+clawdbot nodes camera clip --node <id> --no-audio
 ```
 
 Notes:
@@ -108,30 +108,30 @@ Photos are recompressed to keep the base64 payload under 5 MB.
 
 The macOS companion app exposes a checkbox:
 
-- **Settings → General → Allow Camera** (`moltbot.cameraEnabled`)
+- **Settings → General → Allow Camera** (`clawdbot.cameraEnabled`)
   - Default: **off**
   - When off: camera requests return “Camera disabled by user”.
 
 ### CLI helper (node invoke)
 
-Use the main `moltbot` CLI to invoke camera commands on the macOS node.
+Use the main `clawdbot` CLI to invoke camera commands on the macOS node.
 
 Examples:
 
 ```bash
-moltbot nodes camera list --node <id>            # list camera ids
-moltbot nodes camera snap --node <id>            # prints MEDIA:<path>
-moltbot nodes camera snap --node <id> --max-width 1280
-moltbot nodes camera snap --node <id> --delay-ms 2000
-moltbot nodes camera snap --node <id> --device-id <id>
-moltbot nodes camera clip --node <id> --duration 10s          # prints MEDIA:<path>
-moltbot nodes camera clip --node <id> --duration-ms 3000      # prints MEDIA:<path> (legacy flag)
-moltbot nodes camera clip --node <id> --device-id <id>
-moltbot nodes camera clip --node <id> --no-audio
+clawdbot nodes camera list --node <id>            # list camera ids
+clawdbot nodes camera snap --node <id>            # prints MEDIA:<path>
+clawdbot nodes camera snap --node <id> --max-width 1280
+clawdbot nodes camera snap --node <id> --delay-ms 2000
+clawdbot nodes camera snap --node <id> --device-id <id>
+clawdbot nodes camera clip --node <id> --duration 10s          # prints MEDIA:<path>
+clawdbot nodes camera clip --node <id> --duration-ms 3000      # prints MEDIA:<path> (legacy flag)
+clawdbot nodes camera clip --node <id> --device-id <id>
+clawdbot nodes camera clip --node <id> --no-audio
 ```
 
 Notes:
-- `moltbot nodes camera snap` defaults to `maxWidth=1600` unless overridden.
+- `clawdbot nodes camera snap` defaults to `maxWidth=1600` unless overridden.
 - On macOS, `camera.snap` waits `delayMs` (default 2000ms) after warm-up/exposure settle before capturing.
 - Photo payloads are recompressed to keep base64 under 5 MB.
 
@@ -145,7 +145,7 @@ Notes:
 For *screen* video (not camera), use the macOS companion:
 
 ```bash
-moltbot nodes screen record --node <id> --duration 10s --fps 15   # prints MEDIA:<path>
+clawdbot nodes screen record --node <id> --duration 10s --fps 15   # prints MEDIA:<path>
 ```
 
 Notes:

package/docs/nodes/images.md

@@ -8,12 +8,12 @@ read_when:
 The WhatsApp channel runs via **Baileys Web**. This document captures the current media handling rules for send, gateway, and agent replies.
 
 ## Goals
-- Send media with optional captions via `moltbot message send --media`.
+- Send media with optional captions via `clawdbot message send --media`.
 - Allow auto-replies from the web inbox to include media alongside text.
 - Keep per-type limits sane and predictable.
 
 ## CLI Surface
-- `moltbot message send --media <path-or-url> [--message <caption>]`
+- `clawdbot message send --media <path-or-url> [--message <caption>]`
   - `--media` optional; caption can be empty for media-only sends.
   - `--dry-run` prints the resolved payload; `--json` emits `{ channel, to, messageId, mediaUrl, caption }`.
 
@@ -30,11 +30,11 @@ The WhatsApp channel runs via **Baileys Web**. This document captures the curren
 
 ## Auto-Reply Pipeline
 - `getReplyFromConfig` returns `{ text?, mediaUrl?, mediaUrls? }`.
-- When media is present, the web sender resolves local paths or URLs using the same pipeline as `moltbot message send`.
+- When media is present, the web sender resolves local paths or URLs using the same pipeline as `clawdbot message send`.
 - Multiple media entries are sent sequentially if provided.
 
 ## Inbound Media to Commands (Pi)
-- When inbound web messages include media, Pool Bot downloads to a temp file and exposes templating variables:
+- When inbound web messages include media, Clawdbot downloads to a temp file and exposes templating variables:
   - `{{MediaUrl}}` pseudo-URL for the inbound media.
   - `{{MediaPath}}` local temp path written before running the command.
 - When a per-session Docker sandbox is enabled, inbound media is copied into the sandbox workspace and `MediaPath`/`MediaUrl` are rewritten to a relative path like `media/inbound/<filename>`.

package/docs/nodes/index.md

@@ -12,7 +12,7 @@ A **node** is a companion device (macOS/iOS/Android/headless) that connects to t
 
 Legacy transport: [Bridge protocol](/gateway/bridge-protocol) (TCP JSONL; deprecated/removed for current nodes).
 
-macOS can also run in **node mode**: the menubar app connects to the Gateway’s WS server and exposes its local canvas/camera commands as a node (so `moltbot nodes …` works against this Mac).
+macOS can also run in **node mode**: the menubar app connects to the Gateway’s WS server and exposes its local canvas/camera commands as a node (so `clawdbot nodes …` works against this Mac).
 
 Notes:
 - Nodes are **peripherals**, not gateways. They don’t run the gateway service.
@@ -26,16 +26,16 @@ creates a device pairing request for `role: node`. Approve via the devices CLI (
 Quick CLI:
 
 ```bash
-moltbot devices list
-moltbot devices approve <requestId>
-moltbot devices reject <requestId>
-moltbot nodes status
-moltbot nodes describe --node <idOrNameOrIp>
+clawdbot devices list
+clawdbot devices approve <requestId>
+clawdbot devices reject <requestId>
+clawdbot nodes status
+clawdbot nodes describe --node <idOrNameOrIp>
 ```
 
 Notes:
 - `nodes status` marks a node as **paired** when its device pairing role includes `node`.
-- `node.pair.*` (CLI: `moltbot nodes pending/approve/reject`) is a separate gateway-owned
+- `node.pair.*` (CLI: `clawdbot nodes pending/approve/reject`) is a separate gateway-owned
   node pairing store; it does **not** gate the WS `connect` handshake.
 
 ## Remote node host (system.run)
@@ -54,14 +54,14 @@ forwards `exec` calls to the **node host** when `host=node` is selected.
 On the node machine:
 
 ```bash
-moltbot node run --host <gateway-host> --port 18789 --display-name "Build Node"
+clawdbot node run --host <gateway-host> --port 18789 --display-name "Build Node"
 ```
 
 ### Start a node host (service)
 
 ```bash
-moltbot node install --host <gateway-host> --port 18789 --display-name "Build Node"
-moltbot node restart
+clawdbot node install --host <gateway-host> --port 18789 --display-name "Build Node"
+clawdbot node restart
 ```
 
 ### Pair + name
@@ -69,22 +69,22 @@ moltbot node restart
 On the gateway host:
 
 ```bash
-moltbot nodes pending
-moltbot nodes approve <requestId>
-moltbot nodes list
+clawdbot nodes pending
+clawdbot nodes approve <requestId>
+clawdbot nodes list
 ```
 
 Naming options:
-- `--display-name` on `moltbot node run` / `moltbot node install` (persists in `~/.clawdbot/node.json` on the node).
-- `moltbot nodes rename --node <id|name|ip> --name "Build Node"` (gateway override).
+- `--display-name` on `clawdbot node run` / `clawdbot node install` (persists in `~/.clawdbot/node.json` on the node).
+- `clawdbot nodes rename --node <id|name|ip> --name "Build Node"` (gateway override).
 
 ### Allowlist the commands
 
 Exec approvals are **per node host**. Add allowlist entries from the gateway:
 
 ```bash
-moltbot approvals allowlist add --node <id|name|ip> "/usr/bin/uname"
-moltbot approvals allowlist add --node <id|name|ip> "/usr/bin/sw_vers"
+clawdbot approvals allowlist add --node <id|name|ip> "/usr/bin/uname"
+clawdbot approvals allowlist add --node <id|name|ip> "/usr/bin/sw_vers"
 ```
 
 Approvals live on the node host at `~/.clawdbot/exec-approvals.json`.
@@ -94,9 +94,9 @@ Approvals live on the node host at `~/.clawdbot/exec-approvals.json`.
 Configure defaults (gateway config):
 
 ```bash
-moltbot config set tools.exec.host node
-moltbot config set tools.exec.security allowlist
-moltbot config set tools.exec.node "<id-or-name>"
+clawdbot config set tools.exec.host node
+clawdbot config set tools.exec.security allowlist
+clawdbot config set tools.exec.node "<id-or-name>"
 ```
 
 Or per session:
@@ -118,7 +118,7 @@ Related:
 Low-level (raw RPC):
 
 ```bash
-moltbot nodes invoke --node <idOrNameOrIp> --command canvas.eval --params '{"javaScript":"location.href"}'
+clawdbot nodes invoke --node <idOrNameOrIp> --command canvas.eval --params '{"javaScript":"location.href"}'
 ```
 
 Higher-level helpers exist for the common “give the agent a MEDIA attachment” workflows.
@@ -130,17 +130,17 @@ If the node is showing the Canvas (WebView), `canvas.snapshot` returns `{ format
 CLI helper (writes to a temp file and prints `MEDIA:<path>`):
 
 ```bash
-moltbot nodes canvas snapshot --node <idOrNameOrIp> --format png
-moltbot nodes canvas snapshot --node <idOrNameOrIp> --format jpg --max-width 1200 --quality 0.9
+clawdbot nodes canvas snapshot --node <idOrNameOrIp> --format png
+clawdbot nodes canvas snapshot --node <idOrNameOrIp> --format jpg --max-width 1200 --quality 0.9
 ```
 
 ### Canvas controls
 
 ```bash
-moltbot nodes canvas present --node <idOrNameOrIp> --target https://example.com
-moltbot nodes canvas hide --node <idOrNameOrIp>
-moltbot nodes canvas navigate https://example.com --node <idOrNameOrIp>
-moltbot nodes canvas eval --node <idOrNameOrIp> --js "document.title"
+clawdbot nodes canvas present --node <idOrNameOrIp> --target https://example.com
+clawdbot nodes canvas hide --node <idOrNameOrIp>
+clawdbot nodes canvas navigate https://example.com --node <idOrNameOrIp>
+clawdbot nodes canvas eval --node <idOrNameOrIp> --js "document.title"
 ```
 
 Notes:
@@ -150,9 +150,9 @@ Notes:
 ### A2UI (Canvas)
 
 ```bash
-moltbot nodes canvas a2ui push --node <idOrNameOrIp> --text "Hello"
-moltbot nodes canvas a2ui push --node <idOrNameOrIp> --jsonl ./payload.jsonl
-moltbot nodes canvas a2ui reset --node <idOrNameOrIp>
+clawdbot nodes canvas a2ui push --node <idOrNameOrIp> --text "Hello"
+clawdbot nodes canvas a2ui push --node <idOrNameOrIp> --jsonl ./payload.jsonl
+clawdbot nodes canvas a2ui reset --node <idOrNameOrIp>
 ```
 
 Notes:
@@ -163,16 +163,16 @@ Notes:
 Photos (`jpg`):
 
 ```bash
-moltbot nodes camera list --node <idOrNameOrIp>
-moltbot nodes camera snap --node <idOrNameOrIp>            # default: both facings (2 MEDIA lines)
-moltbot nodes camera snap --node <idOrNameOrIp> --facing front
+clawdbot nodes camera list --node <idOrNameOrIp>
+clawdbot nodes camera snap --node <idOrNameOrIp>            # default: both facings (2 MEDIA lines)
+clawdbot nodes camera snap --node <idOrNameOrIp> --facing front
 ```
 
 Video clips (`mp4`):
 
 ```bash
-moltbot nodes camera clip --node <idOrNameOrIp> --duration 10s
-moltbot nodes camera clip --node <idOrNameOrIp> --duration 3000 --no-audio
+clawdbot nodes camera clip --node <idOrNameOrIp> --duration 10s
+clawdbot nodes camera clip --node <idOrNameOrIp> --duration 3000 --no-audio
 ```
 
 Notes:
@@ -185,8 +185,8 @@ Notes:
 Nodes expose `screen.record` (mp4). Example:
 
 ```bash
-moltbot nodes screen record --node <idOrNameOrIp> --duration 10s --fps 10
-moltbot nodes screen record --node <idOrNameOrIp> --duration 10s --fps 10 --no-audio
+clawdbot nodes screen record --node <idOrNameOrIp> --duration 10s --fps 10
+clawdbot nodes screen record --node <idOrNameOrIp> --duration 10s --fps 10 --no-audio
 ```
 
 Notes:
@@ -203,8 +203,8 @@ Nodes expose `location.get` when Location is enabled in settings.
 CLI helper:
 
 ```bash
-moltbot nodes location get --node <idOrNameOrIp>
-moltbot nodes location get --node <idOrNameOrIp> --accuracy precise --max-age 15000 --location-timeout 10000
+clawdbot nodes location get --node <idOrNameOrIp>
+clawdbot nodes location get --node <idOrNameOrIp> --accuracy precise --max-age 15000 --location-timeout 10000
 ```
 
 Notes:
@@ -219,7 +219,7 @@ Android nodes can expose `sms.send` when the user grants **SMS** permission and
 Low-level invoke:
 
 ```bash
-moltbot nodes invoke --node <idOrNameOrIp> --command sms.send --params '{"to":"+15555550123","message":"Hello from Pool Bot"}'
+clawdbot nodes invoke --node <idOrNameOrIp> --command sms.send --params '{"to":"+15555550123","message":"Hello from Clawdbot"}'
 ```
 
 Notes:
@@ -234,8 +234,8 @@ The headless node host exposes `system.run`, `system.which`, and `system.execApp
 Examples:
 
 ```bash
-moltbot nodes run --node <idOrNameOrIp> -- echo "Hello from mac node"
-moltbot nodes notify --node <idOrNameOrIp> --title "Ping" --body "Gateway ready"
+clawdbot nodes run --node <idOrNameOrIp> -- echo "Hello from mac node"
+clawdbot nodes notify --node <idOrNameOrIp> --title "Ping" --body "Gateway ready"
 ```
 
 Notes:
@@ -256,21 +256,21 @@ This sets the default node for `exec host=node` (and can be overridden per agent
 Global default:
 
 ```bash
-moltbot config set tools.exec.node "node-id-or-name"
+clawdbot config set tools.exec.node "node-id-or-name"
 ```
 
 Per-agent override:
 
 ```bash
-moltbot config get agents.list
-moltbot config set agents.list[0].tools.exec.node "node-id-or-name"
+clawdbot config get agents.list
+clawdbot config set agents.list[0].tools.exec.node "node-id-or-name"
 ```
 
 Unset to allow any node:
 
 ```bash
-moltbot config unset tools.exec.node
-moltbot config unset agents.list[0].tools.exec.node
+clawdbot config unset tools.exec.node
+clawdbot config unset agents.list[0].tools.exec.node
 ```
 
 ## Permissions map
@@ -279,14 +279,14 @@ Nodes may include a `permissions` map in `node.list` / `node.describe`, keyed by
 
 ## Headless node host (cross-platform)
 
-Pool Bot can run a **headless node host** (no UI) that connects to the Gateway
+Clawdbot can run a **headless node host** (no UI) that connects to the Gateway
 WebSocket and exposes `system.run` / `system.which`. This is useful on Linux/Windows
 or for running a minimal node alongside a server.
 
 Start it:
 
 ```bash
-moltbot node run --host <gateway-host> --port 18789
+clawdbot node run --host <gateway-host> --port 18789
 ```
 
 Notes:
@@ -301,5 +301,5 @@ Notes:
 
 ## Mac node mode
 
-- The macOS menubar app connects to the Gateway WS server as a node (so `moltbot nodes …` works against this Mac).
+- The macOS menubar app connects to the Gateway WS server as a node (so `clawdbot nodes …` works against this Mac).
 - In remote mode, the app opens an SSH tunnel for the Gateway port and connects to `localhost`.

package/docs/nodes/location-command.md

@@ -85,11 +85,11 @@ Notes:
 
 ## Model/tooling integration
 - Tool surface: `nodes` tool adds `location_get` action (node required).
-- CLI: `moltbot nodes location get --node <id>`.
+- CLI: `clawdbot nodes location get --node <id>`.
 - Agent guidelines: only call when user enabled location and understands the scope.
 
 ## UX copy (suggested)
 - Off: “Location sharing is disabled.”
-- While Using: “Only when Pool Bot is open.”
+- While Using: “Only when Clawdbot is open.”
 - Always: “Allow background location. Requires system permission.”
 - Precise: “Use precise GPS location. Toggle off to share approximate location.”