@gguf/pigbot 0.0.1 → 0.0.3

package/docs/install/migrating.md

@@ -0,0 +1,190 @@
+---
+summary: "Move (migrate) a Moltbot install from one machine to another"
+read_when:
+  - You are moving Moltbot to a new laptop/server
+  - You want to preserve sessions, auth, and channel logins (WhatsApp, etc.)
+---
+# Migrating Moltbot to a new machine
+
+This guide migrates a Moltbot Gateway from one machine to another **without redoing onboarding**.
+
+The migration is simple conceptually:
+
+- Copy the **state directory** (`$CLAWDBOT_STATE_DIR`, default: `~/.clawdbot/`) — this includes config, auth, sessions, and channel state.
+- Copy your **workspace** (`~/clawd/` by default) — this includes your agent files (memory, prompts, etc.).
+
+But there are common footguns around **profiles**, **permissions**, and **partial copies**.
+
+## Before you start (what you are migrating)
+
+### 1) Identify your state directory
+
+Most installs use the default:
+
+- **State dir:** `~/.clawdbot/`
+
+But it may be different if you use:
+
+- `--profile <name>` (often becomes `~/.clawdbot-<profile>/`)
+- `CLAWDBOT_STATE_DIR=/some/path`
+
+If you’re not sure, run on the **old** machine:
+
+```bash
+moltbot status
+```
+
+Look for mentions of `CLAWDBOT_STATE_DIR` / profile in the output. If you run multiple gateways, repeat for each profile.
+
+### 2) Identify your workspace
+
+Common defaults:
+
+- `~/clawd/` (recommended workspace)
+- a custom folder you created
+
+Your workspace is where files like `MEMORY.md`, `USER.md`, and `memory/*.md` live.
+
+### 3) Understand what you will preserve
+
+If you copy **both** the state dir and workspace, you keep:
+
+- Gateway configuration (`moltbot.json`)
+- Auth profiles / API keys / OAuth tokens
+- Session history + agent state
+- Channel state (e.g. WhatsApp login/session)
+- Your workspace files (memory, skills notes, etc.)
+
+If you copy **only** the workspace (e.g., via Git), you do **not** preserve:
+
+- sessions
+- credentials
+- channel logins
+
+Those live under `$CLAWDBOT_STATE_DIR`.
+
+## Migration steps (recommended)
+
+### Step 0 — Make a backup (old machine)
+
+On the **old** machine, stop the gateway first so files aren’t changing mid-copy:
+
+```bash
+moltbot gateway stop
+```
+
+(Optional but recommended) archive the state dir and workspace:
+
+```bash
+# Adjust paths if you use a profile or custom locations
+cd ~
+tar -czf moltbot-state.tgz .clawdbot
+
+tar -czf clawd-workspace.tgz clawd
+```
+
+If you have multiple profiles/state dirs (e.g. `~/.clawdbot-main`, `~/.clawdbot-work`), archive each.
+
+### Step 1 — Install Moltbot on the new machine
+
+On the **new** machine, install the CLI (and Node if needed):
+
+- See: [Install](/install)
+
+At this stage, it’s OK if onboarding creates a fresh `~/.clawdbot/` — you will overwrite it in the next step.
+
+### Step 2 — Copy the state dir + workspace to the new machine
+
+Copy **both**:
+
+- `$CLAWDBOT_STATE_DIR` (default `~/.clawdbot/`)
+- your workspace (default `~/clawd/`)
+
+Common approaches:
+
+- `scp` the tarballs and extract
+- `rsync -a` over SSH
+- external drive
+
+After copying, ensure:
+
+- Hidden directories were included (e.g. `.clawdbot/`)
+- File ownership is correct for the user running the gateway
+
+### Step 3 — Run Doctor (migrations + service repair)
+
+On the **new** machine:
+
+```bash
+moltbot doctor
+```
+
+Doctor is the “safe boring” command. It repairs services, applies config migrations, and warns about mismatches.
+
+Then:
+
+```bash
+moltbot gateway restart
+moltbot status
+```
+
+## Common footguns (and how to avoid them)
+
+### Footgun: profile / state-dir mismatch
+
+If you ran the old gateway with a profile (or `CLAWDBOT_STATE_DIR`), and the new gateway uses a different one, you’ll see symptoms like:
+
+- config changes not taking effect
+- channels missing / logged out
+- empty session history
+
+Fix: run the gateway/service using the **same** profile/state dir you migrated, then rerun:
+
+```bash
+moltbot doctor
+```
+
+### Footgun: copying only `moltbot.json`
+
+`moltbot.json` is not enough. Many providers store state under:
+
+- `$CLAWDBOT_STATE_DIR/credentials/`
+- `$CLAWDBOT_STATE_DIR/agents/<agentId>/...`
+
+Always migrate the entire `$CLAWDBOT_STATE_DIR` folder.
+
+### Footgun: permissions / ownership
+
+If you copied as root or changed users, the gateway may fail to read credentials/sessions.
+
+Fix: ensure the state dir + workspace are owned by the user running the gateway.
+
+### Footgun: migrating between remote/local modes
+
+- If your UI (WebUI/TUI) points at a **remote** gateway, the remote host owns the session store + workspace.
+- Migrating your laptop won’t move the remote gateway’s state.
+
+If you’re in remote mode, migrate the **gateway host**.
+
+### Footgun: secrets in backups
+
+`$CLAWDBOT_STATE_DIR` contains secrets (API keys, OAuth tokens, WhatsApp creds). Treat backups like production secrets:
+
+- store encrypted
+- avoid sharing over insecure channels
+- rotate keys if you suspect exposure
+
+## Verification checklist
+
+On the new machine, confirm:
+
+- `moltbot status` shows the gateway running
+- Your channels are still connected (e.g. WhatsApp doesn’t require re-pair)
+- The dashboard opens and shows existing sessions
+- Your workspace files (memory, configs) are present
+
+## Related
+
+- [Doctor](/gateway/doctor)
+- [Gateway troubleshooting](/gateway/troubleshooting)
+- [Where does Moltbot store its data?](/help/faq#where-does-moltbot-store-its-data)

package/docs/install/nix.md

@@ -1,5 +1,5 @@
 ---
-summary: "Install Pigbot declaratively with Nix"
+summary: "Install Moltbot declaratively with Nix"
 read_when:
   - You want reproducible, rollback-able installs
   - You're already using Nix/NixOS/Home Manager
@@ -8,30 +8,30 @@ read_when:
 
 # Nix Installation
 
-The recommended way to run Pigbot with Nix is via **[nix-pigbot](https://github.com/pigbot/nix-pigbot)** — a batteries-included Home Manager module.
+The recommended way to run Moltbot with Nix is via **[nix-moltbot](https://github.com/moltbot/nix-moltbot)** — a batteries-included Home Manager module.
 
 ## Quick Start
 
 Paste this to your AI agent (Claude, Cursor, etc.):
 
 ```text
-I want to set up nix-pigbot on my Mac.
-Repository: github:pigbot/nix-pigbot
+I want to set up nix-moltbot on my Mac.
+Repository: github:moltbot/nix-moltbot
 
 What I need you to do:
 1. Check if Determinate Nix is installed (if not, install it)
-2. Create a local flake at ~/code/pigbot-local using templates/agent-first/flake.nix
+2. Create a local flake at ~/code/moltbot-local using templates/agent-first/flake.nix
 3. Help me create a Telegram bot (@BotFather) and get my chat ID (@userinfobot)
 4. Set up secrets (bot token, Anthropic key) - plain files at ~/.secrets/ is fine
 5. Fill in the template placeholders and run home-manager switch
 6. Verify: launchd running, bot responds to messages
 
-Reference the nix-pigbot README for module options.
+Reference the nix-moltbot README for module options.
 ```
 
-> **📦 Full guide: [github.com/pigbot/nix-pigbot](https://github.com/pigbot/nix-pigbot)**
+> **📦 Full guide: [github.com/moltbot/nix-moltbot](https://github.com/moltbot/nix-moltbot)**
 >
-> The nix-pigbot repo is the source of truth for Nix installation. This page is just a quick overview.
+> The nix-moltbot repo is the source of truth for Nix installation. This page is just a quick overview.
 
 ## What you get
 
@@ -44,28 +44,28 @@ Reference the nix-pigbot README for module options.
 
 ## Nix Mode Runtime Behavior
 
-When `PIGBOT_NIX_MODE=1` is set (automatic with nix-pigbot):
+When `CLAWDBOT_NIX_MODE=1` is set (automatic with nix-moltbot):
 
-Pigbot supports a **Nix mode** that makes configuration deterministic and disables auto-install flows.
+Moltbot supports a **Nix mode** that makes configuration deterministic and disables auto-install flows.
 Enable it by exporting:
 
 ```bash
-PIGBOT_NIX_MODE=1
+CLAWDBOT_NIX_MODE=1
 ```
 
 On macOS, the GUI app does not automatically inherit shell env vars. You can
 also enable Nix mode via defaults:
 
 ```bash
-defaults write com.pigbot.mac pigbot.nixMode -bool true
+defaults write bot.molt.mac moltbot.nixMode -bool true
 ```
 
 ### Config + state paths
 
-Pigbot reads JSON5 config from `PIGBOT_CONFIG_PATH` and stores mutable data in `PIGBOT_STATE_DIR`.
+Moltbot reads JSON5 config from `CLAWDBOT_CONFIG_PATH` and stores mutable data in `CLAWDBOT_STATE_DIR`.
 
-- `PIGBOT_STATE_DIR` (default: `~/.pigbot`)
-- `PIGBOT_CONFIG_PATH` (default: `$PIGBOT_STATE_DIR/pigbot.json`)
+- `CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`)
+- `CLAWDBOT_CONFIG_PATH` (default: `$CLAWDBOT_STATE_DIR/moltbot.json`)
 
 When running under Nix, set these explicitly to Nix-managed locations so runtime state and config
 stay out of the immutable store.
@@ -81,15 +81,15 @@ stay out of the immutable store.
 The macOS packaging flow expects a stable Info.plist template at:
 
 ```
-apps/macos/Sources/Pigbot/Resources/Info.plist
+apps/macos/Sources/Moltbot/Resources/Info.plist
 ```
 
-[`scripts/package-mac-app.sh`](https://github.com/pigbot/pigbot/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields
+[`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields
 (bundle ID, version/build, Git SHA, Sparkle keys). This keeps the plist deterministic for SwiftPM
 packaging and Nix builds (which do not rely on a full Xcode toolchain).
 
 ## Related
 
-- [nix-pigbot](https://github.com/pigbot/nix-pigbot) — full setup guide
+- [nix-moltbot](https://github.com/moltbot/nix-moltbot) — full setup guide
 - [Wizard](/start/wizard) — non-Nix CLI setup
 - [Docker](/install/docker) — containerized setup

package/docs/install/node.md

@@ -1,16 +1,17 @@
 ---
+title: "Node.js + npm (PATH sanity)"
 summary: "Node.js + npm install sanity: versions, PATH, and global installs"
 read_when:
-  - You installed Pigbot but `pigbot` is “command not found”
-  - You’re setting up Node.js/npm on a new machine
-  - `npm install -g ...` fails with permissions or PATH issues
+  - "You installed Moltbot but `moltbot` is “command not found”"
+  - "You’re setting up Node.js/npm on a new machine"
+  - "npm install -g ... fails with permissions or PATH issues"
 ---
 
 # Node.js + npm (PATH sanity)
 
-Pigbot’s runtime baseline is **Node 22+**.
+Moltbot’s runtime baseline is **Node 22+**.
 
-If you can run `npm install -g pigbot@latest` but later see `pigbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
+If you can run `npm install -g moltbot@latest` but later see `moltbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
 
 ## Quick diagnosis
 
@@ -23,7 +24,7 @@ npm prefix -g
 echo "$PATH"
 ```
 
-If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `pigbot`).
+If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `moltbot`).
 
 ## Fix: put npm’s global bin dir on PATH
 

package/docs/install/uninstall.md

@@ -1,14 +1,14 @@
 ---
-summary: "Uninstall Pigbot completely (CLI, service, state, workspace)"
+summary: "Uninstall Moltbot completely (CLI, service, state, workspace)"
 read_when:
-  - You want to remove Pigbot from a machine
+  - You want to remove Moltbot from a machine
   - The gateway service is still running after uninstall
 ---
 
 # Uninstall
 
 Two paths:
-- **Easy path** if `pigbot` is still installed.
+- **Easy path** if `moltbot` is still installed.
 - **Manual service removal** if the CLI is gone but the service is still running.
 
 ## Easy path (CLI still installed)
@@ -16,14 +16,14 @@ Two paths:
 Recommended: use the built-in uninstaller:
 
 ```bash
-pigbot uninstall
+moltbot uninstall
 ```
 
 Non-interactive (automation / npx):
 
 ```bash
-pigbot uninstall --all --yes --non-interactive
-npx -y pigbot uninstall --all --yes --non-interactive
+moltbot uninstall --all --yes --non-interactive
+npx -y moltbot uninstall --all --yes --non-interactive
 ```
 
 Manual steps (same result):
@@ -31,22 +31,22 @@ Manual steps (same result):
 1) Stop the gateway service:
 
 ```bash
-pigbot gateway stop
+moltbot gateway stop
 ```
 
 2) Uninstall the gateway service (launchd/systemd/schtasks):
 
 ```bash
-pigbot gateway uninstall
+moltbot gateway uninstall
 ```
 
 3) Delete state + config:
 
 ```bash
-rm -rf "${PIGBOT_STATE_DIR:-$HOME/.pigbot}"
+rm -rf "${CLAWDBOT_STATE_DIR:-$HOME/.clawdbot}"
 ```
 
-If you set `PIGBOT_CONFIG_PATH` to a custom location outside the state dir, delete that file too.
+If you set `CLAWDBOT_CONFIG_PATH` to a custom location outside the state dir, delete that file too.
 
 4) Delete your workspace (optional, removes agent files):
 
@@ -57,68 +57,68 @@ rm -rf ~/clawd
 5) Remove the CLI install (pick the one you used):
 
 ```bash
-npm rm -g pigbot
-pnpm remove -g pigbot
-bun remove -g pigbot
+npm rm -g moltbot
+pnpm remove -g moltbot
+bun remove -g moltbot
 ```
 
 6) If you installed the macOS app:
 
 ```bash
-rm -rf /Applications/Pigbot.app
+rm -rf /Applications/Moltbot.app
 ```
 
 Notes:
-- If you used profiles (`--profile` / `PIGBOT_PROFILE`), repeat step 3 for each state dir (defaults are `~/.pigbot-<profile>`).
+- If you used profiles (`--profile` / `CLAWDBOT_PROFILE`), repeat step 3 for each state dir (defaults are `~/.clawdbot-<profile>`).
 - In remote mode, the state dir lives on the **gateway host**, so run steps 1-4 there too.
 
 ## Manual service removal (CLI not installed)
 
-Use this if the gateway service keeps running but `pigbot` is missing.
+Use this if the gateway service keeps running but `moltbot` is missing.
 
 ### macOS (launchd)
 
-Default label is `com.pigbot.gateway` (or `com.pigbot.<profile>`):
+Default label is `bot.molt.gateway` (or `bot.molt.<profile>`; legacy `com.clawdbot.*` may still exist):
 
 ```bash
-launchctl bootout gui/$UID/com.pigbot.gateway
-rm -f ~/Library/LaunchAgents/com.pigbot.gateway.plist
+launchctl bootout gui/$UID/bot.molt.gateway
+rm -f ~/Library/LaunchAgents/bot.molt.gateway.plist
 ```
 
-If you used a profile, replace the label and plist name with `com.pigbot.<profile>`.
+If you used a profile, replace the label and plist name with `bot.molt.<profile>`. Remove any legacy `com.clawdbot.*` plists if present.
 
 ### Linux (systemd user unit)
 
-Default unit name is `pigbot-gateway.service` (or `pigbot-gateway-<profile>.service`):
+Default unit name is `moltbot-gateway.service` (or `moltbot-gateway-<profile>.service`):
 
 ```bash
-systemctl --user disable --now pigbot-gateway.service
-rm -f ~/.config/systemd/user/pigbot-gateway.service
+systemctl --user disable --now moltbot-gateway.service
+rm -f ~/.config/systemd/user/moltbot-gateway.service
 systemctl --user daemon-reload
 ```
 
 ### Windows (Scheduled Task)
 
-Default task name is `Pigbot Gateway` (or `Pigbot Gateway (<profile>)`).
+Default task name is `Moltbot Gateway` (or `Moltbot Gateway (<profile>)`).
 The task script lives under your state dir.
 
 ```powershell
-schtasks /Delete /F /TN "Pigbot Gateway"
-Remove-Item -Force "$env:USERPROFILE\.pigbot\gateway.cmd"
+schtasks /Delete /F /TN "Moltbot Gateway"
+Remove-Item -Force "$env:USERPROFILE\.clawdbot\gateway.cmd"
 ```
 
-If you used a profile, delete the matching task name and `~\.pigbot-<profile>\gateway.cmd`.
+If you used a profile, delete the matching task name and `~\.clawdbot-<profile>\gateway.cmd`.
 
 ## Normal install vs source checkout
 
 ### Normal install (install.sh / npm / pnpm / bun)
 
-If you used `https://clawd.bot/install.sh` or `install.ps1`, the CLI was installed with `npm install -g pigbot@latest`.
-Remove it with `npm rm -g pigbot` (or `pnpm remove -g` / `bun remove -g` if you installed that way).
+If you used `https://molt.bot/install.sh` or `install.ps1`, the CLI was installed with `npm install -g moltbot@latest`.
+Remove it with `npm rm -g moltbot` (or `pnpm remove -g` / `bun remove -g` if you installed that way).
 
 ### Source checkout (git clone)
 
-If you run from a repo checkout (`git clone` + `pigbot ...` / `bun run pigbot ...`):
+If you run from a repo checkout (`git clone` + `moltbot ...` / `bun run moltbot ...`):
 
 1) Uninstall the gateway service **before** deleting the repo (use the easy path above or manual service removal).
 2) Delete the repo directory.