@gguf/pigbot 0.0.1 → 0.0.3

package/docs/environment.md

@@ -1,5 +1,5 @@
 ---
-summary: "Where Pigbot loads environment variables and the precedence order"
+summary: "Where Moltbot loads environment variables and the precedence order"
 read_when:
   - You need to know which env vars are loaded, and in what order
   - You are debugging missing API keys in the Gateway
@@ -7,15 +7,15 @@ read_when:
 ---
 # Environment variables
 
-Pigbot pulls environment variables from multiple sources. The rule is **never override existing values**.
+Moltbot pulls environment variables from multiple sources. The rule is **never override existing values**.
 
 ## Precedence (highest → lowest)
 
 1) **Process environment** (what the Gateway process already has from the parent shell/daemon).
 2) **`.env` in the current working directory** (dotenv default; does not override).
-3) **Global `.env`** at `~/.pigbot/.env` (aka `$PIGBOT_STATE_DIR/.env`; does not override).
-4) **Config `env` block** in `~/.pigbot/pigbot.json` (applied only if missing).
-5) **Optional login-shell import** (`env.shellEnv.enabled` or `PIGBOT_LOAD_SHELL_ENV=1`), applied only for missing expected keys.
+3) **Global `.env`** at `~/.clawdbot/.env` (aka `$CLAWDBOT_STATE_DIR/.env`; does not override).
+4) **Config `env` block** in `~/.clawdbot/moltbot.json` (applied only if missing).
+5) **Optional login-shell import** (`env.shellEnv.enabled` or `CLAWDBOT_LOAD_SHELL_ENV=1`), applied only for missing expected keys.
 
 If the config file is missing entirely, step 4 is skipped; shell import still runs if enabled.
 
@@ -50,8 +50,8 @@ Two equivalent ways to set inline env vars (both are non-overriding):
 ```
 
 Env var equivalents:
-- `PIGBOT_LOAD_SHELL_ENV=1`
-- `PIGBOT_SHELL_ENV_TIMEOUT_MS=15000`
+- `CLAWDBOT_LOAD_SHELL_ENV=1`
+- `CLAWDBOT_SHELL_ENV_TIMEOUT_MS=15000`
 
 ## Env var substitution in config
 

package/docs/experiments/plans/cron-add-hardening.md

@@ -1,6 +1,6 @@
 ---
 summary: "Harden cron.add input handling, align schemas, and improve cron UI/agent tooling"
-owner: "pigbot"
+owner: "moltbot"
 status: "complete"
 last_updated: "2026-01-05"
 ---

package/docs/experiments/plans/openresponses-gateway.md

@@ -1,6 +1,6 @@
 ---
 summary: "Plan: Add OpenResponses /v1/responses endpoint and deprecate chat completions cleanly"
-owner: "pigbot"
+owner: "moltbot"
 status: "draft"
 last_updated: "2026-01-19"
 ---
@@ -9,7 +9,7 @@ last_updated: "2026-01-19"
 
 ## Context
 
-Pigbot Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
+Moltbot Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
 `/v1/chat/completions` (see [OpenAI Chat Completions](/gateway/openai-http-api)).
 
 Open Responses is an open inference standard based on the OpenAI Responses API. It is designed

package/docs/experiments/research/memory.md

@@ -2,7 +2,7 @@
 summary: "Research notes: offline memory system for Clawd workspaces (Markdown source-of-truth + derived index)"
 read_when:
   - Designing workspace memory (~/clawd) beyond daily Markdown logs
-  - Deciding: standalone CLI vs deep Pigbot integration
+  - Deciding: standalone CLI vs deep Moltbot integration
   - Adding offline recall + reflection (retain/recall/reflect)
 ---
 
@@ -155,16 +155,16 @@ Opinion evolution (simple, explainable):
 
 ## CLI integration: standalone vs deep integration
 
-Recommendation: **deep integration in Pigbot**, but keep a separable core library.
+Recommendation: **deep integration in Moltbot**, but keep a separable core library.
 
-### Why integrate into Pigbot?
-- Pigbot already knows:
+### Why integrate into Moltbot?
+- Moltbot already knows:
   - the workspace path (`agents.defaults.workspace`)
   - the session model + heartbeats
   - logging + troubleshooting patterns
 - You want the agent itself to call the tools:
-  - `pigbot memory recall "…" --k 25 --since 30d`
-  - `pigbot memory reflect --since 7d`
+  - `moltbot memory recall "…" --k 25 --since 30d`
+  - `moltbot memory reflect --since 7d`
 
 ### Why still split a library?
 - keep memory logic testable without gateway/runtime

package/docs/gateway/authentication.md

@@ -1,14 +1,14 @@
 ---
-summary: "Model authentication: OAuth, API keys, and Claude Code token reuse"
+summary: "Model authentication: OAuth, API keys, and setup-token"
 read_when:
   - Debugging model auth or OAuth expiry
   - Documenting authentication or credential storage
 ---
 # Authentication
 
-Pigbot supports OAuth and API keys for model providers. For Anthropic
-accounts, we recommend using an **API key**. Pigbot can also reuse Claude Code
-credentials, including the long‑lived token created by `claude setup-token`.
+Moltbot supports OAuth and API keys for model providers. For Anthropic
+accounts, we recommend using an **API key**. For Claude subscription access,
+use the long‑lived token created by `claude setup-token`.
 
 See [/concepts/oauth](/concepts/oauth) for the full OAuth flow and storage
 layout.
@@ -18,18 +18,18 @@ layout.
 If you’re using Anthropic directly, use an API key.
 
 1) Create an API key in the Anthropic Console.
-2) Put it on the **gateway host** (the machine running `pigbot gateway`).
+2) Put it on the **gateway host** (the machine running `moltbot gateway`).
 
 ```bash
 export ANTHROPIC_API_KEY="..."
-pigbot models status
+moltbot models status
 ```
 
 3) If the Gateway runs under systemd/launchd, prefer putting the key in
-`~/.pigbot/.env` so the daemon can read it:
+`~/.clawdbot/.env` so the daemon can read it:
 
 ```bash
-cat >> ~/.pigbot/.env <<'EOF'
+cat >> ~/.clawdbot/.env <<'EOF'
 ANTHROPIC_API_KEY=...
 EOF
 ```
@@ -37,39 +37,36 @@ EOF
 Then restart the daemon (or restart your Gateway process) and re-check:
 
 ```bash
-pigbot models status
-pigbot doctor
+moltbot models status
+moltbot doctor
 ```
 
 If you’d rather not manage env vars yourself, the onboarding wizard can store
-API keys for daemon use: `pigbot onboard`.
+API keys for daemon use: `moltbot onboard`.
 
 See [Help](/help) for details on env inheritance (`env.shellEnv`,
-`~/.pigbot/.env`, systemd/launchd).
+`~/.clawdbot/.env`, systemd/launchd).
 
-## Anthropic: Claude Code CLI setup-token (supported)
+## Anthropic: setup-token (subscription auth)
 
-For Anthropic, the recommended path is an **API key**. If you’re already using
-Claude Code CLI, the setup-token flow is also supported.
-Run it on the **gateway host**:
+For Anthropic, the recommended path is an **API key**. If you’re using a Claude
+subscription, the setup-token flow is also supported. Run it on the **gateway host**:
 
 ```bash
 claude setup-token
 ```
 
-Then verify and sync into Pigbot:
+Then paste it into Moltbot:
 
 ```bash
-pigbot models status
-pigbot doctor
+moltbot models auth setup-token --provider anthropic
 ```
 
-This should create (or refresh) an auth profile like `anthropic:claude-cli` in
-the agent auth store.
+If the token was created on another machine, paste it manually:
 
-Pigbot config sets `auth.profiles["anthropic:claude-cli"].mode` to `"oauth"` so
-the profile accepts both OAuth and setup-token credentials. Older configs that
-used `"token"` are auto-migrated on load.
+```bash
+moltbot models auth paste-token --provider anthropic
+```
 
 If you see an Anthropic error like:
 
@@ -79,46 +76,36 @@ This credential is only authorized for use with Claude Code and cannot be used f
 
 …use an Anthropic API key instead.
 
-Alternative: run the wrapper (also updates Pigbot config):
-
-```bash
-pigbot models auth setup-token --provider anthropic
-```
-
 Manual token entry (any provider; writes `auth-profiles.json` + updates config):
 
 ```bash
-pigbot models auth paste-token --provider anthropic
-pigbot models auth paste-token --provider openrouter
+moltbot models auth paste-token --provider anthropic
+moltbot models auth paste-token --provider openrouter
 ```
 
 Automation-friendly check (exit `1` when expired/missing, `2` when expiring):
 
 ```bash
-pigbot models status --check
+moltbot models status --check
 ```
 
 Optional ops scripts (systemd/Termux) are documented here:
 [/automation/auth-monitoring](/automation/auth-monitoring)
 
-`pigbot models status` loads Claude Code credentials into Pigbot’s
-`auth-profiles.json` and shows expiry (warns within 24h by default).
-`pigbot doctor` also performs the sync when it runs.
-
 > `claude setup-token` requires an interactive TTY.
 
 ## Checking model auth status
 
 ```bash
-pigbot models status
-pigbot doctor
+moltbot models status
+moltbot doctor
 ```
 
 ## Controlling which credential is used
 
 ### Per-session (chat command)
 
-Use `/model <alias-or-id>@<profileId>` to pin a specific provider credential for the current session (example profile ids: `anthropic:claude-cli`, `anthropic:default`).
+Use `/model <alias-or-id>@<profileId>` to pin a specific provider credential for the current session (example profile ids: `anthropic:default`, `anthropic:work`).
 
 Use `/model` (or `/model list`) for a compact picker; use `/model status` for the full view (candidates + next auth profile, plus provider endpoint details when configured).
 
@@ -127,24 +114,13 @@ Use `/model` (or `/model list`) for a compact picker; use `/model status` for th
 Set an explicit auth profile order override for an agent (stored in that agent’s `auth-profiles.json`):
 
 ```bash
-pigbot models auth order get --provider anthropic
-pigbot models auth order set --provider anthropic anthropic:claude-cli
-pigbot models auth order clear --provider anthropic
+moltbot models auth order get --provider anthropic
+moltbot models auth order set --provider anthropic anthropic:default
+moltbot models auth order clear --provider anthropic
 ```
 
 Use `--agent <id>` to target a specific agent; omit it to use the configured default agent.
 
-## How sync works
-
-1. **Claude Code** stores credentials in `~/.claude/.credentials.json` (or
-   Keychain on macOS).
-2. **Pigbot** syncs those into
-   `~/.pigbot/agents/<agentId>/agent/auth-profiles.json` when the auth store is
-   loaded.
-3. Refreshable OAuth profiles can be refreshed automatically on use. Static
-   token profiles (including Claude Code CLI setup-token) are not refreshable by
-   Pigbot.
-
 ## Troubleshooting
 
 ### “No credentials found”
@@ -153,13 +129,13 @@ If the Anthropic token profile is missing, run `claude setup-token` on the
 **gateway host**, then re-check:
 
 ```bash
-pigbot models status
+moltbot models status
 ```
 
 ### Token expiring/expired
 
-Run `pigbot models status` to confirm which profile is expiring. If the profile
-is `anthropic:claude-cli`, rerun `claude setup-token`.
+Run `moltbot models status` to confirm which profile is expiring. If the profile
+is missing, rerun `claude setup-token` and paste the token again.
 
 ## Requirements
 

package/docs/gateway/background-process.md

@@ -7,7 +7,7 @@ read_when:
 
 # Background Exec + Process Tool
 
-Pigbot runs shell commands through the `exec` tool and keeps long‑running tasks in memory. The `process` tool manages those background sessions.
+Moltbot runs shell commands through the `exec` tool and keeps long‑running tasks in memory. The `process` tool manages those background sessions.
 
 ## exec tool
 
@@ -33,7 +33,7 @@ When spawning long-running child processes outside the exec/process tools (for e
 Environment overrides:
 - `PI_BASH_YIELD_MS`: default yield (ms)
 - `PI_BASH_MAX_OUTPUT_CHARS`: in‑memory output cap (chars)
-- `PIGBOT_BASH_PENDING_MAX_OUTPUT_CHARS`: pending stdout/stderr cap per stream (chars)
+- `CLAWDBOT_BASH_PENDING_MAX_OUTPUT_CHARS`: pending stdout/stderr cap per stream (chars)
 - `PI_BASH_JOB_TTL_MS`: TTL for finished sessions (ms, bounded to 1m–3h)
 
 Config (preferred):

package/docs/gateway/bonjour.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Bonjour / mDNS discovery
 
-Pigbot uses Bonjour (mDNS / DNS‑SD) as a **LAN‑only convenience** to discover
+Moltbot uses Bonjour (mDNS / DNS‑SD) as a **LAN‑only convenience** to discover
 an active Gateway (WebSocket endpoint). It is best‑effort and does **not** replace SSH or
 Tailnet-based connectivity.
 
@@ -19,38 +19,38 @@ boundary. You can keep the same discovery UX by switching to **unicast DNS‑SD*
 High‑level steps:
 
 1) Run a DNS server on the gateway host (reachable over Tailnet).
-2) Publish DNS‑SD records for `_pigbot-gw._tcp` under a dedicated zone
-   (example: `pigbot.internal.`).
-3) Configure Tailscale **split DNS** so `pigbot.internal` resolves via that
+2) Publish DNS‑SD records for `_moltbot-gw._tcp` under a dedicated zone
+   (example: `moltbot.internal.`).
+3) Configure Tailscale **split DNS** so `moltbot.internal` resolves via that
    DNS server for clients (including iOS).
 
-Pigbot standardizes on `pigbot.internal.` for this mode. iOS/Android nodes
-browse both `local.` and `pigbot.internal.` automatically.
+Moltbot standardizes on `moltbot.internal.` for this mode. iOS/Android nodes
+browse both `local.` and `moltbot.internal.` automatically.
 
 ### Gateway config (recommended)
 
 ```json5
 {
   gateway: { bind: "tailnet" }, // tailnet-only (recommended)
-  discovery: { wideArea: { enabled: true } } // enables pigbot.internal DNS-SD publishing
+  discovery: { wideArea: { enabled: true } } // enables moltbot.internal DNS-SD publishing
 }
 ```
 
 ### One‑time DNS server setup (gateway host)
 
 ```bash
-pigbot dns setup --apply
+moltbot dns setup --apply
 ```
 
 This installs CoreDNS and configures it to:
 - listen on port 53 only on the gateway’s Tailscale interfaces
-- serve `pigbot.internal.` from `~/.pigbot/dns/pigbot.internal.db`
+- serve `moltbot.internal.` from `~/.clawdbot/dns/moltbot.internal.db`
 
 Validate from a tailnet‑connected machine:
 
 ```bash
-dns-sd -B _pigbot-gw._tcp pigbot.internal.
-dig @<TAILNET_IPV4> -p 53 _pigbot-gw._tcp.pigbot.internal PTR +short
+dns-sd -B _moltbot-gw._tcp moltbot.internal.
+dig @<TAILNET_IPV4> -p 53 _moltbot-gw._tcp.clawdbot.internal PTR +short
 ```
 
 ### Tailscale DNS settings
@@ -58,10 +58,10 @@ dig @<TAILNET_IPV4> -p 53 _pigbot-gw._tcp.pigbot.internal PTR +short
 In the Tailscale admin console:
 
 - Add a nameserver pointing at the gateway’s tailnet IP (UDP/TCP 53).
-- Add split DNS so the domain `pigbot.internal` uses that nameserver.
+- Add split DNS so the domain `moltbot.internal` uses that nameserver.
 
 Once clients accept tailnet DNS, iOS nodes can browse
-`_pigbot-gw._tcp` in `pigbot.internal.` without multicast.
+`_moltbot-gw._tcp` in `moltbot.internal.` without multicast.
 
 ### Gateway listener security (recommended)
 
@@ -69,16 +69,16 @@ The Gateway WS port (default `18789`) binds to loopback by default. For LAN/tail
 access, bind explicitly and keep auth enabled.
 
 For tailnet‑only setups:
-- Set `gateway.bind: "tailnet"` in `~/.pigbot/pigbot.json`.
+- Set `gateway.bind: "tailnet"` in `~/.clawdbot/moltbot.json`.
 - Restart the Gateway (or restart the macOS menubar app).
 
 ## What advertises
 
-Only the Gateway advertises `_pigbot-gw._tcp`.
+Only the Gateway advertises `_moltbot-gw._tcp`.
 
 ## Service types
 
-- `_pigbot-gw._tcp` — gateway transport beacon (used by macOS/iOS/Android nodes).
+- `_moltbot-gw._tcp` — gateway transport beacon (used by macOS/iOS/Android nodes).
 
 ## TXT keys (non‑secret hints)
 
@@ -93,7 +93,7 @@ The Gateway advertises small non‑secret hints to make UI flows convenient:
 - `canvasPort=<port>` (only when the canvas host is enabled; default `18793`)
 - `sshPort=<port>` (defaults to 22 when not overridden)
 - `transport=gateway`
-- `cliPath=<path>` (optional; absolute path to a runnable `pigbot` entrypoint)
+- `cliPath=<path>` (optional; absolute path to a runnable `moltbot` entrypoint)
 - `tailnetDns=<magicdns>` (optional hint when Tailnet is available)
 
 ## Debugging on macOS
@@ -102,11 +102,11 @@ Useful built‑in tools:
 
 - Browse instances:
   ```bash
-  dns-sd -B _pigbot-gw._tcp local.
+  dns-sd -B _moltbot-gw._tcp local.
   ```
 - Resolve one instance (replace `<instance>`):
   ```bash
-  dns-sd -L "<instance>" _pigbot-gw._tcp local.
+  dns-sd -L "<instance>" _moltbot-gw._tcp local.
   ```
 
 If browsing works but resolving fails, you’re usually hitting a LAN policy or
@@ -123,7 +123,7 @@ The Gateway writes a rolling log file (printed on startup as
 
 ## Debugging on iOS node
 
-The iOS node uses `NWBrowser` to discover `_pigbot-gw._tcp`.
+The iOS node uses `NWBrowser` to discover `_moltbot-gw._tcp`.
 
 To capture logs:
 - Settings → Gateway → Advanced → **Discovery Debug Logs**
@@ -150,11 +150,11 @@ sequences (e.g. spaces become `\032`).
 
 ## Disabling / configuration
 
-- `PIGBOT_DISABLE_BONJOUR=1` disables advertising.
-- `gateway.bind` in `~/.pigbot/pigbot.json` controls the Gateway bind mode.
-- `PIGBOT_SSH_PORT` overrides the SSH port advertised in TXT.
-- `PIGBOT_TAILNET_DNS` publishes a MagicDNS hint in TXT.
-- `PIGBOT_CLI_PATH` overrides the advertised CLI path.
+- `CLAWDBOT_DISABLE_BONJOUR=1` disables advertising.
+- `gateway.bind` in `~/.clawdbot/moltbot.json` controls the Gateway bind mode.
+- `CLAWDBOT_SSH_PORT` overrides the SSH port advertised in TXT.
+- `CLAWDBOT_TAILNET_DNS` publishes a MagicDNS hint in TXT.
+- `CLAWDBOT_CLI_PATH` overrides the advertised CLI path.
 
 ## Related docs
 

package/docs/gateway/bridge-protocol.md

@@ -14,7 +14,7 @@ should use the unified Gateway WebSocket protocol instead.
 If you are building an operator or node client, use the
 [Gateway protocol](/gateway/protocol).
 
-**Note:** Current Pigbot builds no longer ship the TCP bridge listener; this document is kept for historical reference.
+**Note:** Current Moltbot builds no longer ship the TCP bridge listener; this document is kept for historical reference.
 Legacy `bridge.*` config keys are no longer part of the config schema.
 
 ## Why we have both
@@ -74,7 +74,7 @@ Payload fields (all optional unless noted):
 ## Tailnet usage
 
 - Bind the bridge to a tailnet IP: `bridge.bind: "tailnet"` in
-  `~/.pigbot/pigbot.json`.
+  `~/.clawdbot/moltbot.json`.
 - Clients connect via MagicDNS name or tailnet IP.
 - Bonjour does **not** cross networks; use manual host/port or wide-area DNS‑SD
   when needed.

package/docs/gateway/cli-backends.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # CLI backends (fallback runtime)
 
-Pigbot can run **local AI CLIs** as a **text-only fallback** when API providers are down,
+Moltbot can run **local AI CLIs** as a **text-only fallback** when API providers are down,
 rate-limited, or temporarily misbehaving. This is intentionally conservative:
 
 - **Tools are disabled** (no tool calls).
@@ -20,16 +20,16 @@ want “always works” text responses without relying on external APIs.
 
 ## Beginner-friendly quick start
 
-You can use Claude Code CLI **without any config** (Pigbot ships a built-in default):
+You can use Claude Code CLI **without any config** (Moltbot ships a built-in default):
 
 ```bash
-pigbot agent --message "hi" --model claude-cli/opus-4.5
+moltbot agent --message "hi" --model claude-cli/opus-4.5
 ```
 
 Codex CLI also works out of the box:
 
 ```bash
-pigbot agent --message "hi" --model codex-cli/gpt-5.2-codex
+moltbot agent --message "hi" --model codex-cli/gpt-5.2-codex
 ```
 
 If your gateway runs under launchd/systemd and PATH is minimal, add just the
@@ -76,7 +76,7 @@ Add a CLI backend to your fallback list so it only runs when primary models fail
 
 Notes:
 - If you use `agents.defaults.models` (allowlist), you must include `claude-cli/...`.
-- If the primary provider fails (auth, rate limits, timeouts), Pigbot will
+- If the primary provider fails (auth, rate limits, timeouts), Moltbot will
   try the CLI backend next.
 
 ## Configuration overview
@@ -132,7 +132,7 @@ The provider id becomes the left side of your model ref:
 ## How it works
 
 1) **Selects a backend** based on the provider prefix (`claude-cli/...`).
-2) **Builds a system prompt** using the same Pigbot prompt + workspace context.
+2) **Builds a system prompt** using the same Moltbot prompt + workspace context.
 3) **Executes the CLI** with a session id (if supported) so history stays consistent.
 4) **Parses output** (JSON or plain text) and returns the final text.
 5) **Persists session ids** per backend, so follow-ups reuse the same CLI session.
@@ -159,8 +159,8 @@ imageArg: "--image",
 imageMode: "repeat"
 ```
 
-Pigbot will write base64 images to temp files. If `imageArg` is set, those
-paths are passed as CLI args. If `imageArg` is missing, Pigbot appends the
+Moltbot will write base64 images to temp files. If `imageArg` is set, those
+paths are passed as CLI args. If `imageArg` is missing, Moltbot appends the
 file paths to the prompt (path injection), which is enough for CLIs that auto-
 load local files from plain paths (Claude Code CLI behavior).
 
@@ -178,17 +178,18 @@ Input modes:
 
 ## Defaults (built-in)
 
-Pigbot ships a default for `claude-cli`:
+Moltbot ships a default for `claude-cli`:
 
 - `command: "claude"`
 - `args: ["-p", "--output-format", "json", "--dangerously-skip-permissions"]`
+- `resumeArgs: ["-p", "--output-format", "json", "--dangerously-skip-permissions", "--resume", "{sessionId}"]`
 - `modelArg: "--model"`
 - `systemPromptArg: "--append-system-prompt"`
 - `sessionArg: "--session-id"`
 - `systemPromptWhen: "first"`
 - `sessionMode: "always"`
 
-Pigbot also ships a default for `codex-cli`:
+Moltbot also ships a default for `codex-cli`:
 
 - `command: "codex"`
 - `args: ["exec","--json","--color","never","--sandbox","read-only","--skip-git-repo-check"]`
@@ -203,12 +204,12 @@ Override only if needed (common: absolute `command` path).
 
 ## Limitations
 
-- **No Pigbot tools** (the CLI backend never receives tool calls). Some CLIs
+- **No Moltbot tools** (the CLI backend never receives tool calls). Some CLIs
   may still run their own agent tooling.
 - **No streaming** (CLI output is collected then returned).
 - **Structured outputs** depend on the CLI’s JSON format.
 - **Codex CLI sessions** resume via text output (no JSONL), which is less
-  structured than the initial `--json` run. Pigbot sessions still work
+  structured than the initial `--json` run. Moltbot sessions still work
   normally.
 
 ## Troubleshooting

package/docs/gateway/configuration-examples.md

@@ -1,9 +1,9 @@
 ---
-summary: "Schema-accurate configuration examples for common Pigbot setups"
+summary: "Schema-accurate configuration examples for common Moltbot setups"
 read_when:
-  - Learning how to configure Pigbot
+  - Learning how to configure Moltbot
   - Looking for configuration examples
-  - Setting up Pigbot for the first time
+  - Setting up Moltbot for the first time
 ---
 # Configuration Examples
 
@@ -19,7 +19,7 @@ Examples below are aligned with the current config schema. For the exhaustive re
 }
 ```
 
-Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
+Save to `~/.clawdbot/moltbot.json` and you can DM the bot from that number.
 
 ### Recommended starter
 ```json5
@@ -85,7 +85,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
   // Logging
   logging: {
     level: "info",
-    file: "/tmp/pigbot/pigbot.log",
+    file: "/tmp/moltbot/moltbot.log",
     consoleLevel: "info",
     consoleStyle: "pretty",
     redactSensitive: "tools"
@@ -93,7 +93,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
 
   // Message formatting
   messages: {
-    messagePrefix: "[pigbot]",
+    messagePrefix: "[moltbot]",
     responsePrefix: ">",
     ackReaction: "👀",
     ackReactionScope: "group-mentions"
@@ -102,7 +102,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
   // Routing + queue
   routing: {
     groupChat: {
-      mentionPatterns: ["@clawd", "pigbot"],
+      mentionPatterns: ["@clawd", "moltbot"],
       historyLimit: 50
     },
     queue: {
@@ -155,7 +155,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
       discord: { mode: "idle", idleMinutes: 10080 }
     },
     resetTriggers: ["/new", "/reset"],
-    store: "~/.pigbot/agents/default/sessions/sessions.json",
+    store: "~/.clawdbot/agents/default/sessions/sessions.json",
     typingIntervalSeconds: 5,
     sendPolicy: {
       default: "allow",
@@ -272,9 +272,9 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
       sandbox: {
         mode: "non-main",
         perSession: true,
-        workspaceRoot: "~/.pigbot/sandboxes",
+        workspaceRoot: "~/.clawdbot/sandboxes",
         docker: {
-          image: "pigbot-sandbox:bookworm-slim",
+          image: "moltbot-sandbox:bookworm-slim",
           workdir: "/workspace",
           readOnlyRoot: true,
           tmpfs: ["/tmp", "/var/tmp", "/run"],
@@ -339,7 +339,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
   // Cron jobs
   cron: {
     enabled: true,
-    store: "~/.pigbot/cron/cron.json",
+    store: "~/.clawdbot/cron/cron.json",
     maxConcurrentRuns: 2
   },
 
@@ -349,7 +349,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
     path: "/hooks",
     token: "shared-secret",
     presets: ["gmail"],
-    transformsDir: "~/.pigbot/hooks",
+    transformsDir: "~/.clawdbot/hooks",
     mappings: [
       {
         id: "gmail-hook",
@@ -369,7 +369,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
       }
     ],
     gmail: {
-      account: "pigbot@gmail.com",
+      account: "moltbot@gmail.com",
       label: "INBOX",
       topic: "projects/<project-id>/topics/gog-gmail-watch",
       subscription: "gog-gmail-watch-push",
@@ -388,7 +388,7 @@ Save to `~/.pigbot/pigbot.json` and you can DM the bot from that number.
     mode: "local",
     port: 18789,
     bind: "loopback",
-    controlUi: { enabled: true, basePath: "/pigbot" },
+    controlUi: { enabled: true, basePath: "/moltbot" },
     auth: {
       mode: "token",
       token: "gateway-token",