@gguf/pigbot 0.0.1 → 0.0.2

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 `pigbot message send --media`.
+- Send media with optional captions via `moltbot message send --media`.
 - Allow auto-replies from the web inbox to include media alongside text.
 - Keep per-type limits sane and predictable.
 
 ## CLI Surface
-- `pigbot message send --media <path-or-url> [--message <caption>]`
+- `moltbot 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 `pigbot message send`.
+- When media is present, the web sender resolves local paths or URLs using the same pipeline as `moltbot message send`.
 - Multiple media entries are sent sequentially if provided.
 
 ## Inbound Media to Commands (Pi)
-- When inbound web messages include media, Pigbot downloads to a temp file and exposes templating variables:
+- When inbound web messages include media, Moltbot 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 `pigbot 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 `moltbot 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
-pigbot devices list
-pigbot devices approve <requestId>
-pigbot devices reject <requestId>
-pigbot nodes status
-pigbot nodes describe --node <idOrNameOrIp>
+moltbot devices list
+moltbot devices approve <requestId>
+moltbot devices reject <requestId>
+moltbot nodes status
+moltbot nodes describe --node <idOrNameOrIp>
 ```
 
 Notes:
 - `nodes status` marks a node as **paired** when its device pairing role includes `node`.
-- `node.pair.*` (CLI: `pigbot nodes pending/approve/reject`) is a separate gateway-owned
+- `node.pair.*` (CLI: `moltbot 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)
@@ -47,21 +47,21 @@ forwards `exec` calls to the **node host** when `host=node` is selected.
 ### What runs where
 - **Gateway host**: receives messages, runs the model, routes tool calls.
 - **Node host**: executes `system.run`/`system.which` on the node machine.
-- **Approvals**: enforced on the node host via `~/.pigbot/exec-approvals.json`.
+- **Approvals**: enforced on the node host via `~/.clawdbot/exec-approvals.json`.
 
 ### Start a node host (foreground)
 
 On the node machine:
 
 ```bash
-pigbot node run --host <gateway-host> --port 18789 --display-name "Build Node"
+moltbot node run --host <gateway-host> --port 18789 --display-name "Build Node"
 ```
 
 ### Start a node host (service)
 
 ```bash
-pigbot node install --host <gateway-host> --port 18789 --display-name "Build Node"
-pigbot node restart
+moltbot node install --host <gateway-host> --port 18789 --display-name "Build Node"
+moltbot node restart
 ```
 
 ### Pair + name
@@ -69,34 +69,34 @@ pigbot node restart
 On the gateway host:
 
 ```bash
-pigbot nodes pending
-pigbot nodes approve <requestId>
-pigbot nodes list
+moltbot nodes pending
+moltbot nodes approve <requestId>
+moltbot nodes list
 ```
 
 Naming options:
-- `--display-name` on `pigbot node run` / `pigbot node install` (persists in `~/.pigbot/node.json` on the node).
-- `pigbot nodes rename --node <id|name|ip> --name "Build Node"` (gateway override).
+- `--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).
 
 ### Allowlist the commands
 
 Exec approvals are **per node host**. Add allowlist entries from the gateway:
 
 ```bash
-pigbot approvals allowlist add --node <id|name|ip> "/usr/bin/uname"
-pigbot approvals allowlist add --node <id|name|ip> "/usr/bin/sw_vers"
+moltbot approvals allowlist add --node <id|name|ip> "/usr/bin/uname"
+moltbot approvals allowlist add --node <id|name|ip> "/usr/bin/sw_vers"
 ```
 
-Approvals live on the node host at `~/.pigbot/exec-approvals.json`.
+Approvals live on the node host at `~/.clawdbot/exec-approvals.json`.
 
 ### Point exec at the node
 
 Configure defaults (gateway config):
 
 ```bash
-pigbot config set tools.exec.host node
-pigbot config set tools.exec.security allowlist
-pigbot config set tools.exec.node "<id-or-name>"
+moltbot config set tools.exec.host node
+moltbot config set tools.exec.security allowlist
+moltbot config set tools.exec.node "<id-or-name>"
 ```
 
 Or per session:
@@ -118,7 +118,7 @@ Related:
 Low-level (raw RPC):
 
 ```bash
-pigbot nodes invoke --node <idOrNameOrIp> --command canvas.eval --params '{"javaScript":"location.href"}'
+moltbot 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
-pigbot nodes canvas snapshot --node <idOrNameOrIp> --format png
-pigbot nodes canvas snapshot --node <idOrNameOrIp> --format jpg --max-width 1200 --quality 0.9
+moltbot nodes canvas snapshot --node <idOrNameOrIp> --format png
+moltbot nodes canvas snapshot --node <idOrNameOrIp> --format jpg --max-width 1200 --quality 0.9
 ```
 
 ### Canvas controls
 
 ```bash
-pigbot nodes canvas present --node <idOrNameOrIp> --target https://example.com
-pigbot nodes canvas hide --node <idOrNameOrIp>
-pigbot nodes canvas navigate https://example.com --node <idOrNameOrIp>
-pigbot nodes canvas eval --node <idOrNameOrIp> --js "document.title"
+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"
 ```
 
 Notes:
@@ -150,9 +150,9 @@ Notes:
 ### A2UI (Canvas)
 
 ```bash
-pigbot nodes canvas a2ui push --node <idOrNameOrIp> --text "Hello"
-pigbot nodes canvas a2ui push --node <idOrNameOrIp> --jsonl ./payload.jsonl
-pigbot nodes canvas a2ui reset --node <idOrNameOrIp>
+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>
 ```
 
 Notes:
@@ -163,16 +163,16 @@ Notes:
 Photos (`jpg`):
 
 ```bash
-pigbot nodes camera list --node <idOrNameOrIp>
-pigbot nodes camera snap --node <idOrNameOrIp>            # default: both facings (2 MEDIA lines)
-pigbot nodes camera snap --node <idOrNameOrIp> --facing front
+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
 ```
 
 Video clips (`mp4`):
 
 ```bash
-pigbot nodes camera clip --node <idOrNameOrIp> --duration 10s
-pigbot nodes camera clip --node <idOrNameOrIp> --duration 3000 --no-audio
+moltbot nodes camera clip --node <idOrNameOrIp> --duration 10s
+moltbot nodes camera clip --node <idOrNameOrIp> --duration 3000 --no-audio
 ```
 
 Notes:
@@ -185,8 +185,8 @@ Notes:
 Nodes expose `screen.record` (mp4). Example:
 
 ```bash
-pigbot nodes screen record --node <idOrNameOrIp> --duration 10s --fps 10
-pigbot nodes screen record --node <idOrNameOrIp> --duration 10s --fps 10 --no-audio
+moltbot nodes screen record --node <idOrNameOrIp> --duration 10s --fps 10
+moltbot 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
-pigbot nodes location get --node <idOrNameOrIp>
-pigbot nodes location get --node <idOrNameOrIp> --accuracy precise --max-age 15000 --location-timeout 10000
+moltbot nodes location get --node <idOrNameOrIp>
+moltbot 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
-pigbot nodes invoke --node <idOrNameOrIp> --command sms.send --params '{"to":"+15555550123","message":"Hello from Pigbot"}'
+moltbot nodes invoke --node <idOrNameOrIp> --command sms.send --params '{"to":"+15555550123","message":"Hello from Moltbot"}'
 ```
 
 Notes:
@@ -234,8 +234,8 @@ The headless node host exposes `system.run`, `system.which`, and `system.execApp
 Examples:
 
 ```bash
-pigbot nodes run --node <idOrNameOrIp> -- echo "Hello from mac node"
-pigbot nodes notify --node <idOrNameOrIp> --title "Ping" --body "Gateway ready"
+moltbot nodes run --node <idOrNameOrIp> -- echo "Hello from mac node"
+moltbot nodes notify --node <idOrNameOrIp> --title "Ping" --body "Gateway ready"
 ```
 
 Notes:
@@ -246,7 +246,7 @@ Notes:
 - macOS nodes drop `PATH` overrides; headless node hosts only accept `PATH` when it prepends the node host PATH.
 - On macOS node mode, `system.run` is gated by exec approvals in the macOS app (Settings → Exec approvals).
   Ask/allowlist/full behave the same as the headless node host; denied prompts return `SYSTEM_RUN_DENIED`.
-- On headless node host, `system.run` is gated by exec approvals (`~/.pigbot/exec-approvals.json`).
+- On headless node host, `system.run` is gated by exec approvals (`~/.clawdbot/exec-approvals.json`).
 
 ## Exec node binding
 
@@ -256,21 +256,21 @@ This sets the default node for `exec host=node` (and can be overridden per agent
 Global default:
 
 ```bash
-pigbot config set tools.exec.node "node-id-or-name"
+moltbot config set tools.exec.node "node-id-or-name"
 ```
 
 Per-agent override:
 
 ```bash
-pigbot config get agents.list
-pigbot config set agents.list[0].tools.exec.node "node-id-or-name"
+moltbot config get agents.list
+moltbot config set agents.list[0].tools.exec.node "node-id-or-name"
 ```
 
 Unset to allow any node:
 
 ```bash
-pigbot config unset tools.exec.node
-pigbot config unset agents.list[0].tools.exec.node
+moltbot config unset tools.exec.node
+moltbot config unset agents.list[0].tools.exec.node
 ```
 
 ## Permissions map
@@ -279,27 +279,27 @@ Nodes may include a `permissions` map in `node.list` / `node.describe`, keyed by
 
 ## Headless node host (cross-platform)
 
-Pigbot can run a **headless node host** (no UI) that connects to the Gateway
+Moltbot 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
-pigbot node run --host <gateway-host> --port 18789
+moltbot node run --host <gateway-host> --port 18789
 ```
 
 Notes:
 - Pairing is still required (the Gateway will show a node approval prompt).
-- The node host stores its node id, token, display name, and gateway connection info in `~/.pigbot/node.json`.
-- Exec approvals are enforced locally via `~/.pigbot/exec-approvals.json`
+- The node host stores its node id, token, display name, and gateway connection info in `~/.clawdbot/node.json`.
+- Exec approvals are enforced locally via `~/.clawdbot/exec-approvals.json`
   (see [Exec approvals](/tools/exec-approvals)).
 - On macOS, the headless node host prefers the companion app exec host when reachable and falls
-  back to local execution if the app is unavailable. Set `PIGBOT_NODE_EXEC_HOST=app` to require
-  the app, or `PIGBOT_NODE_EXEC_FALLBACK=0` to disable fallback.
+  back to local execution if the app is unavailable. Set `CLAWDBOT_NODE_EXEC_HOST=app` to require
+  the app, or `CLAWDBOT_NODE_EXEC_FALLBACK=0` to disable fallback.
 - Add `--tls` / `--tls-fingerprint` when the Gateway WS uses TLS.
 
 ## Mac node mode
 
-- The macOS menubar app connects to the Gateway WS server as a node (so `pigbot nodes …` works against this Mac).
+- The macOS menubar app connects to the Gateway WS server as a node (so `moltbot 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: `pigbot nodes location get --node <id>`.
+- CLI: `moltbot 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 Pigbot is open.”
+- While Using: “Only when Moltbot is open.”
 - Always: “Allow background location. Requires system permission.”
 - Precise: “Use precise GPS location. Toggle off to share approximate location.”

package/docs/nodes/media-understanding.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Media Understanding (Inbound) — 2026-01-17
 
-Pigbot can **summarize inbound media** (image/audio/video) before the reply pipeline runs. It auto‑detects when local tools or provider keys are available, and can be disabled or customized. If understanding is off, models still receive the original files/URLs as usual.
+Moltbot can **summarize inbound media** (image/audio/video) before the reply pipeline runs. It auto‑detects when local tools or provider keys are available, and can be disabled or customized. If understanding is off, models still receive the original files/URLs as usual.
 
 ## Goals
 - Optional: pre‑digest inbound media into short text for faster routing + better command parsing.
@@ -106,12 +106,12 @@ Rules:
 - If media exceeds `maxBytes`, that model is skipped and the **next model is tried**.
 - If the model returns more than `maxChars`, output is trimmed.
 - `prompt` defaults to simple “Describe the {media}.” plus the `maxChars` guidance (image/video only).
-- If `<capability>.enabled: true` but no models are configured, Pigbot tries the
+- If `<capability>.enabled: true` but no models are configured, Moltbot tries the
   **active reply model** when its provider supports the capability.
 
 ### Auto-detect media understanding (default)
 If `tools.media.<capability>.enabled` is **not** set to `false` and you haven’t
-configured models, Pigbot auto-detects in this order and **stops at the first
+configured models, Moltbot auto-detects in this order and **stops at the first
 working option**:
 
 1) **Local CLIs** (audio only; if installed)
@@ -140,7 +140,7 @@ Note: Binary detection is best-effort across macOS/Linux/Windows; ensure the CLI
 
 ## Capabilities (optional)
 If you set `capabilities`, the entry only runs for those media types. For shared
-lists, Pigbot can infer defaults:
+lists, Moltbot can infer defaults:
 - `openai`, `anthropic`, `minimax`: **image**
 - `google` (Gemini API): **image + audio + video**
 - `groq`: **audio**
@@ -149,7 +149,7 @@ lists, Pigbot can infer defaults:
 For CLI entries, **set `capabilities` explicitly** to avoid surprising matches.
 If you omit `capabilities`, the entry is eligible for the list it appears in.
 
-## Provider support matrix (Pigbot integrations)
+## Provider support matrix (Moltbot integrations)
 | Capability | Provider integration | Notes |
 |------------|----------------------|-------|
 | Image | OpenAI / Anthropic / Google / others via `pi-ai` | Any image-capable model in the registry works. |

package/docs/nodes/talk.md

@@ -40,7 +40,7 @@ Supported keys:
 - `seed`, `normalize`, `lang`, `output_format`, `latency_tier`
 - `once`
 
-## Config (`~/.pigbot/pigbot.json`)
+## Config (`~/.clawdbot/moltbot.json`)
 ```json5
 {
   "talk": {

package/docs/nodes/voicewake.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Voice Wake (Global Wake Words)
 
-Pigbot treats **wake words as a single global list** owned by the **Gateway**.
+Moltbot treats **wake words as a single global list** owned by the **Gateway**.
 
 - There are **no per-node custom wake words**.
 - **Any node/app UI may edit** the list; changes are persisted by the Gateway and broadcast to everyone.
@@ -16,7 +16,7 @@ Pigbot treats **wake words as a single global list** owned by the **Gateway**.
 
 Wake words are stored on the gateway machine at:
 
-- `~/.pigbot/settings/voicewake.json`
+- `~/.clawdbot/settings/voicewake.json`
 
 Shape:
 

package/docs/northflank.mdx

@@ -0,0 +1,53 @@
+---
+title: Deploy on Northflank
+---
+
+Deploy Moltbot on Northflank with a one-click template and finish setup in your browser.
+This is the easiest “no terminal on the server” path: Northflank runs the Gateway for you,
+and you configure everything via the `/setup` web wizard.
+
+## How to get started
+
+1. Click [Deploy Moltbot](https://northflank.com/stacks/deploy-moltbot) to open the template.  
+2. Create an [account on Northflank](https://app.northflank.com/signup) if you don’t already have one.  
+3. Click **Deploy Moltbot now**.  
+4. Set the required environment variable: `SETUP_PASSWORD`.
+5. Click **Deploy stack** to build and run the Moltbot template.
+6. Wait for the deployment to complete, then click **View resources**.
+7. Open the Moltbot service.
+8. Open the public Moltbot URL and complete setup at `/setup`.
+9. Open the Control UI at `/moltbot`.
+
+## What you get
+
+- Hosted Moltbot Gateway + Control UI
+- Web setup wizard at `/setup` (no terminal commands)
+- Persistent storage via Northflank Volume (`/data`) so config/credentials/workspace survive redeploys
+
+## Setup flow
+
+1) Visit `https://<your-northflank-domain>/setup` and enter your `SETUP_PASSWORD`.
+2) Choose a model/auth provider and paste your key.
+3) (Optional) Add Telegram/Discord/Slack tokens.
+4) Click **Run setup**.
+5) Open the Control UI at `https://<your-northflank-domain>/moltbot`
+
+If Telegram DMs are set to pairing, the setup wizard can approve the pairing code.
+
+## Getting chat tokens
+
+### Telegram bot token
+
+1) Message `@BotFather` in Telegram
+2) Run `/newbot`
+3) Copy the token (looks like `123456789:AA...`)
+4) Paste it into `/setup`
+
+### Discord bot token
+
+1) Go to https://discord.com/developers/applications
+2) **New Application** → choose a name
+3) **Bot** → **Add Bot**
+4) **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
+5) Copy the **Bot Token** and paste into `/setup`
+6) Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)

package/docs/perplexity.md

@@ -7,7 +7,7 @@ read_when:
 
 # Perplexity Sonar
 
-Pigbot can use Perplexity Sonar for the `web_search` tool. You can connect
+Moltbot can use Perplexity Sonar for the `web_search` tool. You can connect
 through Perplexity’s direct API or via OpenRouter.
 
 ## API options
@@ -64,7 +64,7 @@ If both `PERPLEXITY_API_KEY` and `OPENROUTER_API_KEY` are set, set
 `tools.web.search.perplexity.baseUrl` (or `tools.web.search.perplexity.apiKey`)
 to disambiguate.
 
-If no base URL is set, Pigbot chooses a default based on the API key source:
+If no base URL is set, Moltbot chooses a default based on the API key source:
 
 - `PERPLEXITY_API_KEY` or `pplx-...` → direct Perplexity (`https://api.perplexity.ai`)
 - `OPENROUTER_API_KEY` or `sk-or-...` → OpenRouter (`https://openrouter.ai/api/v1`)

package/docs/platforms/android.md

@@ -31,12 +31,12 @@ Android connects directly to the Gateway WebSocket (default `ws://<host>:18789`)
   - Same LAN with mDNS/NSD, **or**
   - Same Tailscale tailnet using Wide-Area Bonjour / unicast DNS-SD (see below), **or**
   - Manual gateway host/port (fallback)
-- You can run the CLI (`pigbot`) on the gateway machine (or via SSH).
+- You can run the CLI (`moltbot`) on the gateway machine (or via SSH).
 
 ### 1) Start the Gateway
 
 ```bash
-pigbot gateway --port 18789 --verbose
+moltbot gateway --port 18789 --verbose
 ```
 
 Confirm in logs you see something like:
@@ -44,7 +44,7 @@ Confirm in logs you see something like:
 
 For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to the tailnet IP:
 
-- Set `gateway.bind: "tailnet"` in `~/.pigbot/pigbot.json` on the gateway host.
+- Set `gateway.bind: "tailnet"` in `~/.clawdbot/moltbot.json` on the gateway host.
 - Restart the Gateway / macOS menubar app.
 
 ### 2) Verify discovery (optional)
@@ -52,7 +52,7 @@ For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to
 From the gateway machine:
 
 ```bash
-dns-sd -B _pigbot-gw._tcp local.
+dns-sd -B _moltbot-gw._tcp local.
 ```
 
 More debugging notes: [Bonjour](/gateway/bonjour).
@@ -61,8 +61,8 @@ More debugging notes: [Bonjour](/gateway/bonjour).
 
 Android NSD/mDNS discovery won’t cross networks. If your Android node and the gateway are on different networks but connected via Tailscale, use Wide-Area Bonjour / unicast DNS-SD instead:
 
-1) Set up a DNS-SD zone (example `pigbot.internal.`) on the gateway host and publish `_pigbot-gw._tcp` records.
-2) Configure Tailscale split DNS for `pigbot.internal` pointing at that DNS server.
+1) Set up a DNS-SD zone (example `moltbot.internal.`) on the gateway host and publish `_moltbot-gw._tcp` records.
+2) Configure Tailscale split DNS for `moltbot.internal` pointing at that DNS server.
 
 Details and example CoreDNS config: [Bonjour](/gateway/bonjour).
 
@@ -84,8 +84,8 @@ After the first successful pairing, Android auto-reconnects on launch:
 On the gateway machine:
 
 ```bash
-pigbot nodes pending
-pigbot nodes approve <requestId>
+moltbot nodes pending
+moltbot nodes approve <requestId>
 ```
 
 Pairing details: [Gateway pairing](/gateway/pairing).
@@ -94,11 +94,11 @@ Pairing details: [Gateway pairing](/gateway/pairing).
 
 - Via nodes status:
   ```bash
-  pigbot nodes status
+  moltbot nodes status
   ```
 - Via Gateway:
   ```bash
-  pigbot gateway call node.list --params "{}"
+  moltbot gateway call node.list --params "{}"
   ```
 
 ### 6) Chat + history
@@ -122,13 +122,13 @@ Note: nodes use the standalone canvas host on `canvasHost.port` (default `18793`
 2) Navigate the node to it (LAN):
 
 ```bash
-pigbot nodes invoke --node "<Android Node>" --command canvas.navigate --params '{"url":"http://<gateway-hostname>.local:18793/__pigbot__/canvas/"}'
+moltbot nodes invoke --node "<Android Node>" --command canvas.navigate --params '{"url":"http://<gateway-hostname>.local:18793/__moltbot__/canvas/"}'
 ```
 
-Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://<gateway-magicdns>:18793/__pigbot__/canvas/`.
+Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://<gateway-magicdns>:18793/__moltbot__/canvas/`.
 
 This server injects a live-reload client into HTML and reloads on file changes.
-The A2UI host lives at `http://<gateway-host>:18793/__pigbot__/a2ui/`.
+The A2UI host lives at `http://<gateway-host>:18793/__moltbot__/a2ui/`.
 
 Canvas commands (foreground only):
 - `canvas.eval`, `canvas.snapshot`, `canvas.navigate` (use `{"url":""}` or `{"url":"/"}` to return to the default scaffold). `canvas.snapshot` returns `{ format, base64 }` (default `format="jpeg"`).