@gguf/pigbot 0.0.1 → 0.0.2

package/docs/index.md

@@ -1,14 +1,14 @@
 ---
-summary: "Top-level overview of Pigbot, features, and purpose"
+summary: "Top-level overview of Moltbot, features, and purpose"
 read_when:
-  - Introducing Pigbot to newcomers
+  - Introducing Moltbot to newcomers
 ---
-# Pigbot 🦞
+# Moltbot 🦞
 
 > *"EXFOLIATE! EXFOLIATE!"* — A space lobster, probably
 
 <p align="center">
-  <img src="whatsapp-clawd.jpg" alt="Pigbot" width="420" />
+  <img src="whatsapp-clawd.jpg" alt="Moltbot" width="420" />
 </p>
 
 <p align="center">
@@ -18,23 +18,23 @@ read_when:
 </p>
 
 <p align="center">
-  <a href="https://github.com/pigbot/pigbot">GitHub</a> ·
-  <a href="https://github.com/pigbot/pigbot/releases">Releases</a> ·
+  <a href="https://github.com/moltbot/moltbot">GitHub</a> ·
+  <a href="https://github.com/moltbot/moltbot/releases">Releases</a> ·
   <a href="/">Docs</a> ·
-  <a href="/start/clawd">Pigbot assistant setup</a>
+  <a href="/start/clawd">Moltbot assistant setup</a>
 </p>
 
-Pigbot bridges WhatsApp (via WhatsApp Web / Baileys), Telegram (Bot API / grammY), Discord (Bot API / channels.discord.js), and iMessage (imsg CLI) to coding agents like [Pi](https://github.com/badlogic/pi-mono). Plugins add Mattermost (Bot API + WebSocket) and more.
-Pigbot also powers [Clawd](https://clawd.me), the space‑lobster assistant.
+Moltbot bridges WhatsApp (via WhatsApp Web / Baileys), Telegram (Bot API / grammY), Discord (Bot API / channels.discord.js), and iMessage (imsg CLI) to coding agents like [Pi](https://github.com/badlogic/pi-mono). Plugins add Mattermost (Bot API + WebSocket) and more.
+Moltbot also powers [Clawd](https://clawd.me), the space‑lobster assistant.
 
 ## Start here
 
 - **New install from zero:** [Getting Started](/start/getting-started)
-- **Guided setup (recommended):** [Wizard](/start/wizard) (`pigbot onboard`)
+- **Guided setup (recommended):** [Wizard](/start/wizard) (`moltbot onboard`)
 - **Open the dashboard (local Gateway):** http://127.0.0.1:18789/ (or http://localhost:18789/)
 
 If the Gateway is running on the same computer, that link opens the browser Control UI
-immediately. If it fails, start the Gateway first: `pigbot gateway`.
+immediately. If it fails, start the Gateway first: `moltbot gateway`.
 
 ## Dashboard (browser Control UI)
 
@@ -52,27 +52,27 @@ WhatsApp / Telegram / Discord / iMessage (+ plugins)
   │          Gateway          │  ws://127.0.0.1:18789 (loopback-only)
   │     (single source)       │
   │                           │  http://<gateway-host>:18793
-  │                           │    /__pigbot__/canvas/ (Canvas host)
+  │                           │    /__moltbot__/canvas/ (Canvas host)
   └───────────┬───────────────┘
               │
               ├─ Pi agent (RPC)
-              ├─ CLI (pigbot …)
+              ├─ CLI (moltbot …)
               ├─ Chat UI (SwiftUI)
-              ├─ macOS app (Pigbot.app)
+              ├─ macOS app (Moltbot.app)
               ├─ iOS node via Gateway WS + pairing
               └─ Android node via Gateway WS + pairing
 ```
 
-Most operations flow through the **Gateway** (`pigbot gateway`), a single long-running process that owns channel connections and the WebSocket control plane.
+Most operations flow through the **Gateway** (`moltbot gateway`), a single long-running process that owns channel connections and the WebSocket control plane.
 
 ## Network model
 
 - **One Gateway per host (recommended)**: it is the only process allowed to own the WhatsApp Web session. If you need a rescue bot or strict isolation, run multiple gateways with isolated profiles and ports; see [Multiple gateways](/gateway/multiple-gateways).
 - **Loopback-first**: Gateway WS defaults to `ws://127.0.0.1:18789`.
   - The wizard now generates a gateway token by default (even for loopback).
-  - For Tailnet access, run `pigbot gateway --bind tailnet --token ...` (token is required for non-loopback binds).
+  - For Tailnet access, run `moltbot gateway --bind tailnet --token ...` (token is required for non-loopback binds).
 - **Nodes**: connect to the Gateway WebSocket (LAN/tailnet/SSH as needed); legacy TCP bridge is deprecated/removed.
-- **Canvas host**: HTTP file server on `canvasHost.port` (default `18793`), serving `/__pigbot__/canvas/` for node WebViews; see [Gateway configuration](/gateway/configuration) (`canvasHost`).
+- **Canvas host**: HTTP file server on `canvasHost.port` (default `18793`), serving `/__moltbot__/canvas/` for node WebViews; see [Gateway configuration](/gateway/configuration) (`canvasHost`).
 - **Remote use**: SSH tunnel or tailnet/VPN; see [Remote access](/gateway/remote) and [Discovery](/gateway/discovery).
 
 ## Features (high level)
@@ -102,53 +102,53 @@ Runtime requirement: **Node ≥ 22**.
 
 ```bash
 # Recommended: global install (npm/pnpm)
-npm install -g pigbot@latest
-# or: pnpm add -g pigbot@latest
+npm install -g moltbot@latest
+# or: pnpm add -g moltbot@latest
 
 # Onboard + install the service (launchd/systemd user service)
-pigbot onboard --install-daemon
+moltbot onboard --install-daemon
 
 # Pair WhatsApp Web (shows QR)
-pigbot channels login
+moltbot channels login
 
 # Gateway runs via the service after onboarding; manual run is still possible:
-pigbot gateway --port 18789
+moltbot gateway --port 18789
 ```
 
-Switching between npm and git installs later is easy: install the other flavor and run `pigbot doctor` to update the gateway service entrypoint.
+Switching between npm and git installs later is easy: install the other flavor and run `moltbot doctor` to update the gateway service entrypoint.
 
 From source (development):
 
 ```bash
-git clone https://github.com/pigbot/pigbot.git
-cd pigbot
+git clone https://github.com/moltbot/moltbot.git
+cd moltbot
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
-pigbot onboard --install-daemon
+moltbot onboard --install-daemon
 ```
 
-If you don’t have a global install yet, run the onboarding step via `pnpm pigbot ...` from the repo.
+If you don’t have a global install yet, run the onboarding step via `pnpm moltbot ...` from the repo.
 
 Multi-instance quickstart (optional):
 
 ```bash
-PIGBOT_CONFIG_PATH=~/.pigbot/a.json \
-PIGBOT_STATE_DIR=~/.pigbot-a \
-pigbot gateway --port 19001
+CLAWDBOT_CONFIG_PATH=~/.clawdbot/a.json \
+CLAWDBOT_STATE_DIR=~/.clawdbot-a \
+moltbot gateway --port 19001
 ```
 
 Send a test message (requires a running Gateway):
 
 ```bash
-pigbot message send --target +15555550123 --message "Hello from Pigbot"
+moltbot message send --target +15555550123 --message "Hello from Moltbot"
 ```
 
 ## Configuration (optional)
 
-Config lives at `~/.pigbot/pigbot.json`.
+Config lives at `~/.clawdbot/moltbot.json`.
 
-- If you **do nothing**, Pigbot uses the bundled Pi binary in RPC mode with per-sender sessions.
+- If you **do nothing**, Moltbot uses the bundled Pi binary in RPC mode with per-sender sessions.
 - If you want to lock it down, start with `channels.whatsapp.allowFrom` and (for groups) mention rules.
 
 Example:
@@ -177,7 +177,7 @@ Example:
   - [Updating / rollback](/install/updating)
   - [Pairing (DM + nodes)](/start/pairing)
   - [Nix mode](/install/nix)
-  - [Pigbot assistant setup (Clawd)](/start/clawd)
+  - [Moltbot assistant setup (Clawd)](/start/clawd)
   - [Skills](/tools/skills)
   - [Skills config](/tools/skills-config)
   - [Workspace templates](/reference/templates/AGENTS)
@@ -214,7 +214,7 @@ Example:
 
 ## The name
 
-**Pigbot = CLAW + TARDIS** — because every space lobster needs a time-and-space machine.
+**Moltbot = CLAW + TARDIS** — because every space lobster needs a time-and-space machine.
 
 ---
 

package/docs/install/ansible.md

@@ -1,5 +1,5 @@
 ---
-summary: "Automated, hardened Pigbot installation with Ansible, Tailscale VPN, and firewall isolation"
+summary: "Automated, hardened Moltbot installation with Ansible, Tailscale VPN, and firewall isolation"
 read_when:
   - You want automated server deployment with security hardening
   - You need firewall-isolated setup with VPN access
@@ -8,19 +8,19 @@ read_when:
 
 # Ansible Installation
 
-The recommended way to deploy Pigbot to production servers is via **[pigbot-ansible](https://github.com/pigbot/pigbot-ansible)** — an automated installer with security-first architecture.
+The recommended way to deploy Moltbot to production servers is via **[moltbot-ansible](https://github.com/moltbot/moltbot-ansible)** — an automated installer with security-first architecture.
 
 ## Quick Start
 
 One-command install:
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/pigbot/pigbot-ansible/main/install.sh | bash
+curl -fsSL https://raw.githubusercontent.com/moltbot/moltbot-ansible/main/install.sh | bash
 ```
 
-> **📦 Full guide: [github.com/pigbot/pigbot-ansible](https://github.com/pigbot/pigbot-ansible)**
+> **📦 Full guide: [github.com/moltbot/moltbot-ansible](https://github.com/moltbot/moltbot-ansible)**
 >
-> The pigbot-ansible repo is the source of truth for Ansible deployment. This page is a quick overview.
+> The moltbot-ansible repo is the source of truth for Ansible deployment. This page is a quick overview.
 
 ## What You Get
 
@@ -46,22 +46,22 @@ The Ansible playbook installs and configures:
 2. **UFW firewall** (SSH + Tailscale ports only)
 3. **Docker CE + Compose V2** (for agent sandboxes)
 4. **Node.js 22.x + pnpm** (runtime dependencies)
-5. **Pigbot** (host-based, not containerized)
+5. **Moltbot** (host-based, not containerized)
 6. **Systemd service** (auto-start with security hardening)
 
 Note: The gateway runs **directly on the host** (not in Docker), but agent sandboxes use Docker for isolation. See [Sandboxing](/gateway/sandboxing) for details.
 
 ## Post-Install Setup
 
-After installation completes, switch to the pigbot user:
+After installation completes, switch to the moltbot user:
 
 ```bash
-sudo -i -u pigbot
+sudo -i -u moltbot
 ```
 
 The post-install script will guide you through:
 
-1. **Onboarding wizard**: Configure Pigbot settings
+1. **Onboarding wizard**: Configure Moltbot settings
 2. **Provider login**: Connect WhatsApp/Telegram/Discord/Signal
 3. **Gateway testing**: Verify the installation
 4. **Tailscale setup**: Connect to your VPN mesh
@@ -70,17 +70,17 @@ The post-install script will guide you through:
 
 ```bash
 # Check service status
-sudo systemctl status pigbot
+sudo systemctl status moltbot
 
 # View live logs
-sudo journalctl -u pigbot -f
+sudo journalctl -u moltbot -f
 
 # Restart gateway
-sudo systemctl restart pigbot
+sudo systemctl restart moltbot
 
-# Provider login (run as pigbot user)
-sudo -i -u pigbot
-pigbot channels login
+# Provider login (run as moltbot user)
+sudo -i -u moltbot
+moltbot channels login
 ```
 
 ## Security Architecture
@@ -117,8 +117,8 @@ If you prefer manual control over the automation:
 sudo apt update && sudo apt install -y ansible git
 
 # 2. Clone repository
-git clone https://github.com/pigbot/pigbot-ansible.git
-cd pigbot-ansible
+git clone https://github.com/moltbot/moltbot-ansible.git
+cd moltbot-ansible
 
 # 3. Install Ansible collections
 ansible-galaxy collection install -r requirements.yml
@@ -126,18 +126,18 @@ ansible-galaxy collection install -r requirements.yml
 # 4. Run playbook
 ./run-playbook.sh
 
-# Or run directly (then manually execute /tmp/pigbot-setup.sh after)
+# Or run directly (then manually execute /tmp/moltbot-setup.sh after)
 # ansible-playbook playbook.yml --ask-become-pass
 ```
 
-## Updating Pigbot
+## Updating Moltbot
 
-The Ansible installer sets up Pigbot for manual updates. See [Updating](/install/updating) for the standard update flow.
+The Ansible installer sets up Moltbot for manual updates. See [Updating](/install/updating) for the standard update flow.
 
 To re-run the Ansible playbook (e.g., for configuration changes):
 
 ```bash
-cd pigbot-ansible
+cd moltbot-ansible
 ./run-playbook.sh
 ```
 
@@ -156,14 +156,14 @@ If you're locked out:
 
 ```bash
 # Check logs
-sudo journalctl -u pigbot -n 100
+sudo journalctl -u moltbot -n 100
 
 # Verify permissions
-sudo ls -la /opt/pigbot
+sudo ls -la /opt/moltbot
 
 # Test manual start
-sudo -i -u pigbot
-cd ~/pigbot
+sudo -i -u moltbot
+cd ~/moltbot
 pnpm start
 ```
 
@@ -174,32 +174,32 @@ pnpm start
 sudo systemctl status docker
 
 # Check sandbox image
-sudo docker images | grep pigbot-sandbox
+sudo docker images | grep moltbot-sandbox
 
 # Build sandbox image if missing
-cd /opt/pigbot/pigbot
-sudo -u pigbot ./scripts/sandbox-setup.sh
+cd /opt/moltbot/moltbot
+sudo -u moltbot ./scripts/sandbox-setup.sh
 ```
 
 ### Provider login fails
 
-Make sure you're running as the `pigbot` user:
+Make sure you're running as the `moltbot` user:
 
 ```bash
-sudo -i -u pigbot
-pigbot channels login
+sudo -i -u moltbot
+moltbot channels login
 ```
 
 ## Advanced Configuration
 
 For detailed security architecture and troubleshooting:
-- [Security Architecture](https://github.com/pigbot/pigbot-ansible/blob/main/docs/security.md)
-- [Technical Details](https://github.com/pigbot/pigbot-ansible/blob/main/docs/architecture.md)
-- [Troubleshooting Guide](https://github.com/pigbot/pigbot-ansible/blob/main/docs/troubleshooting.md)
+- [Security Architecture](https://github.com/moltbot/moltbot-ansible/blob/main/docs/security.md)
+- [Technical Details](https://github.com/moltbot/moltbot-ansible/blob/main/docs/architecture.md)
+- [Troubleshooting Guide](https://github.com/moltbot/moltbot-ansible/blob/main/docs/troubleshooting.md)
 
 ## Related
 
-- [pigbot-ansible](https://github.com/pigbot/pigbot-ansible) — full deployment guide
+- [moltbot-ansible](https://github.com/moltbot/moltbot-ansible) — full deployment guide
 - [Docker](/install/docker) — containerized gateway setup
 - [Sandboxing](/gateway/sandboxing) — agent sandbox configuration
 - [Multi-Agent Sandbox & Tools](/multi-agent-sandbox-tools) — per-agent isolation

package/docs/install/development-channels.md

@@ -9,7 +9,7 @@ read_when:
 
 Last updated: 2026-01-21
 
-Pigbot ships three update channels:
+Moltbot ships three update channels:
 
 - **stable**: npm dist-tag `latest`.
 - **beta**: npm dist-tag `beta` (builds under test).
@@ -23,9 +23,9 @@ without changing the version number — dist-tags are the source of truth for np
 Git checkout:
 
 ```bash
-pigbot update --channel stable
-pigbot update --channel beta
-pigbot update --channel dev
+moltbot update --channel stable
+moltbot update --channel beta
+moltbot update --channel dev
 ```
 
 - `stable`/`beta` check out the latest matching tag (often the same tag).
@@ -34,17 +34,17 @@ pigbot update --channel dev
 npm/pnpm global install:
 
 ```bash
-pigbot update --channel stable
-pigbot update --channel beta
-pigbot update --channel dev
+moltbot update --channel stable
+moltbot update --channel beta
+moltbot update --channel dev
 ```
 
 This updates via the corresponding npm dist-tag (`latest`, `beta`, `dev`).
 
-When you **explicitly** switch channels with `--channel`, Pigbot also aligns
+When you **explicitly** switch channels with `--channel`, Moltbot also aligns
 the install method:
 
-- `dev` ensures a git checkout (default `~/pigbot`, override with `PIGBOT_GIT_DIR`),
+- `dev` ensures a git checkout (default `~/moltbot`, override with `CLAWDBOT_GIT_DIR`),
   updates it, and installs the global CLI from that checkout.
 - `stable`/`beta` installs from npm using the matching dist-tag.
 
@@ -52,7 +52,7 @@ Tip: if you want stable + dev in parallel, keep two clones and point your gatewa
 
 ## Plugins and channels
 
-When you switch channels with `pigbot update`, Pigbot also syncs plugin sources:
+When you switch channels with `moltbot update`, Moltbot also syncs plugin sources:
 
 - `dev` prefers bundled plugins from the git checkout.
 - `stable` and `beta` restore npm-installed plugin packages.