@gguf/pigbot 0.0.1 → 0.0.2

package/docs/install/updating.md

@@ -1,40 +1,41 @@
 ---
-summary: "Updating Pigbot safely (global install or source), plus rollback strategy"
+summary: "Updating Moltbot safely (global install or source), plus rollback strategy"
 read_when:
-  - Updating Pigbot
+  - Updating Moltbot
   - Something breaks after an update
 ---
 
 # Updating
 
-Pigbot is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart (or use `pigbot update`, which restarts) → verify.
+Moltbot is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart (or use `moltbot update`, which restarts) → verify.
 
 ## Recommended: re-run the website installer (upgrade in place)
 
 The **preferred** update path is to re-run the installer from the website. It
-detects existing installs, upgrades in place, and runs `pigbot doctor` when
+detects existing installs, upgrades in place, and runs `moltbot doctor` when
 needed.
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash
+curl -fsSL https://molt.bot/install.sh | bash
 ```
 
 Notes:
 - Add `--no-onboard` if you don’t want the onboarding wizard to run again.
 - For **source installs**, use:
   ```bash
-  curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git --no-onboard
+  curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git --no-onboard
   ```
   The installer will `git pull --rebase` **only** if the repo is clean.
-- For **global installs**, the script uses `npm install -g pigbot@latest` under the hood.
+- For **global installs**, the script uses `npm install -g moltbot@latest` under the hood.
+- Legacy note: `moltbot` remains available as a compatibility shim.
 
 ## Before you update
 
 - Know how you installed: **global** (npm/pnpm) vs **from source** (git clone).
 - Know how your Gateway is running: **foreground terminal** vs **supervised service** (launchd/systemd).
 - Snapshot your tailoring:
-  - Config: `~/.pigbot/pigbot.json`
-  - Credentials: `~/.pigbot/credentials/`
+  - Config: `~/.clawdbot/moltbot.json`
+  - Credentials: `~/.clawdbot/credentials/`
   - Workspace: `~/clawd`
 
 ## Update (global install)
@@ -42,20 +43,20 @@ Notes:
 Global install (pick one):
 
 ```bash
-npm i -g pigbot@latest
+npm i -g moltbot@latest
 ```
 
 ```bash
-pnpm add -g pigbot@latest
+pnpm add -g moltbot@latest
 ```
 We do **not** recommend Bun for the Gateway runtime (WhatsApp/Telegram bugs).
 
 To switch update channels (git + npm installs):
 
 ```bash
-pigbot update --channel beta
-pigbot update --channel dev
-pigbot update --channel stable
+moltbot update --channel beta
+moltbot update --channel dev
+moltbot update --channel stable
 ```
 
 Use `--tag <dist-tag|version>` for a one-off install tag/version.
@@ -67,36 +68,36 @@ Note: on npm installs, the gateway logs an update hint on startup (checks the cu
 Then:
 
 ```bash
-pigbot doctor
-pigbot gateway restart
-pigbot health
+moltbot doctor
+moltbot gateway restart
+moltbot health
 ```
 
 Notes:
-- If your Gateway runs as a service, `pigbot gateway restart` is preferred over killing PIDs.
+- If your Gateway runs as a service, `moltbot gateway restart` is preferred over killing PIDs.
 - If you’re pinned to a specific version, see “Rollback / pinning” below.
 
-## Update (`pigbot update`)
+## Update (`moltbot update`)
 
 For **source installs** (git checkout), prefer:
 
 ```bash
-pigbot update
+moltbot update
 ```
 
 It runs a safe-ish update flow:
 - Requires a clean worktree.
 - Switches to the selected channel (tag or branch).
 - Fetches + rebases against the configured upstream (dev channel).
-- Installs deps, builds, builds the Control UI, and runs `pigbot doctor`.
+- Installs deps, builds, builds the Control UI, and runs `moltbot doctor`.
 - Restarts the gateway by default (use `--no-restart` to skip).
 
-If you installed via **npm/pnpm** (no git metadata), `pigbot update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead.
+If you installed via **npm/pnpm** (no git metadata), `moltbot update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead.
 
 ## Update (Control UI / RPC)
 
 The Control UI has **Update & Restart** (RPC: `update.run`). It:
-1) Runs the same source-update flow as `pigbot update` (git checkout only).
+1) Runs the same source-update flow as `moltbot update` (git checkout only).
 2) Writes a restart sentinel with a structured report (stdout/stderr tail).
 3) Restarts the gateway and pings the last active session with the report.
 
@@ -109,7 +110,7 @@ From the repo checkout:
 Preferred:
 
 ```bash
-pigbot update
+moltbot update
 ```
 
 Manual (equivalent-ish):
@@ -119,27 +120,27 @@ git pull
 pnpm install
 pnpm build
 pnpm ui:build # auto-installs UI deps on first run
-pigbot doctor
-pigbot health
+moltbot doctor
+moltbot health
 ```
 
 Notes:
-- `pnpm build` matters when you run the packaged `pigbot` binary ([`dist/entry.js`](https://github.com/pigbot/pigbot/blob/main/dist/entry.js)) or use Node to run `dist/`.
-- If you run from a repo checkout without a global install, use `pnpm pigbot ...` for CLI commands.
-- If you run directly from TypeScript (`pnpm pigbot ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor.
-- Switching between global and git installs is easy: install the other flavor, then run `pigbot doctor` so the gateway service entrypoint is rewritten to the current install.
+- `pnpm build` matters when you run the packaged `moltbot` binary ([`dist/entry.js`](https://github.com/moltbot/moltbot/blob/main/dist/entry.js)) or use Node to run `dist/`.
+- If you run from a repo checkout without a global install, use `pnpm moltbot ...` for CLI commands.
+- If you run directly from TypeScript (`pnpm moltbot ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor.
+- Switching between global and git installs is easy: install the other flavor, then run `moltbot doctor` so the gateway service entrypoint is rewritten to the current install.
 
-## Always run: `pigbot doctor`
+## Always Run: `moltbot doctor`
 
 Doctor is the “safe update” command. It’s intentionally boring: repair + migrate + warn.
 
-Note: if you’re on a **source install** (git checkout), `pigbot doctor` will offer to run `pigbot update` first.
+Note: if you’re on a **source install** (git checkout), `moltbot doctor` will offer to run `moltbot update` first.
 
 Typical things it does:
 - Migrate deprecated config keys / legacy config file locations.
 - Audit DM policies and warn on risky “open” settings.
 - Check Gateway health and can offer to restart.
-- Detect and migrate older gateway services (launchd/systemd; legacy schtasks) to current Pigbot services.
+- Detect and migrate older gateway services (launchd/systemd; legacy schtasks) to current Moltbot services.
 - On Linux, ensure systemd user lingering (so the Gateway survives logout).
 
 Details: [Doctor](/gateway/doctor)
@@ -149,18 +150,18 @@ Details: [Doctor](/gateway/doctor)
 CLI (works regardless of OS):
 
 ```bash
-pigbot gateway status
-pigbot gateway stop
-pigbot gateway restart
-pigbot gateway --port 18789
-pigbot logs --follow
+moltbot gateway status
+moltbot gateway stop
+moltbot gateway restart
+moltbot gateway --port 18789
+moltbot logs --follow
 ```
 
 If you’re supervised:
-- macOS launchd (app-bundled LaunchAgent): `launchctl kickstart -k gui/$UID/com.pigbot.gateway` (use `com.pigbot.<profile>` if set)
-- Linux systemd user service: `systemctl --user restart pigbot-gateway[-<profile>].service`
-- Windows (WSL2): `systemctl --user restart pigbot-gateway[-<profile>].service`
-  - `launchctl`/`systemctl` only work if the service is installed; otherwise run `pigbot gateway install`.
+- macOS launchd (app-bundled LaunchAgent): `launchctl kickstart -k gui/$UID/bot.molt.gateway` (use `bot.molt.<profile>`; legacy `com.clawdbot.*` still works)
+- Linux systemd user service: `systemctl --user restart moltbot-gateway[-<profile>].service`
+- Windows (WSL2): `systemctl --user restart moltbot-gateway[-<profile>].service`
+  - `launchctl`/`systemctl` only work if the service is installed; otherwise run `moltbot gateway install`.
 
 Runbook + exact service labels: [Gateway runbook](/gateway)
 
@@ -171,20 +172,20 @@ Runbook + exact service labels: [Gateway runbook](/gateway)
 Install a known-good version (replace `<version>` with the last working one):
 
 ```bash
-npm i -g pigbot@<version>
+npm i -g moltbot@<version>
 ```
 
 ```bash
-pnpm add -g pigbot@<version>
+pnpm add -g moltbot@<version>
 ```
 
-Tip: to see the current published version, run `npm view pigbot version`.
+Tip: to see the current published version, run `npm view moltbot version`.
 
 Then restart + re-run doctor:
 
 ```bash
-pigbot doctor
-pigbot gateway restart
+moltbot doctor
+moltbot gateway restart
 ```
 
 ### Pin (source) by date
@@ -201,7 +202,7 @@ Then reinstall deps + restart:
 ```bash
 pnpm install
 pnpm build
-pigbot gateway restart
+moltbot gateway restart
 ```
 
 If you want to go back to latest later:
@@ -213,6 +214,6 @@ git pull
 
 ## If you’re stuck
 
-- Run `pigbot doctor` again and read the output carefully (it often tells you the fix).
+- Run `moltbot doctor` again and read the output carefully (it often tells you the fix).
 - Check: [Troubleshooting](/gateway/troubleshooting)
 - Ask in Discord: https://channels.discord.gg/clawd

package/docs/logging.md

@@ -8,7 +8,7 @@ read_when:
 
 # Logging
 
-Pigbot logs in two places:
+Moltbot 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/pigbot/pigbot-YYYY-MM-DD.log`
+`/tmp/moltbot/moltbot-YYYY-MM-DD.log`
 
 The date uses the gateway host's local timezone.
 
-You can override this in `~/.pigbot/pigbot.json`:
+You can override this in `~/.clawdbot/moltbot.json`:
 
 ```json
 {
   "logging": {
-    "file": "/path/to/pigbot.log"
+    "file": "/path/to/moltbot.log"
   }
 }
 ```
@@ -41,7 +41,7 @@ You can override this in `~/.pigbot/pigbot.json`:
 Use the CLI to tail the gateway log file via RPC:
 
 ```bash
-pigbot logs --follow
+moltbot 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
-pigbot doctor
+moltbot 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
-pigbot channels logs --channel whatsapp
+moltbot 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 `~/.pigbot/pigbot.json`.
+All logging configuration lives under `logging` in `~/.clawdbot/moltbot.json`.
 
 ```json
 {
   "logging": {
     "level": "info",
-    "file": "/tmp/pigbot/pigbot-YYYY-MM-DD.log",
+    "file": "/tmp/moltbot/moltbot-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.
-- Pigbot exports via **OTLP/HTTP (protobuf)** today.
+- Moltbot exports via **OTLP/HTTP (protobuf)** today.
 
 ### Signals exported
 
@@ -192,6 +192,30 @@ Use this if you want diagnostics events available to plugins or custom sinks:
 }
 ```
 
+### Diagnostics flags (targeted logs)
+
+Use flags to turn on extra, targeted debug logs without raising `logging.level`.
+Flags are case-insensitive and support wildcards (e.g. `telegram.*` or `*`).
+
+```json
+{
+  "diagnostics": {
+    "flags": ["telegram.http"]
+  }
+}
+```
+
+Env override (one-off):
+
+```
+CLAWDBOT_DIAGNOSTICS=telegram.http,telegram.payload
+```
+
+Notes:
+- Flag logs go to the standard log file (same as `logging.file`).
+- Output is still redacted according to `logging.redactSensitive`.
+- Full guide: [/diagnostics/flags](/diagnostics/flags).
+
 ### Export to OpenTelemetry
 
 Diagnostics can be exported via the `diagnostics-otel` plugin (OTLP/HTTP). This
@@ -213,7 +237,7 @@ works with any OpenTelemetry collector/backend that accepts OTLP/HTTP.
       "enabled": true,
       "endpoint": "http://otel-collector:4318",
       "protocol": "http/protobuf",
-      "serviceName": "pigbot-gateway",
+      "serviceName": "moltbot-gateway",
       "traces": true,
       "metrics": true,
       "logs": true,
@@ -225,7 +249,7 @@ works with any OpenTelemetry collector/backend that accepts OTLP/HTTP.
 ```
 
 Notes:
-- You can also enable the plugin with `pigbot plugins enable diagnostics-otel`.
+- You can also enable the plugin with `moltbot 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).
@@ -238,58 +262,58 @@ Notes:
 ### Exported metrics (names + types)
 
 Model usage:
-- `pigbot.tokens` (counter, attrs: `pigbot.token`, `pigbot.channel`,
-  `pigbot.provider`, `pigbot.model`)
-- `pigbot.cost.usd` (counter, attrs: `pigbot.channel`, `pigbot.provider`,
-  `pigbot.model`)
-- `pigbot.run.duration_ms` (histogram, attrs: `pigbot.channel`,
-  `pigbot.provider`, `pigbot.model`)
-- `pigbot.context.tokens` (histogram, attrs: `pigbot.context`,
-  `pigbot.channel`, `pigbot.provider`, `pigbot.model`)
+- `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`)
 
 Message flow:
-- `pigbot.webhook.received` (counter, attrs: `pigbot.channel`,
-  `pigbot.webhook`)
-- `pigbot.webhook.error` (counter, attrs: `pigbot.channel`,
-  `pigbot.webhook`)
-- `pigbot.webhook.duration_ms` (histogram, attrs: `pigbot.channel`,
-  `pigbot.webhook`)
-- `pigbot.message.queued` (counter, attrs: `pigbot.channel`,
-  `pigbot.source`)
-- `pigbot.message.processed` (counter, attrs: `pigbot.channel`,
-  `pigbot.outcome`)
-- `pigbot.message.duration_ms` (histogram, attrs: `pigbot.channel`,
-  `pigbot.outcome`)
+- `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`)
 
 Queues + sessions:
-- `pigbot.queue.lane.enqueue` (counter, attrs: `pigbot.lane`)
-- `pigbot.queue.lane.dequeue` (counter, attrs: `pigbot.lane`)
-- `pigbot.queue.depth` (histogram, attrs: `pigbot.lane` or
-  `pigbot.channel=heartbeat`)
-- `pigbot.queue.wait_ms` (histogram, attrs: `pigbot.lane`)
-- `pigbot.session.state` (counter, attrs: `pigbot.state`, `pigbot.reason`)
-- `pigbot.session.stuck` (counter, attrs: `pigbot.state`)
-- `pigbot.session.stuck_age_ms` (histogram, attrs: `pigbot.state`)
-- `pigbot.run.attempt` (counter, attrs: `pigbot.attempt`)
+- `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`)
 
 ### Exported spans (names + key attributes)
 
-- `pigbot.model.usage`
-  - `pigbot.channel`, `pigbot.provider`, `pigbot.model`
-  - `pigbot.sessionKey`, `pigbot.sessionId`
-  - `pigbot.tokens.*` (input/output/cache_read/cache_write/total)
-- `pigbot.webhook.processed`
-  - `pigbot.channel`, `pigbot.webhook`, `pigbot.chatId`
-- `pigbot.webhook.error`
-  - `pigbot.channel`, `pigbot.webhook`, `pigbot.chatId`,
-    `pigbot.error`
-- `pigbot.message.processed`
-  - `pigbot.channel`, `pigbot.outcome`, `pigbot.chatId`,
-    `pigbot.messageId`, `pigbot.sessionKey`, `pigbot.sessionId`,
-    `pigbot.reason`
-- `pigbot.session.stuck`
-  - `pigbot.state`, `pigbot.ageMs`, `pigbot.queueDepth`,
-    `pigbot.sessionKey`, `pigbot.sessionId`
+- `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`
 
 ### Sampling + flushing
 
@@ -313,7 +337,7 @@ Queues + sessions:
 
 ## Troubleshooting tips
 
-- **Gateway not reachable?** Run `pigbot doctor` first.
+- **Gateway not reachable?** Run `moltbot 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

@@ -24,14 +24,14 @@ when the container is created.
 Auth is per-agent: each agent reads from its own `agentDir` auth store at:
 
 ```
-~/.pigbot/agents/<agentId>/agent/auth-profiles.json
+~/.clawdbot/agents/<agentId>/agent/auth-profiles.json
 ```
 
 Credentials are **not** shared between agents. Never reuse `agentDir` across agents.
 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 `pigbot sandbox explain`.
+For debugging “why is this blocked?”, see [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) and `moltbot 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:pigbot`: all built-in Pigbot tools (excludes provider plugins)
+- `group:moltbot`: all built-in Moltbot 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 `pigbot doctor`; prefer `agents.defaults` + `agents.list` going forward.
+Legacy `agent.*` configs are migrated by `moltbot doctor`; prefer `agents.defaults` + `agents.list` going forward.
 
 ---
 
@@ -331,12 +331,12 @@ After configuring multi-agent sandbox and tools:
 
 1. **Check agent resolution:**
    ```exec
-   pigbot agents list --bindings
+   moltbot agents list --bindings
    ```
 
 2. **Verify sandbox containers:**
    ```exec
-   docker ps --filter "label=pigbot.sandbox=1"
+   docker ps --filter "label=moltbot.sandbox=1"
    ```
 
 3. **Test tool restrictions:**
@@ -345,7 +345,7 @@ After configuring multi-agent sandbox and tools:
 
 4. **Monitor logs:**
    ```exec
-   tail -f "${PIGBOT_STATE_DIR:-$HOME/.pigbot}/logs/gateway.log" | grep -E "routing|sandbox|tools"
+   tail -f "${CLAWDBOT_STATE_DIR:-$HOME/.clawdbot}/logs/gateway.log" | grep -E "routing|sandbox|tools"
    ```
 
 ---

package/docs/network.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Network hub
 
-This hub links the core docs for how Pigbot connects, pairs, and secures
+This hub links the core docs for how Moltbot 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), Pigbot:
+- **Media understanding (audio)**: If audio understanding is enabled (or auto‑detected), Moltbot:
   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`,
-Pigbot auto-detects in this order and stops at the first working option:
+Moltbot 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)
 
-Pigbot supports **camera capture** for agent workflows:
+Moltbot 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
-pigbot nodes camera snap --node <id>               # default: both front + back (2 MEDIA lines)
-pigbot nodes camera snap --node <id> --facing front
-pigbot nodes camera clip --node <id> --duration 3000
-pigbot nodes camera clip --node <id> --no-audio
+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
 ```
 
 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** (`pigbot.cameraEnabled`)
+- **Settings → General → Allow Camera** (`moltbot.cameraEnabled`)
   - Default: **off**
   - When off: camera requests return “Camera disabled by user”.
 
 ### CLI helper (node invoke)
 
-Use the main `pigbot` CLI to invoke camera commands on the macOS node.
+Use the main `moltbot` CLI to invoke camera commands on the macOS node.
 
 Examples:
 
 ```bash
-pigbot nodes camera list --node <id>            # list camera ids
-pigbot nodes camera snap --node <id>            # prints MEDIA:<path>
-pigbot nodes camera snap --node <id> --max-width 1280
-pigbot nodes camera snap --node <id> --delay-ms 2000
-pigbot nodes camera snap --node <id> --device-id <id>
-pigbot nodes camera clip --node <id> --duration 10s          # prints MEDIA:<path>
-pigbot nodes camera clip --node <id> --duration-ms 3000      # prints MEDIA:<path> (legacy flag)
-pigbot nodes camera clip --node <id> --device-id <id>
-pigbot nodes camera clip --node <id> --no-audio
+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
 ```
 
 Notes:
-- `pigbot nodes camera snap` defaults to `maxWidth=1600` unless overridden.
+- `moltbot 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
-pigbot nodes screen record --node <id> --duration 10s --fps 15   # prints MEDIA:<path>
+moltbot nodes screen record --node <id> --duration 10s --fps 15   # prints MEDIA:<path>
 ```
 
 Notes: