@gguf/pigbot 0.0.1 → 0.0.3

package/docs/platforms/mac/release.md

@@ -1,11 +1,11 @@
 ---
-summary: "Pigbot macOS release checklist (Sparkle feed, packaging, signing)"
+summary: "Moltbot macOS release checklist (Sparkle feed, packaging, signing)"
 read_when:
-  - Cutting or validating a Pigbot macOS release
+  - Cutting or validating a Moltbot macOS release
   - Updating the Sparkle appcast or feed assets
 ---
 
-# Pigbot macOS release (Sparkle)
+# Moltbot macOS release (Sparkle)
 
 This app now ships Sparkle auto-updates. Release builds must be Developer ID–signed, zipped, and published with a signed appcast entry.
 
@@ -13,10 +13,10 @@ This app now ships Sparkle auto-updates. Release builds must be Developer ID–s
 - Developer ID Application cert installed (example: `Developer ID Application: <Developer Name> (<TEAMID>)`).
 - Sparkle private key path set in the environment as `SPARKLE_PRIVATE_KEY_FILE` (path to your Sparkle ed25519 private key; public key baked into Info.plist). If it is missing, check `~/.profile`.
 - Notary credentials (keychain profile or API key) for `xcrun notarytool` if you want Gatekeeper-safe DMG/zip distribution.
-  - We use a Keychain profile named `pigbot-notary`, created from App Store Connect API key env vars in your shell profile:
+  - We use a Keychain profile named `moltbot-notary`, created from App Store Connect API key env vars in your shell profile:
     - `APP_STORE_CONNECT_API_KEY_P8`, `APP_STORE_CONNECT_KEY_ID`, `APP_STORE_CONNECT_ISSUER_ID`
-    - `echo "$APP_STORE_CONNECT_API_KEY_P8" | sed 's/\\n/\n/g' > /tmp/pigbot-notary.p8`
-    - `xcrun notarytool store-credentials "pigbot-notary" --key /tmp/pigbot-notary.p8 --key-id "$APP_STORE_CONNECT_KEY_ID" --issuer "$APP_STORE_CONNECT_ISSUER_ID"`
+    - `echo "$APP_STORE_CONNECT_API_KEY_P8" | sed 's/\\n/\n/g' > /tmp/moltbot-notary.p8`
+    - `xcrun notarytool store-credentials "moltbot-notary" --key /tmp/moltbot-notary.p8 --key-id "$APP_STORE_CONNECT_KEY_ID" --issuer "$APP_STORE_CONNECT_ISSUER_ID"`
 - `pnpm` deps installed (`pnpm install --config.node-linker=hoisted`).
 - Sparkle tools are fetched automatically via SwiftPM at `apps/macos/.build/artifacts/sparkle/Sparkle/bin/` (`sign_update`, `generate_appcast`, etc.).
 
@@ -29,48 +29,48 @@ Notes:
 ```bash
 # From repo root; set release IDs so Sparkle feed is enabled.
 # APP_BUILD must be numeric + monotonic for Sparkle compare.
-BUNDLE_ID=com.pigbot.mac \
-APP_VERSION=2026.1.24 \
+BUNDLE_ID=bot.molt.mac \
+APP_VERSION=2026.1.26 \
 APP_BUILD="$(git rev-list --count HEAD)" \
 BUILD_CONFIG=release \
 SIGN_IDENTITY="Developer ID Application: <Developer Name> (<TEAMID>)" \
 scripts/package-mac-app.sh
 
 # Zip for distribution (includes resource forks for Sparkle delta support)
-ditto -c -k --sequesterRsrc --keepParent dist/Pigbot.app dist/Pigbot-2026.1.24.zip
+ditto -c -k --sequesterRsrc --keepParent dist/Moltbot.app dist/Moltbot-2026.1.26.zip
 
 # Optional: also build a styled DMG for humans (drag to /Applications)
-scripts/create-dmg.sh dist/Pigbot.app dist/Pigbot-2026.1.24.dmg
+scripts/create-dmg.sh dist/Moltbot.app dist/Moltbot-2026.1.26.dmg
 
 # Recommended: build + notarize/staple zip + DMG
 # First, create a keychain profile once:
-#   xcrun notarytool store-credentials "pigbot-notary" \
+#   xcrun notarytool store-credentials "moltbot-notary" \
 #     --apple-id "<apple-id>" --team-id "<team-id>" --password "<app-specific-password>"
-NOTARIZE=1 NOTARYTOOL_PROFILE=pigbot-notary \
-BUNDLE_ID=com.pigbot.mac \
-APP_VERSION=2026.1.24 \
+NOTARIZE=1 NOTARYTOOL_PROFILE=moltbot-notary \
+BUNDLE_ID=bot.molt.mac \
+APP_VERSION=2026.1.26 \
 APP_BUILD="$(git rev-list --count HEAD)" \
 BUILD_CONFIG=release \
 SIGN_IDENTITY="Developer ID Application: <Developer Name> (<TEAMID>)" \
 scripts/package-mac-dist.sh
 
 # Optional: ship dSYM alongside the release
-ditto -c -k --keepParent apps/macos/.build/release/Pigbot.app.dSYM dist/Pigbot-2026.1.24.dSYM.zip
+ditto -c -k --keepParent apps/macos/.build/release/Moltbot.app.dSYM dist/Moltbot-2026.1.26.dSYM.zip
 ```
 
 ## Appcast entry
 Use the release note generator so Sparkle renders formatted HTML notes:
 ```bash
-SPARKLE_PRIVATE_KEY_FILE=/path/to/ed25519-private-key scripts/make_appcast.sh dist/Pigbot-2026.1.24.zip https://raw.githubusercontent.com/pigbot/pigbot/main/appcast.xml
+SPARKLE_PRIVATE_KEY_FILE=/path/to/ed25519-private-key scripts/make_appcast.sh dist/Moltbot-2026.1.26.zip https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml
 ```
-Generates HTML release notes from `CHANGELOG.md` (via [`scripts/changelog-to-html.sh`](https://github.com/pigbot/pigbot/blob/main/scripts/changelog-to-html.sh)) and embeds them in the appcast entry.
+Generates HTML release notes from `CHANGELOG.md` (via [`scripts/changelog-to-html.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/changelog-to-html.sh)) and embeds them in the appcast entry.
 Commit the updated `appcast.xml` alongside the release assets (zip + dSYM) when publishing.
 
 ## Publish & verify
-- Upload `Pigbot-2026.1.24.zip` (and `Pigbot-2026.1.24.dSYM.zip`) to the GitHub release for tag `v2026.1.24`.
-- Ensure the raw appcast URL matches the baked feed: `https://raw.githubusercontent.com/pigbot/pigbot/main/appcast.xml`.
+- Upload `Moltbot-2026.1.26.zip` (and `Moltbot-2026.1.26.dSYM.zip`) to the GitHub release for tag `v2026.1.26`.
+- Ensure the raw appcast URL matches the baked feed: `https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml`.
 - Sanity checks:
-  - `curl -I https://raw.githubusercontent.com/pigbot/pigbot/main/appcast.xml` returns 200.
+  - `curl -I https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml` returns 200.
   - `curl -I <enclosure url>` returns 200 after assets upload.
   - On a previous public build, run “Check for Updates…” from the About tab and verify Sparkle installs the new build cleanly.
 

package/docs/platforms/mac/remote.md

@@ -1,16 +1,16 @@
 ---
-summary: "macOS app flow for controlling a remote Pigbot gateway over SSH"
+summary: "macOS app flow for controlling a remote Moltbot gateway over SSH"
 read_when:
   - Setting up or debugging remote mac control
 ---
-# Remote Pigbot (macOS ⇄ remote host)
+# Remote Moltbot (macOS ⇄ remote host)
 
 
-This flow lets the macOS app act as a full remote control for a Pigbot gateway running on another host (desktop/server). It’s the app’s **Remote over SSH** (remote run) feature. All features—health checks, Voice Wake forwarding, and Web Chat—reuse the same remote SSH configuration from *Settings → General*.
+This flow lets the macOS app act as a full remote control for a Moltbot gateway running on another host (desktop/server). It’s the app’s **Remote over SSH** (remote run) feature. All features—health checks, Voice Wake forwarding, and Web Chat—reuse the same remote SSH configuration from *Settings → General*.
 
 ## Modes
 - **Local (this Mac)**: Everything runs on the laptop. No SSH involved.
-- **Remote over SSH (default)**: Pigbot commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key and a local port-forward.
+- **Remote over SSH (default)**: Moltbot commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key and a local port-forward.
 - **Remote direct (ws/wss)**: No SSH tunnel. The mac app connects to the gateway URL directly (for example, via Tailscale Serve or a public HTTPS reverse proxy).
 
 ## Remote transports
@@ -19,21 +19,21 @@ Remote mode supports two transports:
 - **Direct (ws/wss)**: Connects straight to the gateway URL. The gateway sees the real client IP.
 
 ## Prereqs on the remote host
-1) Install Node + pnpm and build/install the Pigbot CLI (`pnpm install && pnpm build && pnpm link --global`).
-2) Ensure `pigbot` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed).
+1) Install Node + pnpm and build/install the Moltbot CLI (`pnpm install && pnpm build && pnpm link --global`).
+2) Ensure `moltbot` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed).
 3) Open SSH with key auth. We recommend **Tailscale** IPs for stable reachability off-LAN.
 
 ## macOS app setup
 1) Open *Settings → General*.
-2) Under **Pigbot runs**, pick **Remote over SSH** and set:
+2) Under **Moltbot runs**, pick **Remote over SSH** and set:
    - **Transport**: **SSH tunnel** or **Direct (ws/wss)**.
    - **SSH target**: `user@host` (optional `:port`).
      - If the gateway is on the same LAN and advertises Bonjour, pick it from the discovered list to auto-fill this field.
    - **Gateway URL** (Direct only): `wss://gateway.example.ts.net` (or `ws://...` for local/LAN).
    - **Identity file** (advanced): path to your key.
    - **Project root** (advanced): remote checkout path used for commands.
-   - **CLI path** (advanced): optional path to a runnable `pigbot` entrypoint/binary (auto-filled when advertised).
-3) Hit **Test remote**. Success indicates the remote `pigbot status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely.
+   - **CLI path** (advanced): optional path to a runnable `moltbot` entrypoint/binary (auto-filled when advertised).
+3) Hit **Test remote**. Success indicates the remote `moltbot status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely.
 4) Health checks and Web Chat will now run through this SSH tunnel automatically.
 
 ## Web Chat
@@ -51,21 +51,21 @@ Remote mode supports two transports:
 - See [Security](/gateway/security) and [Tailscale](/gateway/tailscale).
 
 ## WhatsApp login flow (remote)
-- Run `pigbot channels login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone.
+- Run `moltbot channels login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone.
 - Re-run login on that host if auth expires. Health check will surface link problems.
 
 ## Troubleshooting
-- **exit 127 / not found**: `pigbot` isn’t on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`.
-- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`pigbot status --json`).
+- **exit 127 / not found**: `moltbot` isn’t on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`.
+- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`moltbot status --json`).
 - **Web Chat stuck**: confirm the gateway is running on the remote host and the forwarded port matches the gateway WS port; the UI requires a healthy WS connection.
 - **Node IP shows 127.0.0.1**: expected with the SSH tunnel. Switch **Transport** to **Direct (ws/wss)** if you want the gateway to see the real client IP.
 - **Voice Wake**: trigger phrases are forwarded automatically in remote mode; no separate forwarder is needed.
 
 ## Notification sounds
-Pick sounds per notification from scripts with `pigbot` and `node.invoke`, e.g.:
+Pick sounds per notification from scripts with `moltbot` and `node.invoke`, e.g.:
 
 ```bash
-pigbot nodes notify --node <id> --title "Ping" --body "Remote gateway ready" --sound Glass
+moltbot nodes notify --node <id> --title "Ping" --body "Remote gateway ready" --sound Glass
 ```
 
 There is no global “default sound” toggle in the app anymore; callers choose a sound (or none) per request.

package/docs/platforms/mac/signing.md

@@ -5,13 +5,13 @@ read_when:
 ---
 # mac signing (debug builds)
 
-This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/pigbot/pigbot/blob/main/scripts/package-mac-app.sh), which now:
+This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh), which now:
 
-- sets a stable debug bundle identifier: `com.pigbot.mac.debug`
+- sets a stable debug bundle identifier: `bot.molt.mac.debug`
 - writes the Info.plist with that bundle id (override via `BUNDLE_ID=...`)
-- calls [`scripts/codesign-mac-app.sh`](https://github.com/pigbot/pigbot/blob/main/scripts/codesign-mac-app.sh) to sign the main binary and app bundle so macOS treats each rebuild as the same signed bundle and keeps TCC permissions (notifications, accessibility, screen recording, mic, speech). For stable permissions, use a real signing identity; ad-hoc is opt-in and fragile (see [macOS permissions](/platforms/mac/permissions)).
+- calls [`scripts/codesign-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/codesign-mac-app.sh) to sign the main binary and app bundle so macOS treats each rebuild as the same signed bundle and keeps TCC permissions (notifications, accessibility, screen recording, mic, speech). For stable permissions, use a real signing identity; ad-hoc is opt-in and fragile (see [macOS permissions](/platforms/mac/permissions)).
 - uses `CODESIGN_TIMESTAMP=auto` by default; it enables trusted timestamps for Developer ID signatures. Set `CODESIGN_TIMESTAMP=off` to skip timestamping (offline debug builds).
-- inject build metadata into Info.plist: `PigbotBuildTimestamp` (UTC) and `PigbotGitCommit` (short hash) so the About pane can show build, git, and debug/release channel.
+- inject build metadata into Info.plist: `MoltbotBuildTimestamp` (UTC) and `MoltbotGitCommit` (short hash) so the About pane can show build, git, and debug/release channel.
 - **Packaging requires Node 22+**: the script runs TS builds and the Control UI build.
 - reads `SIGN_IDENTITY` from the environment. Add `export SIGN_IDENTITY="Apple Development: Your Name (TEAMID)"` (or your Developer ID Application cert) to your shell rc to always sign with your cert. Ad-hoc signing requires explicit opt-in via `ALLOW_ADHOC_SIGNING=1` or `SIGN_IDENTITY="-"` (not recommended for permission testing).
 - runs a Team ID audit after signing and fails if any Mach-O inside the app bundle is signed by a different Team ID. Set `SKIP_TEAM_ID_CHECK=1` to bypass.
@@ -33,11 +33,11 @@ When signing with `SIGN_IDENTITY="-"` (ad-hoc), the script automatically disable
 ## Build metadata for About
 
 `package-mac-app.sh` stamps the bundle with:
-- `PigbotBuildTimestamp`: ISO8601 UTC at package time
-- `PigbotGitCommit`: short git hash (or `unknown` if unavailable)
+- `MoltbotBuildTimestamp`: ISO8601 UTC at package time
+- `MoltbotGitCommit`: short git hash (or `unknown` if unavailable)
 
 The About tab reads these keys to show version, build date, git commit, and whether it’s a debug build (via `#if DEBUG`). Run the packager to refresh these values after code changes.
 
 ## Why
 
-TCC permissions are tied to the bundle identifier *and* code signature. Unsigned debug builds with changing UUIDs were causing macOS to forget grants after each rebuild. Signing the binaries (ad‑hoc by default) and keeping a fixed bundle id/path (`dist/Pigbot.app`) preserves the grants between builds, matching the VibeTunnel approach.
+TCC permissions are tied to the bundle identifier *and* code signature. Unsigned debug builds with changing UUIDs were causing macOS to forget grants after each rebuild. Signing the binaries (ad‑hoc by default) and keeping a fixed bundle id/path (`dist/Moltbot.app`) preserves the grants between builds, matching the VibeTunnel approach.

package/docs/platforms/mac/skills.md

@@ -6,21 +6,21 @@ read_when:
 ---
 # Skills (macOS)
 
-The macOS app surfaces Pigbot skills via the gateway; it does not parse skills locally.
+The macOS app surfaces Moltbot skills via the gateway; it does not parse skills locally.
 
 ## Data source
 - `skills.status` (gateway) returns all skills plus eligibility and missing requirements
   (including allowlist blocks for bundled skills).
-- Requirements are derived from `metadata.pigbot.requires` in each `SKILL.md`.
+- Requirements are derived from `metadata.clawdbot.requires` in each `SKILL.md`.
 
 ## Install actions
-- `metadata.pigbot.install` defines install options (brew/node/go/uv).
+- `metadata.clawdbot.install` defines install options (brew/node/go/uv).
 - The app calls `skills.install` to run installers on the gateway host.
 - The gateway surfaces only one preferred installer when multiple are provided
   (brew when available, otherwise node manager from `skills.install`, default npm).
 
 ## Env/API keys
-- The app stores keys in `~/.pigbot/pigbot.json` under `skills.entries.<skillKey>`.
+- The app stores keys in `~/.clawdbot/moltbot.json` under `skills.entries.<skillKey>`.
 - `skills.update` patches `enabled`, `apiKey`, and `env`.
 
 ## Remote mode

package/docs/platforms/mac/voice-overlay.md

@@ -32,14 +32,14 @@ Audience: macOS app contributors. Goal: keep the voice overlay predictable when
    - Push-to-talk: no delay; wake-word: optional delay for auto-send.
    - Apply a short cooldown to the wake runtime after push-to-talk finishes so wake-word doesn’t immediately retrigger.
 5. **Logging**
-   - Coordinator emits `.info` logs in subsystem `com.pigbot`, categories `voicewake.overlay` and `voicewake.chime`.
+   - Coordinator emits `.info` logs in subsystem `bot.molt`, categories `voicewake.overlay` and `voicewake.chime`.
    - Key events: `session_started`, `adopted_by_push_to_talk`, `partial`, `finalized`, `send`, `dismiss`, `cancel`, `cooldown`.
 
 ### Debugging checklist
 - Stream logs while reproducing a sticky overlay:
 
   ```bash
-  sudo log stream --predicate 'subsystem == "com.pigbot" AND category CONTAINS "voicewake"' --level info --style compact
+  sudo log stream --predicate 'subsystem == "bot.molt" AND category CONTAINS "voicewake"' --level info --style compact
   ```
 - Verify only one active session token; stale callbacks should be dropped by the coordinator.
 - Ensure push-to-talk release always calls `endCapture` with the active token; if text is empty, expect `dismiss` without chime or send.

package/docs/platforms/mac/webchat.md

@@ -18,9 +18,9 @@ agent (with a session switcher for other sessions).
 - Manual: Lobster menu → “Open Chat”.
 - Auto‑open for testing:
   ```bash
-  dist/Pigbot.app/Contents/MacOS/Pigbot --webchat
+  dist/Moltbot.app/Contents/MacOS/Moltbot --webchat
   ```
-- Logs: `./scripts/clawlog.sh` (subsystem `com.pigbot`, category `WebChatSwiftUI`).
+- Logs: `./scripts/clawlog.sh` (subsystem `bot.molt`, category `WebChatSwiftUI`).
 
 ## How it’s wired
 

package/docs/platforms/mac/xpc.md

@@ -1,11 +1,11 @@
 ---
-summary: "macOS IPC architecture for Pigbot app, gateway node transport, and PeekabooBridge"
+summary: "macOS IPC architecture for Moltbot app, gateway node transport, and PeekabooBridge"
 read_when:
   - Editing IPC contracts or menu bar app IPC
 ---
-# Pigbot macOS IPC architecture
+# Moltbot macOS IPC architecture
 
-**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `pigbot-mac` debug CLI exists for discovery/connect checks; agent actions still flow through the Gateway WebSocket and `node.invoke`. UI automation uses PeekabooBridge.
+**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `moltbot-mac` debug CLI exists for discovery/connect checks; agent actions still flow through the Gateway WebSocket and `node.invoke`. UI automation uses PeekabooBridge.
 
 ## Goals
 - Single GUI app instance that owns all TCC-facing work (notifications, screen recording, mic, speech, AppleScript).
@@ -32,7 +32,7 @@ Agent -> Gateway -> Node Service (WS)
 
 ### PeekabooBridge (UI automation)
 - UI automation uses a separate UNIX socket named `bridge.sock` and the PeekabooBridge JSON protocol.
-- Host preference order (client-side): Peekaboo.app → Claude.app → Pigbot.app → local execution.
+- Host preference order (client-side): Peekaboo.app → Claude.app → Moltbot.app → local execution.
 - Security: bridge hosts require an allowed TeamID; DEBUG-only same-UID escape hatch is guarded by `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1` (Peekaboo convention).
 - See: [PeekabooBridge usage](/platforms/mac/peekaboo) for details.
 

package/docs/platforms/macos-vm.md

@@ -1,13 +1,13 @@
 ---
-summary: "Run Pigbot in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage"
+summary: "Run Moltbot in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage"
 read_when:
-  - You want Pigbot isolated from your main macOS environment
+  - You want Moltbot isolated from your main macOS environment
   - You want iMessage integration (BlueBubbles) in a sandbox
   - You want a resettable macOS environment you can clone
   - You want to compare local vs hosted macOS VM options
 ---
 
-# Pigbot on macOS VMs (Sandboxing)
+# Moltbot on macOS VMs (Sandboxing)
 
 ## Recommended default (most users)
 
@@ -21,7 +21,7 @@ Use a macOS VM when you specifically need macOS-only capabilities (iMessage/Blue
 
 ### Local VM on your Apple Silicon Mac (Lume)
 
-Run Pigbot in a sandboxed macOS VM on your existing Apple Silicon Mac using [Lume](https://cua.ai/docs/lume).
+Run Moltbot in a sandboxed macOS VM on your existing Apple Silicon Mac using [Lume](https://cua.ai/docs/lume).
 
 This gives you:
 - Full macOS environment in isolation (your host stays clean)
@@ -42,10 +42,10 @@ Once you have SSH access to a macOS VM, continue at step 6 below.
 ## Quick path (Lume, experienced users)
 
 1. Install Lume
-2. `lume create pigbot --os macos --ipsw latest`
+2. `lume create moltbot --os macos --ipsw latest`
 3. Complete Setup Assistant, enable Remote Login (SSH)
-4. `lume run pigbot --no-display`
-5. SSH in, install Pigbot, configure channels
+4. `lume run moltbot --no-display`
+5. SSH in, install Moltbot, configure channels
 6. Done
 
 ---
@@ -84,7 +84,7 @@ Docs: [Lume Installation](https://cua.ai/docs/lume/guide/getting-started/install
 ## 2) Create the macOS VM
 
 ```bash
-lume create pigbot --os macos --ipsw latest
+lume create moltbot --os macos --ipsw latest
 ```
 
 This downloads macOS and creates the VM. A VNC window opens automatically.
@@ -110,7 +110,7 @@ After setup completes, enable SSH:
 ## 4) Get the VM's IP address
 
 ```bash
-lume get pigbot
+lume get moltbot
 ```
 
 Look for the IP address (usually `192.168.64.x`).
@@ -127,13 +127,13 @@ Replace `youruser` with the account you created, and the IP with your VM's IP.
 
 ---
 
-## 6) Install Pigbot
+## 6) Install Moltbot
 
 Inside the VM:
 
 ```bash
-npm install -g pigbot@latest
-pigbot onboard --install-daemon
+npm install -g moltbot@latest
+moltbot onboard --install-daemon
 ```
 
 Follow the onboarding prompts to set up your model provider (Anthropic, OpenAI, etc.).
@@ -145,7 +145,7 @@ Follow the onboarding prompts to set up your model provider (Anthropic, OpenAI,
 Edit the config file:
 
 ```bash
-nano ~/.pigbot/pigbot.json
+nano ~/.clawdbot/moltbot.json
 ```
 
 Add your channels:
@@ -167,7 +167,7 @@ Add your channels:
 Then login to WhatsApp (scan QR):
 
 ```bash
-pigbot channels login
+moltbot channels login
 ```
 
 ---
@@ -177,23 +177,23 @@ pigbot channels login
 Stop the VM and restart without display:
 
 ```bash
-lume stop pigbot
-lume run pigbot --no-display
+lume stop moltbot
+lume run moltbot --no-display
 ```
 
-The VM runs in the background. Pigbot's daemon keeps the gateway running.
+The VM runs in the background. Moltbot's daemon keeps the gateway running.
 
 To check status:
 
 ```bash
-ssh youruser@192.168.64.X "pigbot status"
+ssh youruser@192.168.64.X "moltbot status"
 ```
 
 ---
 
 ## Bonus: iMessage integration
 
-This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to Pigbot.
+This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to Moltbot.
 
 Inside the VM:
 
@@ -202,7 +202,7 @@ Inside the VM:
 3. Enable the Web API and set a password
 4. Point BlueBubbles webhooks at your gateway (example: `https://your-gateway-host:3000/bluebubbles-webhook?password=<password>`)
 
-Add to your Pigbot config:
+Add to your Moltbot config:
 
 ```json
 {
@@ -227,16 +227,16 @@ Full setup details: [BlueBubbles channel](/channels/bluebubbles)
 Before customizing further, snapshot your clean state:
 
 ```bash
-lume stop pigbot
-lume clone pigbot pigbot-golden
+lume stop moltbot
+lume clone moltbot moltbot-golden
 ```
 
 Reset anytime:
 
 ```bash
-lume stop pigbot && lume delete pigbot
-lume clone pigbot-golden pigbot
-lume run pigbot --no-display
+lume stop moltbot && lume delete moltbot
+lume clone moltbot-golden moltbot
+lume run moltbot --no-display
 ```
 
 ---
@@ -257,9 +257,9 @@ For true always-on, consider a dedicated Mac mini or a small VPS. See [VPS hosti
 | Problem | Solution |
 |---------|----------|
 | Can't SSH into VM | Check "Remote Login" is enabled in VM's System Settings |
-| VM IP not showing | Wait for VM to fully boot, run `lume get pigbot` again |
+| VM IP not showing | Wait for VM to fully boot, run `lume get moltbot` again |
 | Lume command not found | Add `~/.local/bin` to your PATH |
-| WhatsApp QR not scanning | Ensure you're logged into the VM (not host) when running `pigbot channels login` |
+| WhatsApp QR not scanning | Ensure you're logged into the VM (not host) when running `moltbot channels login` |
 
 ---
 

package/docs/platforms/macos.md

@@ -1,12 +1,12 @@
 ---
-summary: "Pigbot macOS companion app (menu bar + gateway broker)"
+summary: "Moltbot macOS companion app (menu bar + gateway broker)"
 read_when:
   - Implementing macOS app features
   - Changing gateway lifecycle or node bridging on macOS
 ---
-# Pigbot macOS Companion (menu bar + gateway broker)
+# Moltbot macOS Companion (menu bar + gateway broker)
 
-The macOS app is the **menu‑bar companion** for Pigbot. It owns permissions,
+The macOS app is the **menu‑bar companion** for Moltbot. It owns permissions,
 manages/attaches to the Gateway locally (launchd or manual), and exposes macOS
 capabilities to the agent as a node.
 
@@ -19,12 +19,12 @@ capabilities to the agent as a node.
 - Exposes macOS‑only tools (Canvas, Camera, Screen Recording, `system.run`).
 - Starts the local node host service in **remote** mode (launchd), and stops it in **local** mode.
 - Optionally hosts **PeekabooBridge** for UI automation.
-- Installs the global CLI (`pigbot`) via npm/pnpm on request (bun not recommended for the Gateway runtime).
+- Installs the global CLI (`moltbot`) via npm/pnpm on request (bun not recommended for the Gateway runtime).
 
 ## Local vs remote mode
 
 - **Local** (default): the app attaches to a running local Gateway if present;
-  otherwise it enables the launchd service via `pigbot gateway install`.
+  otherwise it enables the launchd service via `moltbot gateway install`.
 - **Remote**: the app connects to a Gateway over SSH/Tailscale and never starts
   a local process.
   The app starts the local **node host service** so the remote Gateway can reach this Mac.
@@ -32,18 +32,18 @@ The app does not spawn the Gateway as a child process.
 
 ## Launchd control
 
-The app manages a per‑user LaunchAgent labeled `com.pigbot.gateway`
-(or `com.pigbot.<profile>` when using `--profile`/`PIGBOT_PROFILE`).
+The app manages a per‑user LaunchAgent labeled `bot.molt.gateway`
+(or `bot.molt.<profile>` when using `--profile`/`CLAWDBOT_PROFILE`; legacy `com.clawdbot.*` still unloads).
 
 ```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.
 
 If the LaunchAgent isn’t installed, enable it from the app or run
-`pigbot gateway install`.
+`moltbot gateway install`.
 
 ## Node capabilities (mac)
 
@@ -74,7 +74,7 @@ Gateway -> Node Service (WS)
 Security + ask + allowlist are stored locally on the Mac in:
 
 ```
-~/.pigbot/exec-approvals.json
+~/.clawdbot/exec-approvals.json
 ```
 
 Example:
@@ -105,14 +105,14 @@ Notes:
 
 ## Deep links
 
-The app registers the `pigbot://` URL scheme for local actions.
+The app registers the `moltbot://` URL scheme for local actions.
 
-### `pigbot://agent`
+### `moltbot://agent`
 
 Triggers a Gateway `agent` request.
 
 ```bash
-open 'pigbot://agent?message=Hello%20from%20deep%20link'
+open 'moltbot://agent?message=Hello%20from%20deep%20link'
 ```
 
 Query parameters:
@@ -129,7 +129,7 @@ Safety:
 
 ## Onboarding flow (typical)
 
-1) Install and launch **Pigbot.app**.
+1) Install and launch **Moltbot.app**.
 2) Complete the permissions checklist (TCC prompts).
 3) Ensure **Local** mode is active and the Gateway is running.
 4) Install the CLI if you want terminal access.
@@ -137,7 +137,7 @@ Safety:
 ## Build & dev workflow (native)
 
 - `cd apps/macos && swift build`
-- `swift run Pigbot` (or Xcode)
+- `swift run Moltbot` (or Xcode)
 - Package app: `scripts/package-mac-app.sh`
 
 ## Debug gateway connectivity (macOS CLI)
@@ -147,8 +147,8 @@ logic that the macOS app uses, without launching the app.
 
 ```bash
 cd apps/macos
-swift run pigbot-mac connect --json
-swift run pigbot-mac discover --timeout 3000 --json
+swift run moltbot-mac connect --json
+swift run moltbot-mac discover --timeout 3000 --json
 ```
 
 Connect options:
@@ -163,7 +163,7 @@ Discovery options:
 - `--timeout <ms>`: overall discovery window (default: `2000`)
 - `--json`: structured output for diffing
 
-Tip: compare against `pigbot gateway discover --json` to see whether the
+Tip: compare against `moltbot gateway discover --json` to see whether the
 macOS app’s discovery pipeline (NWBrowser + tailnet DNS‑SD fallback) differs from
 the Node CLI’s `dns-sd` based discovery.