@gguf/pigbot 0.0.1 → 0.0.2

package/docs/platforms/index.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Platforms
 
-Pigbot core is written in TypeScript. **Node is the recommended runtime**.
+Moltbot core is written in TypeScript. **Node is the recommended runtime**.
 Bun is not recommended for the Gateway (WhatsApp/Telegram bugs).
 
 Companion apps exist for macOS (menu bar app) and mobile nodes (iOS/Android). Windows and
@@ -24,9 +24,9 @@ Native companion apps for Windows are also planned; the Gateway is recommended v
 ## VPS & hosting
 
 - VPS hub: [VPS hosting](/vps)
-- Railway (one-click): [Railway](/railway)
 - Fly.io: [Fly.io](/platforms/fly)
 - Hetzner (Docker): [Hetzner](/platforms/hetzner)
+- GCP (Compute Engine): [GCP](/platforms/gcp)
 - exe.dev (VM + HTTPS proxy): [exe.dev](/platforms/exe-dev)
 
 ## Common links
@@ -34,17 +34,17 @@ Native companion apps for Windows are also planned; the Gateway is recommended v
 - Install guide: [Getting Started](/start/getting-started)
 - Gateway runbook: [Gateway](/gateway)
 - Gateway configuration: [Configuration](/gateway/configuration)
-- Service status: `pigbot gateway status`
+- Service status: `moltbot gateway status`
 
 ## Gateway service install (CLI)
 
 Use one of these (all supported):
 
-- Wizard (recommended): `pigbot onboard --install-daemon`
-- Direct: `pigbot gateway install`
-- Configure flow: `pigbot configure` → select **Gateway service**
-- Repair/migrate: `pigbot doctor` (offers to install or fix the service)
+- Wizard (recommended): `moltbot onboard --install-daemon`
+- Direct: `moltbot gateway install`
+- Configure flow: `moltbot configure` → select **Gateway service**
+- Repair/migrate: `moltbot doctor` (offers to install or fix the service)
 
 The service target depends on OS:
-- macOS: LaunchAgent (`com.pigbot.gateway` or `com.pigbot.<profile>`)
-- Linux/WSL2: systemd user service (`pigbot-gateway[-<profile>].service`)
+- macOS: LaunchAgent (`bot.molt.gateway` or `bot.molt.<profile>`; legacy `com.clawdbot.*`)
+- Linux/WSL2: systemd user service (`moltbot-gateway[-<profile>].service`)

package/docs/platforms/ios.md

@@ -20,7 +20,7 @@ Availability: internal preview. The iOS app is not publicly distributed yet.
 - Gateway running on another device (macOS, Linux, or Windows via WSL2).
 - Network path:
   - Same LAN via Bonjour, **or**
-  - Tailnet via unicast DNS-SD (`pigbot.internal.`), **or**
+  - Tailnet via unicast DNS-SD (`moltbot.internal.`), **or**
   - Manual host/port (fallback).
 
 ## Quick start (pair + connect)
@@ -28,7 +28,7 @@ Availability: internal preview. The iOS app is not publicly distributed yet.
 1) Start the Gateway:
 
 ```bash
-pigbot gateway --port 18789
+moltbot gateway --port 18789
 ```
 
 2) In the iOS app, open Settings and pick a discovered gateway (or enable Manual Host and enter host/port).
@@ -36,26 +36,26 @@ pigbot gateway --port 18789
 3) Approve the pairing request on the gateway host:
 
 ```bash
-pigbot nodes pending
-pigbot nodes approve <requestId>
+moltbot nodes pending
+moltbot nodes approve <requestId>
 ```
 
 4) Verify connection:
 
 ```bash
-pigbot nodes status
-pigbot gateway call node.list --params "{}"
+moltbot nodes status
+moltbot gateway call node.list --params "{}"
 ```
 
 ## Discovery paths
 
 ### Bonjour (LAN)
 
-The Gateway advertises `_pigbot._tcp` on `local.`. The iOS app lists these automatically.
+The Gateway advertises `_moltbot._tcp` on `local.`. The iOS app lists these automatically.
 
 ### Tailnet (cross-network)
 
-If mDNS is blocked, use a unicast DNS-SD zone (recommended domain: `pigbot.internal.`) and Tailscale split DNS.
+If mDNS is blocked, use a unicast DNS-SD zone (recommended domain: `moltbot.internal.`) and Tailscale split DNS.
 See [Bonjour](/gateway/bonjour) for the CoreDNS example.
 
 ### Manual host/port
@@ -67,22 +67,22 @@ In Settings, enable **Manual Host** and enter the gateway host + port (default `
 The iOS node renders a WKWebView canvas. Use `node.invoke` to drive it:
 
 ```bash
-pigbot nodes invoke --node "iOS Node" --command canvas.navigate --params '{"url":"http://<gateway-host>:18793/__pigbot__/canvas/"}'
+moltbot nodes invoke --node "iOS Node" --command canvas.navigate --params '{"url":"http://<gateway-host>:18793/__moltbot__/canvas/"}'
 ```
 
 Notes:
-- The Gateway canvas host serves `/__pigbot__/canvas/` and `/__pigbot__/a2ui/`.
+- The Gateway canvas host serves `/__moltbot__/canvas/` and `/__moltbot__/a2ui/`.
 - The iOS node auto-navigates to A2UI on connect when a canvas host URL is advertised.
 - Return to the built-in scaffold with `canvas.navigate` and `{"url":""}`.
 
 ### Canvas eval / snapshot
 
 ```bash
-pigbot nodes invoke --node "iOS Node" --command canvas.eval --params '{"javaScript":"(() => { const {ctx} = window.__pigbot; ctx.clearRect(0,0,innerWidth,innerHeight); ctx.lineWidth=6; ctx.strokeStyle=\"#ff2d55\"; ctx.beginPath(); ctx.moveTo(40,40); ctx.lineTo(innerWidth-40, innerHeight-40); ctx.stroke(); return \"ok\"; })()"}'
+moltbot nodes invoke --node "iOS Node" --command canvas.eval --params '{"javaScript":"(() => { const {ctx} = window.__moltbot; ctx.clearRect(0,0,innerWidth,innerHeight); ctx.lineWidth=6; ctx.strokeStyle=\"#ff2d55\"; ctx.beginPath(); ctx.moveTo(40,40); ctx.lineTo(innerWidth-40, innerHeight-40); ctx.stroke(); return \"ok\"; })()"}'
 ```
 
 ```bash
-pigbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"maxWidth":900,"format":"jpeg"}'
+moltbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"maxWidth":900,"format":"jpeg"}'
 ```
 
 ## Voice wake + talk mode
@@ -94,7 +94,7 @@ pigbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"maxW
 
 - `NODE_BACKGROUND_UNAVAILABLE`: bring the iOS app to the foreground (canvas/camera/screen commands require it).
 - `A2UI_HOST_NOT_CONFIGURED`: the Gateway did not advertise a canvas host URL; check `canvasHost` in [Gateway configuration](/gateway/configuration).
-- Pairing prompt never appears: run `pigbot nodes pending` and approve manually.
+- Pairing prompt never appears: run `moltbot nodes pending` and approve manually.
 - Reconnect fails after reinstall: the Keychain pairing token was cleared; re-pair the node.
 
 ## Related docs

package/docs/platforms/linux.md

@@ -14,8 +14,8 @@ Native Linux companion apps are planned. Contributions are welcome if you want t
 ## Beginner quick path (VPS)
 
 1) Install Node 22+  
-2) `npm i -g pigbot@latest`  
-3) `pigbot onboard --install-daemon`  
+2) `npm i -g moltbot@latest`  
+3) `moltbot onboard --install-daemon`  
 4) From your laptop: `ssh -N -L 18789:127.0.0.1:18789 <user>@<host>`  
 5) Open `http://127.0.0.1:18789/` and paste your token
 
@@ -35,19 +35,19 @@ Step-by-step VPS guide: [exe.dev](/platforms/exe-dev)
 Use one of these:
 
 ```
-pigbot onboard --install-daemon
+moltbot onboard --install-daemon
 ```
 
 Or:
 
 ```
-pigbot gateway install
+moltbot gateway install
 ```
 
 Or:
 
 ```
-pigbot configure
+moltbot configure
 ```
 
 Select **Gateway service** when prompted.
@@ -55,26 +55,26 @@ Select **Gateway service** when prompted.
 Repair/migrate:
 
 ```
-pigbot doctor
+moltbot doctor
 ```
 
 ## System control (systemd user unit)
-Pigbot installs a systemd **user** service by default. Use a **system**
+Moltbot installs a systemd **user** service by default. Use a **system**
 service for shared or always-on servers. The full unit example and guidance
 live in the [Gateway runbook](/gateway).
 
 Minimal setup:
 
-Create `~/.config/systemd/user/pigbot-gateway[-<profile>].service`:
+Create `~/.config/systemd/user/moltbot-gateway[-<profile>].service`:
 
 ```
 [Unit]
-Description=Pigbot Gateway (profile: <profile>, v<version>)
+Description=Moltbot Gateway (profile: <profile>, v<version>)
 After=network-online.target
 Wants=network-online.target
 
 [Service]
-ExecStart=/usr/local/bin/pigbot gateway --port 18789
+ExecStart=/usr/local/bin/moltbot gateway --port 18789
 Restart=always
 RestartSec=5
 
@@ -85,5 +85,5 @@ WantedBy=default.target
 Enable it:
 
 ```
-systemctl --user enable --now pigbot-gateway[-<profile>].service
+systemctl --user enable --now moltbot-gateway[-<profile>].service
 ```

package/docs/platforms/mac/bundled-gateway.md

@@ -1,24 +1,24 @@
 ---
 summary: "Gateway runtime on macOS (external launchd service)"
 read_when:
-  - Packaging Pigbot.app
+  - Packaging Moltbot.app
   - Debugging the macOS gateway launchd service
   - Installing the gateway CLI for macOS
 ---
 
 # Gateway on macOS (external launchd)
 
-Pigbot.app no longer bundles Node/Bun or the Gateway runtime. The macOS app
-expects an **external** `pigbot` CLI install, does not spawn the Gateway as a
+Moltbot.app no longer bundles Node/Bun or the Gateway runtime. The macOS app
+expects an **external** `moltbot` CLI install, does not spawn the Gateway as a
 child process, and manages a per‑user launchd service to keep the Gateway
 running (or attaches to an existing local Gateway if one is already running).
 
 ## Install the CLI (required for local mode)
 
-You need Node 22+ on the Mac, then install `pigbot` globally:
+You need Node 22+ on the Mac, then install `moltbot` globally:
 
 ```bash
-npm install -g pigbot@<version>
+npm install -g moltbot@<version>
 ```
 
 The macOS app’s **Install CLI** button runs the same flow via npm/pnpm (bun not recommended for Gateway runtime).
@@ -26,24 +26,24 @@ The macOS app’s **Install CLI** button runs the same flow via npm/pnpm (bun no
 ## Launchd (Gateway as LaunchAgent)
 
 Label:
-- `com.pigbot.gateway` (or `com.pigbot.<profile>`)
+- `bot.molt.gateway` (or `bot.molt.<profile>`; legacy `com.clawdbot.*` may remain)
 
 Plist location (per‑user):
-- `~/Library/LaunchAgents/com.pigbot.gateway.plist`
-  (or `~/Library/LaunchAgents/com.pigbot.<profile>.plist`)
+- `~/Library/LaunchAgents/bot.molt.gateway.plist`
+  (or `~/Library/LaunchAgents/bot.molt.<profile>.plist`)
 
 Manager:
 - The macOS app owns LaunchAgent install/update in Local mode.
-- The CLI can also install it: `pigbot gateway install`.
+- The CLI can also install it: `moltbot gateway install`.
 
 Behavior:
-- “Pigbot Active” enables/disables the LaunchAgent.
+- “Moltbot Active” enables/disables the LaunchAgent.
 - App quit does **not** stop the gateway (launchd keeps it alive).
 - If a Gateway is already running on the configured port, the app attaches to
   it instead of starting a new one.
 
 Logging:
-- launchd stdout/err: `/tmp/pigbot/pigbot-gateway.log`
+- launchd stdout/err: `/tmp/moltbot/moltbot-gateway.log`
 
 ## Version compatibility
 
@@ -53,15 +53,15 @@ incompatible, update the global CLI to match the app version.
 ## Smoke check
 
 ```bash
-pigbot --version
+moltbot --version
 
-PIGBOT_SKIP_CHANNELS=1 \
-PIGBOT_SKIP_CANVAS_HOST=1 \
-pigbot gateway --port 18999 --bind loopback
+CLAWDBOT_SKIP_CHANNELS=1 \
+CLAWDBOT_SKIP_CANVAS_HOST=1 \
+moltbot gateway --port 18999 --bind loopback
 ```
 
 Then:
 
 ```bash
-pigbot gateway call health --url ws://127.0.0.1:18999 --timeout 3000
+moltbot gateway call health --url ws://127.0.0.1:18999 --timeout 3000
 ```

package/docs/platforms/mac/canvas.md

@@ -15,16 +15,16 @@ UI surfaces.
 
 Canvas state is stored under Application Support:
 
-- `~/Library/Application Support/Pigbot/canvas/<session>/...`
+- `~/Library/Application Support/Moltbot/canvas/<session>/...`
 
 The Canvas panel serves those files via a **custom URL scheme**:
 
-- `pigbot-canvas://<session>/<path>`
+- `moltbot-canvas://<session>/<path>`
 
 Examples:
-- `pigbot-canvas://main/` → `<canvasRoot>/main/index.html`
-- `pigbot-canvas://main/assets/app.css` → `<canvasRoot>/main/assets/app.css`
-- `pigbot-canvas://main/widgets/todo/` → `<canvasRoot>/main/widgets/todo/index.html`
+- `moltbot-canvas://main/` → `<canvasRoot>/main/index.html`
+- `moltbot-canvas://main/assets/app.css` → `<canvasRoot>/main/assets/app.css`
+- `moltbot-canvas://main/widgets/todo/` → `<canvasRoot>/main/widgets/todo/index.html`
 
 If no `index.html` exists at the root, the app shows a **built‑in scaffold page**.
 
@@ -50,10 +50,10 @@ Canvas is exposed via the **Gateway WebSocket**, so the agent can:
 CLI examples:
 
 ```bash
-pigbot nodes canvas present --node <id>
-pigbot nodes canvas navigate --node <id> --url "/"
-pigbot nodes canvas eval --node <id> --js "document.title"
-pigbot nodes canvas snapshot --node <id>
+moltbot nodes canvas present --node <id>
+moltbot nodes canvas navigate --node <id> --url "/"
+moltbot nodes canvas eval --node <id> --js "document.title"
+moltbot nodes canvas snapshot --node <id>
 ```
 
 Notes:
@@ -69,7 +69,7 @@ A2UI host page on first open.
 Default A2UI host URL:
 
 ```
-http://<gateway-host>:18793/__pigbot__/a2ui/
+http://<gateway-host>:18793/__moltbot__/a2ui/
 ```
 
 ### A2UI commands (v0.8)
@@ -91,25 +91,25 @@ cat > /tmp/a2ui-v0.8.jsonl <<'EOFA2'
 {"beginRendering":{"surfaceId":"main","root":"root"}}
 EOFA2
 
-pigbot nodes canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node <id>
+moltbot nodes canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node <id>
 ```
 
 Quick smoke:
 
 ```bash
-pigbot nodes canvas a2ui push --node <id> --text "Hello from A2UI"
+moltbot nodes canvas a2ui push --node <id> --text "Hello from A2UI"
 ```
 
 ## Triggering agent runs from Canvas
 
 Canvas can trigger new agent runs via deep links:
 
-- `pigbot://agent?...`
+- `moltbot://agent?...`
 
 Example (in JS):
 
 ```js
-window.location.href = "pigbot://agent?message=Review%20this%20design";
+window.location.href = "moltbot://agent?message=Review%20this%20design";
 ```
 
 The app prompts for confirmation unless a valid key is provided.

package/docs/platforms/mac/child-process.md

@@ -8,7 +8,7 @@ read_when:
 The macOS app **manages the Gateway via launchd** by default and does not spawn
 the Gateway as a child process. It first tries to attach to an already‑running
 Gateway on the configured port; if none is reachable, it enables the launchd
-service via the external `pigbot` CLI (no embedded runtime). This gives you
+service via the external `moltbot` CLI (no embedded runtime). This gives you
 reliable auto‑start at login and restart on crashes.
 
 Child‑process mode (Gateway spawned directly by the app) is **not in use** today.
@@ -16,8 +16,8 @@ If you need tighter coupling to the UI, run the Gateway manually in a terminal.
 
 ## Default behavior (launchd)
 
-- The app installs a per‑user LaunchAgent labeled `com.pigbot.gateway`
-  (or `com.pigbot.<profile>` when using `--profile`/`PIGBOT_PROFILE`).
+- The app installs a per‑user LaunchAgent labeled `bot.molt.gateway`
+  (or `bot.molt.<profile>` when using `--profile`/`CLAWDBOT_PROFILE`; legacy `com.clawdbot.*` is supported).
 - When Local mode is enabled, the app ensures the LaunchAgent is loaded and
   starts the Gateway if needed.
 - Logs are written to the launchd gateway log path (visible in Debug Settings).
@@ -25,30 +25,30 @@ If you need tighter coupling to the UI, run the Gateway manually in a terminal.
 Common commands:
 
 ```bash
-launchctl kickstart -k gui/$UID/com.pigbot.gateway
-launchctl bootout gui/$UID/com.pigbot.gateway
+launchctl kickstart -k gui/$UID/bot.molt.gateway
+launchctl bootout gui/$UID/bot.molt.gateway
 ```
 
-Replace the label with `com.pigbot.<profile>` when running a named profile.
+Replace the label with `bot.molt.<profile>` when running a named profile.
 
 ## Unsigned dev builds
 
 `scripts/restart-mac.sh --no-sign` is for fast local builds when you don’t have
 signing keys. To prevent launchd from pointing at an unsigned relay binary, it:
 
-- Writes `~/.pigbot/disable-launchagent`.
+- Writes `~/.clawdbot/disable-launchagent`.
 
 Signed runs of `scripts/restart-mac.sh` clear this override if the marker is
 present. To reset manually:
 
 ```bash
-rm ~/.pigbot/disable-launchagent
+rm ~/.clawdbot/disable-launchagent
 ```
 
 ## Attach-only mode
 
 To force the macOS app to **never install or manage launchd**, launch it with
-`--attach-only` (or `--no-launchd`). This sets `~/.pigbot/disable-launchagent`,
+`--attach-only` (or `--no-launchd`). This sets `~/.clawdbot/disable-launchagent`,
 so the app only attaches to an already running Gateway. You can toggle the same
 behavior in Debug Settings.
 

package/docs/platforms/mac/dev-setup.md

@@ -1,11 +1,11 @@
 ---
-summary: "Setup guide for developers working on the Pigbot macOS app"
+summary: "Setup guide for developers working on the Moltbot macOS app"
 read_when:
   - Setting up the macOS development environment
 ---
 # macOS Developer Setup
 
-This guide covers the necessary steps to build and run the Pigbot macOS application from source.
+This guide covers the necessary steps to build and run the Moltbot macOS application from source.
 
 ## Prerequisites
 
@@ -24,7 +24,7 @@ pnpm install
 
 ## 2. Build and Package the App
 
-To build the macOS app and package it into `dist/Pigbot.app`, run:
+To build the macOS app and package it into `dist/Moltbot.app`, run:
 
 ```bash
 ./scripts/package-mac-app.sh
@@ -33,22 +33,22 @@ To build the macOS app and package it into `dist/Pigbot.app`, run:
 If you don't have an Apple Developer ID certificate, the script will automatically use **ad-hoc signing** (`-`). 
 
 For dev run modes, signing flags, and Team ID troubleshooting, see the macOS app README:
-https://github.com/pigbot/pigbot/blob/main/apps/macos/README.md
+https://github.com/moltbot/moltbot/blob/main/apps/macos/README.md
 
 > **Note**: Ad-hoc signed apps may trigger security prompts. If the app crashes immediately with "Abort trap 6", see the [Troubleshooting](#troubleshooting) section.
 
 ## 3. Install the CLI
 
-The macOS app expects a global `pigbot` CLI install to manage background tasks.
+The macOS app expects a global `moltbot` CLI install to manage background tasks.
 
 **To install it (recommended):**
-1.  Open the Pigbot app.
+1.  Open the Moltbot app.
 2.  Go to the **General** settings tab.
 3.  Click **"Install CLI"**.
 
 Alternatively, install it manually:
 ```bash
-npm install -g pigbot@<version>
+npm install -g moltbot@<version>
 ```
 
 ## Troubleshooting
@@ -74,16 +74,16 @@ If the app crashes when you try to allow **Speech Recognition** or **Microphone*
 **Fix:**
 1. Reset the TCC permissions:
    ```bash
-   tccutil reset All com.pigbot.mac.debug
+   tccutil reset All bot.molt.mac.debug
    ```
-2. If that fails, change the `BUNDLE_ID` temporarily in [`scripts/package-mac-app.sh`](https://github.com/pigbot/pigbot/blob/main/scripts/package-mac-app.sh) to force a "clean slate" from macOS.
+2. If that fails, change the `BUNDLE_ID` temporarily in [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) to force a "clean slate" from macOS.
 
 ### Gateway "Starting..." indefinitely
 If the gateway status stays on "Starting...", check if a zombie process is holding the port:
 
 ```bash
-pigbot gateway status
-pigbot gateway stop
+moltbot gateway status
+moltbot gateway stop
 
 # If you’re not using a LaunchAgent (dev mode / manual runs), find the listener:
 lsof -nP -iTCP:18789 -sTCP:LISTEN

package/docs/platforms/mac/health.md

@@ -21,8 +21,8 @@ How to see whether the linked channel is healthy from the menu bar app.
 - **Channels tab** surfaces channel status + controls for WhatsApp/Telegram (login QR, logout, probe, last disconnect/error).
 
 ## How the probe works
-- App runs `pigbot health --json` via `ShellExecutor` every ~60s and on demand. The probe loads creds and reports status without sending messages.
+- App runs `moltbot health --json` via `ShellExecutor` every ~60s and on demand. The probe loads creds and reports status without sending messages.
 - Cache the last good snapshot and the last error separately to avoid flicker; show the timestamp of each.
 
 ## When in doubt
-- You can still use the CLI flow in [Gateway health](/gateway/health) (`pigbot status`, `pigbot status --deep`, `pigbot health --json`) and tail `/tmp/pigbot/pigbot-*.log` for `web-heartbeat` / `web-reconnect`.
+- You can still use the CLI flow in [Gateway health](/gateway/health) (`moltbot status`, `moltbot status --deep`, `moltbot health --json`) and tail `/tmp/moltbot/moltbot-*.log` for `web-heartbeat` / `web-reconnect`.

package/docs/platforms/mac/icon.md

@@ -1,5 +1,5 @@
 ---
-summary: "Menu bar icon states and animations for Pigbot on macOS"
+summary: "Menu bar icon states and animations for Moltbot on macOS"
 read_when:
   - Changing menu bar icon behavior
 ---

package/docs/platforms/mac/logging.md

@@ -1,5 +1,5 @@
 ---
-summary: "Pigbot logging: rolling diagnostics file log + unified log privacy flags"
+summary: "Moltbot logging: rolling diagnostics file log + unified log privacy flags"
 read_when:
   - Capturing macOS logs or investigating private data logging
   - Debugging voice wake/session lifecycle issues
@@ -7,11 +7,11 @@ read_when:
 # Logging (macOS)
 
 ## Rolling diagnostics file log (Debug pane)
-Pigbot routes macOS app logs through swift-log (unified logging by default) and can write a local, rotating file log to disk when you need a durable capture.
+Moltbot routes macOS app logs through swift-log (unified logging by default) and can write a local, rotating file log to disk when you need a durable capture.
 
 - Verbosity: **Debug pane → Logs → App logging → Verbosity**
 - Enable: **Debug pane → Logs → App logging → “Write rolling diagnostics log (JSONL)”**
-- Location: `~/Library/Logs/Pigbot/diagnostics.jsonl` (rotates automatically; old files are suffixed with `.1`, `.2`, …)
+- Location: `~/Library/Logs/Moltbot/diagnostics.jsonl` (rotates automatically; old files are suffixed with `.1`, `.2`, …)
 - Clear: **Debug pane → Logs → App logging → “Clear”**
 
 Notes:
@@ -22,11 +22,11 @@ Notes:
 
 Unified logging redacts most payloads unless a subsystem opts into `privacy -off`. Per Peter's write-up on macOS [logging privacy shenanigans](https://steipete.me/posts/2025/logging-privacy-shenanigans) (2025) this is controlled by a plist in `/Library/Preferences/Logging/Subsystems/` keyed by the subsystem name. Only new log entries pick up the flag, so enable it before reproducing an issue.
 
-## Enable for Pigbot (`com.pigbot`)
+## Enable for Moltbot (`bot.molt`)
 - Write the plist to a temp file first, then install it atomically as root:
 
 ```bash
-cat <<'EOF' >/tmp/com.pigbot.plist
+cat <<'EOF' >/tmp/bot.molt.plist
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
@@ -39,13 +39,13 @@ cat <<'EOF' >/tmp/com.pigbot.plist
 </dict>
 </plist>
 EOF
-sudo install -m 644 -o root -g wheel /tmp/com.pigbot.plist /Library/Preferences/Logging/Subsystems/com.pigbot.plist
+sudo install -m 644 -o root -g wheel /tmp/bot.molt.plist /Library/Preferences/Logging/Subsystems/bot.molt.plist
 ```
 
 - No reboot is required; logd notices the file quickly, but only new log lines will include private payloads.
 - View the richer output with the existing helper, e.g. `./scripts/clawlog.sh --category WebChat --last 5m`.
 
 ## Disable after debugging
-- Remove the override: `sudo rm /Library/Preferences/Logging/Subsystems/com.pigbot.plist`.
+- Remove the override: `sudo rm /Library/Preferences/Logging/Subsystems/bot.molt.plist`.
 - Optionally run `sudo log config --reload` to force logd to drop the override immediately.
 - Remember this surface can include phone numbers and message bodies; keep the plist in place only while you actively need the extra detail.

package/docs/platforms/mac/menu-bar.md

@@ -40,7 +40,7 @@ read_when:
 
 ## Status row text (menu)
 - While work is active: `<Session role> · <activity label>`
-  - Examples: `Main · exec: pnpm test`, `Other · read: apps/macos/Sources/Pigbot/AppState.swift`.
+  - Examples: `Main · exec: pnpm test`, `Other · read: apps/macos/Sources/Moltbot/AppState.swift`.
 - When idle: falls back to the health summary.
 
 ## Event ingestion

package/docs/platforms/mac/peekaboo.md

@@ -1,28 +1,28 @@
 ---
 summary: "PeekabooBridge integration for macOS UI automation"
 read_when:
-  - Hosting PeekabooBridge in Pigbot.app
+  - Hosting PeekabooBridge in Moltbot.app
   - Integrating Peekaboo via Swift Package Manager
   - Changing PeekabooBridge protocol/paths
 ---
 # Peekaboo Bridge (macOS UI automation)
 
-Pigbot can host **PeekabooBridge** as a local, permission‑aware UI automation
+Moltbot can host **PeekabooBridge** as a local, permission‑aware UI automation
 broker. This lets the `peekaboo` CLI drive UI automation while reusing the
 macOS app’s TCC permissions.
 
 ## What this is (and isn’t)
 
-- **Host**: Pigbot.app can act as a PeekabooBridge host.
-- **Client**: use the `peekaboo` CLI (no separate `pigbot ui ...` surface).
-- **UI**: visual overlays stay in Peekaboo.app; Pigbot is a thin broker host.
+- **Host**: Moltbot.app can act as a PeekabooBridge host.
+- **Client**: use the `peekaboo` CLI (no separate `moltbot ui ...` surface).
+- **UI**: visual overlays stay in Peekaboo.app; Moltbot is a thin broker host.
 
 ## Enable the bridge
 
 In the macOS app:
 - Settings → **Enable Peekaboo Bridge**
 
-When enabled, Pigbot starts a local UNIX socket server. If disabled, the host
+When enabled, Moltbot starts a local UNIX socket server. If disabled, the host
 is stopped and `peekaboo` will fall back to other available hosts.
 
 ## Client discovery order
@@ -31,7 +31,7 @@ Peekaboo clients typically try hosts in this order:
 
 1. Peekaboo.app (full UX)
 2. Claude.app (if installed)
-3. Pigbot.app (thin broker)
+3. Moltbot.app (thin broker)
 
 Use `peekaboo bridge status --verbose` to see which host is active and which
 socket path is in use. You can override with:
@@ -43,7 +43,7 @@ export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock
 ## Security & permissions
 
 - The bridge validates **caller code signatures**; an allowlist of TeamIDs is
-  enforced (Peekaboo host TeamID + Pigbot app TeamID).
+  enforced (Peekaboo host TeamID + Moltbot app TeamID).
 - Requests time out after ~10 seconds.
 - If required permissions are missing, the bridge returns a clear error message
   rather than launching System Settings.
@@ -58,5 +58,5 @@ If you need longer retention, re‑capture from the client.
 - If `peekaboo` reports “bridge client is not authorized”, ensure the client is
   properly signed or run the host with `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1`
   in **debug** mode only.
-- If no hosts are found, open one of the host apps (Peekaboo.app or Pigbot.app)
+- If no hosts are found, open one of the host apps (Peekaboo.app or Moltbot.app)
   and confirm permissions are granted.

package/docs/platforms/mac/permissions.md

@@ -12,7 +12,7 @@ app's code signature, bundle identifier, and on-disk path. If any of those chang
 macOS treats the app as new and may drop or hide prompts.
 
 ## Requirements for stable permissions
-- Same path: run the app from a fixed location (for Pigbot, `dist/Pigbot.app`).
+- Same path: run the app from a fixed location (for Moltbot, `dist/Moltbot.app`).
 - Same bundle identifier: changing the bundle ID creates a new permission identity.
 - Signed app: unsigned or ad-hoc signed builds do not persist permissions.
 - Consistent signature: use a real Apple Development or Developer ID certificate
@@ -31,8 +31,8 @@ grants, and prompts can disappear entirely until the stale entries are cleared.
 Example resets (replace bundle ID as needed):
 
 ```bash
-sudo tccutil reset Accessibility com.pigbot.mac
-sudo tccutil reset ScreenCapture com.pigbot.mac
+sudo tccutil reset Accessibility bot.molt.mac
+sudo tccutil reset ScreenCapture bot.molt.mac
 sudo tccutil reset AppleEvents
 ```