@gguf/pigbot 0.0.1 → 0.0.2

package/docs/_config.yml

@@ -1,4 +1,4 @@
-title: "Pigbot Docs"
+title: "Moltbot Docs"
 description: "A TypeScript/Node gateway + macOS/iOS/Android companions for WhatsApp (web) and Telegram (bot)."
 markdown: kramdown
 highlighter: rouge
@@ -22,7 +22,7 @@ defaults:
 nav:
   - title: "Home"
     url: "/"
-  - title: "Pigbot Assistant"
+  - title: "Moltbot Assistant"
     url: "/start/clawd/"
   - title: "Gateway"
     url: "/gateway/"

package/docs/_layouts/default.html

@@ -17,7 +17,7 @@
     <script>
       (() => {
         try {
-          const stored = localStorage.getItem("pigbot:theme");
+          const stored = localStorage.getItem("moltbot:theme");
           if (stored === "light" || stored === "dark") document.documentElement.dataset.theme = stored;
         } catch {
           // ignore
@@ -35,7 +35,7 @@
     <header class="shell">
       <div class="shell__frame" role="banner">
         <div class="shell__titlebar">
-          <div class="brand" aria-label="Pigbot docs terminal">
+          <div class="brand" aria-label="Moltbot docs terminal">
             <img
               class="brand__logo"
               src="{{ "/assets/pixel-lobster.svg" | relative_url }}"
@@ -45,17 +45,17 @@
               decoding="async"
             />
             <div class="brand__text">
-              <div class="brand__name">Pigbot</div>
+              <div class="brand__name">Moltbot</div>
               <div class="brand__hint">docs // lobster terminal</div>
             </div>
           </div>
 
           <div class="titlebar__actions">
-            <a class="titlebar__cta" href="https://github.com/pigbot/pigbot">
+            <a class="titlebar__cta" href="https://github.com/moltbot/moltbot">
               <span class="titlebar__cta-label">GitHub</span>
               <span class="titlebar__cta-meta">repo</span>
             </a>
-            <a class="titlebar__cta titlebar__cta--accent" href="https://github.com/pigbot/pigbot/releases/latest">
+            <a class="titlebar__cta titlebar__cta--accent" href="https://github.com/moltbot/moltbot/releases/latest">
               <span class="titlebar__cta-label">Download</span>
               <span class="titlebar__cta-meta">latest</span>
             </a>
@@ -90,7 +90,7 @@
     <main id="content" class="content" role="main">
       <div class="terminal">
         <div class="terminal__prompt" aria-hidden="true">
-          <span class="prompt__user">clawd</span>@<span class="prompt__host">pigbot</span>:<span class="prompt__path">~/docs</span>$<span class="prompt__cmd">
+          <span class="prompt__user">clawd</span>@<span class="prompt__host">moltbot</span>:<span class="prompt__path">~/docs</span>$<span class="prompt__cmd">
             {% if page.url == "/" %}cat index.md{% else %}less {{ page.path }}{% endif %}
           </span>
         </div>
@@ -116,11 +116,11 @@
 
         <footer class="terminal__footer" role="contentinfo">
           <div class="footer__line">
-            <span class="footer__sig">pigbot.ai</span>
+            <span class="footer__sig">moltbot.ai</span>
             <span class="footer__sep">·</span>
-            <a href="https://github.com/pigbot/pigbot">source</a>
+            <a href="https://github.com/moltbot/moltbot">source</a>
             <span class="footer__sep">·</span>
-            <a href="https://github.com/pigbot/pigbot/releases">releases</a>
+            <a href="https://github.com/moltbot/moltbot/releases">releases</a>
           </div>
           <div class="footer__hint" aria-hidden="true">
             tip: press <kbd>F2</kbd> (Mac: <kbd>fn</kbd>+<kbd>F2</kbd>) to flip

package/docs/assets/terminal.css

@@ -115,6 +115,9 @@ body::after {
 }
 
 .shell {
+  position: sticky;
+  top: 0;
+  z-index: 100;
   padding: 22px 16px 10px;
 }
 

package/docs/assets/theme.js

@@ -1,4 +1,4 @@
-const THEME_STORAGE_KEY = "pigbot:theme";
+const THEME_STORAGE_KEY = "moltbot:theme";
 
 function safeGet(key) {
   try {

package/docs/automation/auth-monitoring.md

@@ -6,13 +6,13 @@ read_when:
 ---
 # Auth monitoring
 
-Pigbot exposes OAuth expiry health via `pigbot models status`. Use that for
+Moltbot exposes OAuth expiry health via `moltbot models status`. Use that for
 automation and alerting; scripts are optional extras for phone workflows.
 
 ## Preferred: CLI check (portable)
 
 ```bash
-pigbot models status --check
+moltbot models status --check
 ```
 
 Exit codes:
@@ -27,15 +27,15 @@ This works in cron/systemd and requires no extra scripts.
 These live under `scripts/` and are **optional**. They assume SSH access to the
 gateway host and are tuned for systemd + Termux.
 
-- `scripts/claude-auth-status.sh` now uses `pigbot models status --json` as the
+- `scripts/claude-auth-status.sh` now uses `moltbot models status --json` as the
   source of truth (falling back to direct file reads if the CLI is unavailable),
-  so keep `pigbot` on `PATH` for timers.
+  so keep `moltbot` on `PATH` for timers.
 - `scripts/auth-monitor.sh`: cron/systemd timer target; sends alerts (ntfy or phone).
-- `scripts/systemd/pigbot-auth-monitor.{service,timer}`: systemd user timer.
-- `scripts/claude-auth-status.sh`: Claude Code + Pigbot auth checker (full/json/simple).
+- `scripts/systemd/moltbot-auth-monitor.{service,timer}`: systemd user timer.
+- `scripts/claude-auth-status.sh`: Claude Code + Moltbot auth checker (full/json/simple).
 - `scripts/mobile-reauth.sh`: guided re‑auth flow over SSH.
 - `scripts/termux-quick-auth.sh`: one‑tap widget status + open auth URL.
 - `scripts/termux-auth-widget.sh`: full guided widget flow.
-- `scripts/termux-sync-widget.sh`: sync Claude Code creds → Pigbot.
+- `scripts/termux-sync-widget.sh`: sync Claude Code creds → Moltbot.
 
 If you don’t need phone automation or systemd timers, skip these scripts.

package/docs/automation/cron-jobs.md

@@ -17,7 +17,7 @@ cron is the mechanism.
 
 ## TL;DR
 - Cron runs **inside the Gateway** (not inside the model).
-- Jobs persist under `~/.pigbot/cron/` so restarts don’t lose schedules.
+- Jobs persist under `~/.clawdbot/cron/` so restarts don’t lose schedules.
 - Two execution styles:
   - **Main session**: enqueue a system event, then run on the next heartbeat.
   - **Isolated**: run a dedicated agent turn in `cron:<jobId>`, optionally deliver output.
@@ -151,8 +151,8 @@ Prefixed targets like `telegram:...` / `telegram:group:...` are also accepted:
 - `telegram:group:-1001234567890:topic:123`
 
 ## Storage & history
-- Job store: `~/.pigbot/cron/jobs.json` (Gateway-managed JSON).
-- Run history: `~/.pigbot/cron/runs/<jobId>.jsonl` (JSONL, auto-pruned).
+- Job store: `~/.clawdbot/cron/jobs.json` (Gateway-managed JSON).
+- Run history: `~/.clawdbot/cron/runs/<jobId>.jsonl` (JSONL, auto-pruned).
 - Override store path: `cron.store` in config.
 
 ## Configuration
@@ -161,7 +161,7 @@ Prefixed targets like `telegram:...` / `telegram:group:...` are also accepted:
 {
   cron: {
     enabled: true, // default true
-    store: "~/.pigbot/cron/jobs.json",
+    store: "~/.clawdbot/cron/jobs.json",
     maxConcurrentRuns: 1 // default 1
   }
 }
@@ -169,13 +169,13 @@ Prefixed targets like `telegram:...` / `telegram:group:...` are also accepted:
 
 Disable cron entirely:
 - `cron.enabled: false` (config)
-- `PIGBOT_SKIP_CRON=1` (env)
+- `CLAWDBOT_SKIP_CRON=1` (env)
 
 ## CLI quickstart
 
 One-shot reminder (UTC ISO, auto-delete after success):
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Send reminder" \
   --at "2026-01-12T18:00:00Z" \
   --session main \
@@ -186,7 +186,7 @@ pigbot cron add \
 
 One-shot reminder (main session, wake immediately):
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Calendar check" \
   --at "20m" \
   --session main \
@@ -196,7 +196,7 @@ pigbot cron add \
 
 Recurring isolated job (deliver to WhatsApp):
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Morning status" \
   --cron "0 7 * * *" \
   --tz "America/Los_Angeles" \
@@ -209,7 +209,7 @@ pigbot cron add \
 
 Recurring isolated job (deliver to a Telegram topic):
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Nightly summary (topic)" \
   --cron "0 22 * * *" \
   --tz "America/Los_Angeles" \
@@ -222,7 +222,7 @@ pigbot cron add \
 
 Isolated job with model and thinking override:
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Deep analysis" \
   --cron "0 6 * * 1" \
   --tz "America/Los_Angeles" \
@@ -237,22 +237,22 @@ pigbot cron add \
 Agent selection (multi-agent setups):
 ```bash
 # Pin a job to agent "ops" (falls back to default if that agent is missing)
-pigbot cron add --name "Ops sweep" --cron "0 6 * * *" --session isolated --message "Check ops queue" --agent ops
+moltbot cron add --name "Ops sweep" --cron "0 6 * * *" --session isolated --message "Check ops queue" --agent ops
 
 # Switch or clear the agent on an existing job
-pigbot cron edit <jobId> --agent ops
-pigbot cron edit <jobId> --clear-agent
+moltbot cron edit <jobId> --agent ops
+moltbot cron edit <jobId> --clear-agent
 ```
 ```
 
 Manual run (debug):
 ```bash
-pigbot cron run <jobId> --force
+moltbot cron run <jobId> --force
 ```
 
 Edit an existing job (patch fields):
 ```bash
-pigbot cron edit <jobId> \
+moltbot cron edit <jobId> \
   --message "Updated prompt" \
   --model "opus" \
   --thinking low
@@ -260,23 +260,23 @@ pigbot cron edit <jobId> \
 
 Run history:
 ```bash
-pigbot cron runs --id <jobId> --limit 50
+moltbot cron runs --id <jobId> --limit 50
 ```
 
 Immediate system event without creating a job:
 ```bash
-pigbot system event --mode now --text "Next heartbeat: check battery."
+moltbot system event --mode now --text "Next heartbeat: check battery."
 ```
 
 ## Gateway API surface
 - `cron.list`, `cron.status`, `cron.add`, `cron.update`, `cron.remove`
 - `cron.run` (force or due), `cron.runs`
-For immediate system events without a job, use [`pigbot system event`](/cli/system).
+For immediate system events without a job, use [`moltbot system event`](/cli/system).
 
 ## Troubleshooting
 
 ### “Nothing runs”
-- Check cron is enabled: `cron.enabled` and `PIGBOT_SKIP_CRON`.
+- Check cron is enabled: `cron.enabled` and `CLAWDBOT_SKIP_CRON`.
 - Check the Gateway is running continuously (cron runs inside the Gateway process).
 - For `cron` schedules: confirm timezone (`--tz`) vs the host timezone.
 

package/docs/automation/cron-vs-heartbeat.md

@@ -95,7 +95,7 @@ Cron jobs run at **exact times** and can run in isolated sessions without affect
 ### Cron example: Daily morning briefing
 
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Morning briefing" \
   --cron "0 7 * * *" \
   --tz "America/New_York" \
@@ -112,7 +112,7 @@ This runs at exactly 7:00 AM New York time, uses Opus for quality, and delivers
 ### Cron example: One-shot reminder
 
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Meeting reminder" \
   --at "20m" \
   --session main \
@@ -168,13 +168,13 @@ The most efficient setup uses **both**:
 **Cron jobs** (precise timing):
 ```bash
 # Daily morning briefing at 7am
-pigbot cron add --name "Morning brief" --cron "0 7 * * *" --session isolated --message "..." --deliver
+moltbot cron add --name "Morning brief" --cron "0 7 * * *" --session isolated --message "..." --deliver
 
 # Weekly project review on Mondays at 9am
-pigbot cron add --name "Weekly review" --cron "0 9 * * 1" --session isolated --message "..." --model opus
+moltbot cron add --name "Weekly review" --cron "0 9 * * 1" --session isolated --message "..." --model opus
 
 # One-shot reminder
-pigbot cron add --name "Call back" --at "2h" --session main --system-event "Call back the client" --wake now
+moltbot cron add --name "Call back" --at "2h" --session main --system-event "Call back the client" --wake now
 ```
 
 
@@ -201,7 +201,7 @@ For ad-hoc workflows, call Lobster directly.
 
 - Lobster runs as a **local subprocess** (`lobster` CLI) in tool mode and returns a **JSON envelope**.
 - If the tool returns `needs_approval`, you resume with a `resumeToken` and `approve` flag.
-- The tool is an **optional plugin**; you must allowlist `lobster` in `tools.allow`.
+- The tool is an **optional plugin**; enable it additively via `tools.alsoAllow: ["lobster"]` (recommended).
 - If you pass `lobsterPath`, it must be an **absolute path**.
 
 See [Lobster](/tools/lobster) for full usage and examples.
@@ -226,7 +226,7 @@ Use `--session main` with `--system-event` when you want:
 - No separate isolated run
 
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Check project" \
   --every "4h" \
   --session main \
@@ -243,7 +243,7 @@ Use `--session isolated` when you want:
 - History that doesn't clutter main session
 
 ```bash
-pigbot cron add \
+moltbot cron add \
   --name "Deep analysis" \
   --cron "0 6 * * 0" \
   --session isolated \

package/docs/automation/gmail-pubsub.md

@@ -1,19 +1,19 @@
 ---
-summary: "Gmail Pub/Sub push wired into Pigbot webhooks via gogcli"
+summary: "Gmail Pub/Sub push wired into Moltbot webhooks via gogcli"
 read_when:
-  - Wiring Gmail inbox triggers to Pigbot
+  - Wiring Gmail inbox triggers to Moltbot
   - Setting up Pub/Sub push for agent wake
 ---
 
-# Gmail Pub/Sub -> Pigbot
+# Gmail Pub/Sub -> Moltbot
 
-Goal: Gmail watch -> Pub/Sub push -> `gog gmail watch serve` -> Pigbot webhook.
+Goal: Gmail watch -> Pub/Sub push -> `gog gmail watch serve` -> Moltbot webhook.
 
 ## Prereqs
 
 - `gcloud` installed and logged in ([install guide](https://docs.cloud.google.com/sdk/docs/install-sdk)).
 - `gog` (gogcli) installed and authorized for the Gmail account ([gogcli.sh](https://gogcli.sh/)).
-- Pigbot hooks enabled (see [Webhooks](/automation/webhook)).
+- Moltbot hooks enabled (see [Webhooks](/automation/webhook)).
 - `tailscale` logged in ([tailscale.com](https://tailscale.com/)). Supported setup uses Tailscale Funnel for the public HTTPS endpoint.
   Other tunnel services can work, but are DIY/unsupported and require manual wiring.
   Right now, Tailscale is what we support.
@@ -24,7 +24,7 @@ Example hook config (enable Gmail preset mapping):
 {
   hooks: {
     enabled: true,
-    token: "PIGBOT_HOOK_TOKEN",
+    token: "CLAWDBOT_HOOK_TOKEN",
     path: "/hooks",
     presets: ["gmail"]
   }
@@ -38,7 +38,7 @@ that sets `deliver` + optional `channel`/`to`:
 {
   hooks: {
     enabled: true,
-    token: "PIGBOT_HOOK_TOKEN",
+    token: "CLAWDBOT_HOOK_TOKEN",
     presets: ["gmail"],
     mappings: [
       {
@@ -83,25 +83,27 @@ Notes:
 - Per-hook `model`/`thinking` in the mapping still overrides these defaults.
 - Fallback order: `hooks.gmail.model` → `agents.defaults.model.fallbacks` → primary (auth/rate-limit/timeouts).
 - If `agents.defaults.models` is set, the Gmail model must be in the allowlist.
+- Gmail hook content is wrapped with external-content safety boundaries by default.
+  To disable (dangerous), set `hooks.gmail.allowUnsafeExternalContent: true`.
 
 To customize payload handling further, add `hooks.mappings` or a JS/TS transform module
 under `hooks.transformsDir` (see [Webhooks](/automation/webhook)).
 
 ## Wizard (recommended)
 
-Use the Pigbot helper to wire everything together (installs deps on macOS via brew):
+Use the Moltbot helper to wire everything together (installs deps on macOS via brew):
 
 ```bash
-pigbot webhooks gmail setup \
-  --account pigbot@gmail.com
+moltbot webhooks gmail setup \
+  --account moltbot@gmail.com
 ```
 
 Defaults:
 - Uses Tailscale Funnel for the public push endpoint.
-- Writes `hooks.gmail` config for `pigbot webhooks gmail run`.
+- Writes `hooks.gmail` config for `moltbot webhooks gmail run`.
 - Enables the Gmail hook preset (`hooks.presets: ["gmail"]`).
 
-Path note: when `tailscale.mode` is enabled, Pigbot automatically sets
+Path note: when `tailscale.mode` is enabled, Moltbot automatically sets
 `hooks.gmail.serve.path` to `/` and keeps the public path at
 `hooks.gmail.tailscale.path` (default `/gmail-pubsub`) because Tailscale
 strips the set-path prefix before proxying.
@@ -117,14 +119,14 @@ via Homebrew; on Linux install them manually first.
 Gateway auto-start (recommended):
 - When `hooks.enabled=true` and `hooks.gmail.account` is set, the Gateway starts
   `gog gmail watch serve` on boot and auto-renews the watch.
-- Set `PIGBOT_SKIP_GMAIL_WATCHER=1` to opt out (useful if you run the daemon yourself).
+- Set `CLAWDBOT_SKIP_GMAIL_WATCHER=1` to opt out (useful if you run the daemon yourself).
 - Do not run the manual daemon at the same time, or you will hit
   `listen tcp 127.0.0.1:8788: bind: address already in use`.
 
 Manual daemon (starts `gog gmail watch serve` + auto-renew):
 
 ```bash
-pigbot webhooks gmail run
+moltbot webhooks gmail run
 ```
 
 ## One-time setup
@@ -162,7 +164,7 @@ gcloud pubsub topics add-iam-policy-binding gog-gmail-watch \
 
 ```bash
 gog gmail watch start \
-  --account pigbot@gmail.com \
+  --account moltbot@gmail.com \
   --label INBOX \
   --topic projects/<project-id>/topics/gog-gmail-watch
 ```
@@ -175,23 +177,23 @@ Local example (shared token auth):
 
 ```bash
 gog gmail watch serve \
-  --account pigbot@gmail.com \
+  --account moltbot@gmail.com \
   --bind 127.0.0.1 \
   --port 8788 \
   --path /gmail-pubsub \
   --token <shared> \
   --hook-url http://127.0.0.1:18789/hooks/gmail \
-  --hook-token PIGBOT_HOOK_TOKEN \
+  --hook-token CLAWDBOT_HOOK_TOKEN \
   --include-body \
   --max-bytes 20000
 ```
 
 Notes:
 - `--token` protects the push endpoint (`x-gog-token` or `?token=`).
-- `--hook-url` points to Pigbot `/hooks/gmail` (mapped; isolated run + summary to main).
-- `--include-body` and `--max-bytes` control the body snippet sent to Pigbot.
+- `--hook-url` points to Moltbot `/hooks/gmail` (mapped; isolated run + summary to main).
+- `--include-body` and `--max-bytes` control the body snippet sent to Moltbot.
 
-Recommended: `pigbot webhooks gmail run` wraps the same flow and auto-renews the watch.
+Recommended: `moltbot webhooks gmail run` wraps the same flow and auto-renews the watch.
 
 ## Expose the handler (advanced, unsupported)
 
@@ -222,8 +224,8 @@ Send a message to the watched inbox:
 
 ```bash
 gog gmail send \
-  --account pigbot@gmail.com \
-  --to pigbot@gmail.com \
+  --account moltbot@gmail.com \
+  --to moltbot@gmail.com \
   --subject "watch test" \
   --body "ping"
 ```
@@ -231,8 +233,8 @@ gog gmail send \
 Check watch state and history:
 
 ```bash
-gog gmail watch status --account pigbot@gmail.com
-gog gmail history --account pigbot@gmail.com --since <historyId>
+gog gmail watch status --account moltbot@gmail.com
+gog gmail history --account moltbot@gmail.com --since <historyId>
 ```
 
 ## Troubleshooting
@@ -244,7 +246,7 @@ gog gmail history --account pigbot@gmail.com --since <historyId>
 ## Cleanup
 
 ```bash
-gog gmail watch stop --account pigbot@gmail.com
+gog gmail watch stop --account moltbot@gmail.com
 gcloud pubsub subscriptions delete gog-gmail-watch-push
 gcloud pubsub topics delete gog-gmail-watch
 ```

package/docs/automation/poll.md

@@ -16,19 +16,19 @@ read_when:
 
 ```bash
 # WhatsApp
-pigbot message poll --target +15555550123 \
+moltbot message poll --target +15555550123 \
   --poll-question "Lunch today?" --poll-option "Yes" --poll-option "No" --poll-option "Maybe"
-pigbot message poll --target 123456789@g.us \
+moltbot message poll --target 123456789@g.us \
   --poll-question "Meeting time?" --poll-option "10am" --poll-option "2pm" --poll-option "4pm" --poll-multi
 
 # Discord
-pigbot message poll --channel discord --target channel:123456789 \
+moltbot message poll --channel discord --target channel:123456789 \
   --poll-question "Snack?" --poll-option "Pizza" --poll-option "Sushi"
-pigbot message poll --channel discord --target channel:123456789 \
+moltbot message poll --channel discord --target channel:123456789 \
   --poll-question "Plan?" --poll-option "A" --poll-option "B" --poll-duration-hours 48
 
 # MS Teams
-pigbot message poll --channel msteams --target conversation:19:abc@thread.tacv2 \
+moltbot message poll --channel msteams --target conversation:19:abc@thread.tacv2 \
   --poll-question "Lunch?" --poll-option "Pizza" --poll-option "Sushi"
 ```
 
@@ -53,11 +53,11 @@ Params:
 ## Channel differences
 - WhatsApp: 2-12 options, `maxSelections` must be within option count, ignores `durationHours`.
 - Discord: 2-10 options, `durationHours` clamped to 1-768 hours (default 24). `maxSelections > 1` enables multi-select; Discord does not support a strict selection count.
-- MS Teams: Adaptive Card polls (Pigbot-managed). No native poll API; `durationHours` is ignored.
+- MS Teams: Adaptive Card polls (Moltbot-managed). No native poll API; `durationHours` is ignored.
 
 ## Agent tool (Message)
 Use the `message` tool with `poll` action (`to`, `pollQuestion`, `pollOption`, optional `pollMulti`, `pollDurationHours`, `channel`).
 
 Note: Discord has no “pick exactly N” mode; `pollMulti` maps to multi-select.
 Teams polls are rendered as Adaptive Cards and require the gateway to stay online
-to record votes in `~/.pigbot/msteams-polls.json`.
+to record votes in `~/.clawdbot/msteams-polls.json`.

package/docs/automation/webhook.md

@@ -2,7 +2,7 @@
 summary: "Webhook ingress for wake and isolated agent runs"
 read_when:
   - Adding or changing webhook endpoints
-  - Wiring external systems into Pigbot
+  - Wiring external systems into Moltbot
 ---
 
 # Webhooks
@@ -27,10 +27,10 @@ Notes:
 
 ## Auth
 
-Every request must include the hook token:
-- `Authorization: Bearer <token>`
-- or `x-pigbot-token: <token>`
-- or `?token=<token>`
+Every request must include the hook token. Prefer headers:
+- `Authorization: Bearer <token>` (recommended)
+- `x-moltbot-token: <token>`
+- `?token=<token>` (deprecated; logs a warning and will be removed in a future major release)
 
 ## Endpoints
 
@@ -96,7 +96,9 @@ Mapping options (summary):
 - TS transforms require a TS loader (e.g. `bun` or `tsx`) or precompiled `.js` at runtime.
 - Set `deliver: true` + `channel`/`to` on mappings to route replies to a chat surface
   (`channel` defaults to `last` and falls back to WhatsApp).
-- `pigbot webhooks gmail setup` writes `hooks.gmail` config for `pigbot webhooks gmail run`.
+- `allowUnsafeExternalContent: true` disables the external content safety wrapper for that hook
+  (dangerous; only for trusted internal sources).
+- `moltbot webhooks gmail setup` writes `hooks.gmail` config for `moltbot webhooks gmail run`.
 See [Gmail Pub/Sub](/automation/gmail-pubsub) for the full Gmail watch flow.
 
 ## Responses
@@ -118,7 +120,7 @@ curl -X POST http://127.0.0.1:18789/hooks/wake \
 
 ```bash
 curl -X POST http://127.0.0.1:18789/hooks/agent \
-  -H 'x-pigbot-token: SECRET' \
+  -H 'x-moltbot-token: SECRET' \
   -H 'Content-Type: application/json' \
   -d '{"message":"Summarize inbox","name":"Email","wakeMode":"next-heartbeat"}'
 ```
@@ -129,7 +131,7 @@ Add `model` to the agent payload (or mapping) to override the model for that run
 
 ```bash
 curl -X POST http://127.0.0.1:18789/hooks/agent \
-  -H 'x-pigbot-token: SECRET' \
+  -H 'x-moltbot-token: SECRET' \
   -H 'Content-Type: application/json' \
   -d '{"message":"Summarize inbox","name":"Email","model":"openai/gpt-5.2-mini"}'
 ```
@@ -148,3 +150,6 @@ curl -X POST http://127.0.0.1:18789/hooks/gmail \
 - Keep hook endpoints behind loopback, tailnet, or trusted reverse proxy.
 - Use a dedicated hook token; do not reuse gateway auth tokens.
 - Avoid including sensitive raw payloads in webhook logs.
+- Hook payloads are treated as untrusted and wrapped with safety boundaries by default.
+  If you must disable this for a specific hook, set `allowUnsafeExternalContent: true`
+  in that hook's mapping (dangerous).

package/docs/bedrock.md

@@ -1,12 +1,12 @@
 ---
-summary: "Use Amazon Bedrock (Converse API) models with Pigbot"
+summary: "Use Amazon Bedrock (Converse API) models with Moltbot"
 read_when:
-  - You want to use Amazon Bedrock models with Pigbot
+  - You want to use Amazon Bedrock models with Moltbot
   - You need AWS credential/region setup for model calls
 ---
 # Amazon Bedrock
 
-Pigbot can use **Amazon Bedrock** models via pi‑ai’s **Bedrock Converse**
+Moltbot can use **Amazon Bedrock** models via pi‑ai’s **Bedrock Converse**
 streaming provider. Bedrock auth uses the **AWS SDK default credential chain**,
 not an API key.
 
@@ -19,7 +19,7 @@ not an API key.
 
 ## Automatic model discovery
 
-If AWS credentials are detected, Pigbot can automatically discover Bedrock
+If AWS credentials are detected, Moltbot can automatically discover Bedrock
 models that support **streaming** and **text output**. Discovery uses
 `bedrock:ListFoundationModels` and is cached (default: 1 hour).
 
@@ -97,9 +97,9 @@ export AWS_BEARER_TOKEN_BEDROCK="..."
 
 ## EC2 Instance Roles
 
-When running Pigbot on an EC2 instance with an IAM role attached, the AWS SDK
+When running Moltbot on an EC2 instance with an IAM role attached, the AWS SDK
 will automatically use the instance metadata service (IMDS) for authentication.
-However, Pigbot's credential detection currently only checks for environment
+However, Moltbot's credential detection currently only checks for environment
 variables, not IMDS credentials.
 
 **Workaround:** Set `AWS_PROFILE=default` to signal that AWS credentials are
@@ -146,8 +146,8 @@ aws ec2 associate-iam-instance-profile \
   --iam-instance-profile Name=EC2-Bedrock-Access
 
 # 3. On the EC2 instance, enable discovery
-pigbot config set models.bedrockDiscovery.enabled true
-pigbot config set models.bedrockDiscovery.region us-east-1
+moltbot config set models.bedrockDiscovery.enabled true
+moltbot config set models.bedrockDiscovery.region us-east-1
 
 # 4. Set the workaround env vars
 echo 'export AWS_PROFILE=default' >> ~/.bashrc
@@ -155,7 +155,7 @@ echo 'export AWS_REGION=us-east-1' >> ~/.bashrc
 source ~/.bashrc
 
 # 5. Verify models are discovered
-pigbot models list
+moltbot models list
 ```
 
 ## Notes
@@ -163,7 +163,7 @@ pigbot models list
 - Bedrock requires **model access** enabled in your AWS account/region.
 - Automatic discovery needs the `bedrock:ListFoundationModels` permission.
 - If you use profiles, set `AWS_PROFILE` on the gateway host.
-- Pigbot surfaces the credential source in this order: `AWS_BEARER_TOKEN_BEDROCK`,
+- Moltbot surfaces the credential source in this order: `AWS_BEARER_TOKEN_BEDROCK`,
   then `AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`, then `AWS_PROFILE`, then the
   default AWS SDK chain.
 - Reasoning support depends on the model; check the Bedrock model card for

package/docs/brave-search.md

@@ -7,7 +7,7 @@ read_when:
 
 # Brave Search API
 
-Pigbot uses Brave Search as the default provider for `web_search`.
+Moltbot uses Brave Search as the default provider for `web_search`.
 
 ## Get an API key