@gguf/pigbot 0.0.1 → 0.0.3

package/docs/cli/plugins.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot plugins` (list, install, enable/disable, doctor)"
+summary: "CLI reference for `moltbot plugins` (list, install, enable/disable, doctor)"
 read_when:
   - You want to install or manage in-process Gateway plugins
   - You want to debug plugin load failures
 ---
 
-# `pigbot plugins`
+# `moltbot plugins`
 
 Manage Gateway plugins/extensions (loaded in-process).
 
@@ -17,26 +17,26 @@ Related:
 ## Commands
 
 ```bash
-pigbot plugins list
-pigbot plugins info <id>
-pigbot plugins enable <id>
-pigbot plugins disable <id>
-pigbot plugins doctor
-pigbot plugins update <id>
-pigbot plugins update --all
+moltbot plugins list
+moltbot plugins info <id>
+moltbot plugins enable <id>
+moltbot plugins disable <id>
+moltbot plugins doctor
+moltbot plugins update <id>
+moltbot plugins update --all
 ```
 
-Bundled plugins ship with Pigbot but start disabled. Use `plugins enable` to
+Bundled plugins ship with Moltbot but start disabled. Use `plugins enable` to
 activate them.
 
-All plugins must ship a `pigbot.plugin.json` file with an inline JSON Schema
+All plugins must ship a `moltbot.plugin.json` file with an inline JSON Schema
 (`configSchema`, even if empty). Missing/invalid manifests or schemas prevent
 the plugin from loading and fail config validation.
 
 ### Install
 
 ```bash
-pigbot plugins install <path-or-spec>
+moltbot plugins install <path-or-spec>
 ```
 
 Security note: treat plugin installs like running code. Prefer pinned versions.
@@ -46,15 +46,15 @@ Supported archives: `.zip`, `.tgz`, `.tar.gz`, `.tar`.
 Use `--link` to avoid copying a local directory (adds to `plugins.load.paths`):
 
 ```bash
-pigbot plugins install -l ./my-plugin
+moltbot plugins install -l ./my-plugin
 ```
 
 ### Update
 
 ```bash
-pigbot plugins update <id>
-pigbot plugins update --all
-pigbot plugins update <id> --dry-run
+moltbot plugins update <id>
+moltbot plugins update --all
+moltbot plugins update <id> --dry-run
 ```
 
 Updates only apply to plugins installed from npm (tracked in `plugins.installs`).

package/docs/cli/reset.md

@@ -1,17 +1,17 @@
 ---
-summary: "CLI reference for `pigbot reset` (reset local state/config)"
+summary: "CLI reference for `moltbot reset` (reset local state/config)"
 read_when:
   - You want to wipe local state while keeping the CLI installed
   - You want a dry-run of what would be removed
 ---
 
-# `pigbot reset`
+# `moltbot reset`
 
 Reset local config/state (keeps the CLI installed).
 
 ```bash
-pigbot reset
-pigbot reset --dry-run
-pigbot reset --scope config+creds+sessions --yes --non-interactive
+moltbot reset
+moltbot reset --dry-run
+moltbot reset --scope config+creds+sessions --yes --non-interactive
 ```
 

package/docs/cli/sandbox.md

@@ -11,29 +11,29 @@ Manage Docker-based sandbox containers for isolated agent execution.
 
 ## Overview
 
-Pigbot can run agents in isolated Docker containers for security. The `sandbox` commands help you manage these containers, especially after updates or configuration changes.
+Moltbot can run agents in isolated Docker containers for security. The `sandbox` commands help you manage these containers, especially after updates or configuration changes.
 
 ## Commands
 
-### `pigbot sandbox explain`
+### `moltbot sandbox explain`
 
 Inspect the **effective** sandbox mode/scope/workspace access, sandbox tool policy, and elevated gates (with fix-it config key paths).
 
 ```bash
-pigbot sandbox explain
-pigbot sandbox explain --session agent:main:main
-pigbot sandbox explain --agent work
-pigbot sandbox explain --json
+moltbot sandbox explain
+moltbot sandbox explain --session agent:main:main
+moltbot sandbox explain --agent work
+moltbot sandbox explain --json
 ```
 
-### `pigbot sandbox list`
+### `moltbot sandbox list`
 
 List all sandbox containers with their status and configuration.
 
 ```bash
-pigbot sandbox list
-pigbot sandbox list --browser  # List only browser containers
-pigbot sandbox list --json     # JSON output
+moltbot sandbox list
+moltbot sandbox list --browser  # List only browser containers
+moltbot sandbox list --json     # JSON output
 ```
 
 **Output includes:**
@@ -43,16 +43,16 @@ pigbot sandbox list --json     # JSON output
 - Idle time (time since last use)
 - Associated session/agent
 
-### `pigbot sandbox recreate`
+### `moltbot sandbox recreate`
 
 Remove sandbox containers to force recreation with updated images/config.
 
 ```bash
-pigbot sandbox recreate --all                # Recreate all containers
-pigbot sandbox recreate --session main       # Specific session
-pigbot sandbox recreate --agent mybot        # Specific agent
-pigbot sandbox recreate --browser            # Only browser containers
-pigbot sandbox recreate --all --force        # Skip confirmation
+moltbot sandbox recreate --all                # Recreate all containers
+moltbot sandbox recreate --session main       # Specific session
+moltbot sandbox recreate --agent mybot        # Specific agent
+moltbot sandbox recreate --browser            # Only browser containers
+moltbot sandbox recreate --all --force        # Skip confirmation
 ```
 
 **Options:**
@@ -70,14 +70,14 @@ pigbot sandbox recreate --all --force        # Skip confirmation
 
 ```bash
 # Pull new image
-docker pull pigbot-sandbox:latest
-docker tag pigbot-sandbox:latest pigbot-sandbox:bookworm-slim
+docker pull moltbot-sandbox:latest
+docker tag moltbot-sandbox:latest moltbot-sandbox:bookworm-slim
 
 # Update config to use new image
 # Edit config: agents.defaults.sandbox.docker.image (or agents.list[].sandbox.docker.image)
 
 # Recreate containers
-pigbot sandbox recreate --all
+moltbot sandbox recreate --all
 ```
 
 ### After changing sandbox configuration
@@ -86,15 +86,15 @@ pigbot sandbox recreate --all
 # Edit config: agents.defaults.sandbox.* (or agents.list[].sandbox.*)
 
 # Recreate to apply new config
-pigbot sandbox recreate --all
+moltbot sandbox recreate --all
 ```
 
 ### After changing setupCommand
 
 ```bash
-pigbot sandbox recreate --all
+moltbot sandbox recreate --all
 # or just one agent:
-pigbot sandbox recreate --agent family
+moltbot sandbox recreate --agent family
 ```
 
 
@@ -102,7 +102,7 @@ pigbot sandbox recreate --agent family
 
 ```bash
 # Update only one agent's containers
-pigbot sandbox recreate --agent alfred
+moltbot sandbox recreate --agent alfred
 ```
 
 ## Why is this needed?
@@ -112,14 +112,14 @@ pigbot sandbox recreate --agent alfred
 - Containers are only pruned after 24h of inactivity
 - Regularly-used agents keep old containers running indefinitely
 
-**Solution:** Use `pigbot sandbox recreate` to force removal of old containers. They'll be recreated automatically with current settings when next needed.
+**Solution:** Use `moltbot sandbox recreate` to force removal of old containers. They'll be recreated automatically with current settings when next needed.
 
-Tip: prefer `pigbot sandbox recreate` over manual `docker rm`. It uses the
+Tip: prefer `moltbot sandbox recreate` over manual `docker rm`. It uses the
 Gateway’s container naming and avoids mismatches when scope/session keys change.
 
 ## Configuration
 
-Sandbox settings live in `~/.pigbot/pigbot.json` under `agents.defaults.sandbox` (per-agent overrides go in `agents.list[].sandbox`):
+Sandbox settings live in `~/.clawdbot/moltbot.json` under `agents.defaults.sandbox` (per-agent overrides go in `agents.list[].sandbox`):
 
 ```jsonc
 {
@@ -129,8 +129,8 @@ Sandbox settings live in `~/.pigbot/pigbot.json` under `agents.defaults.sandbox`
         "mode": "all",                    // off, non-main, all
         "scope": "agent",                 // session, agent, shared
         "docker": {
-          "image": "pigbot-sandbox:bookworm-slim",
-          "containerPrefix": "pigbot-sbx-"
+          "image": "moltbot-sandbox:bookworm-slim",
+          "containerPrefix": "moltbot-sbx-"
           // ... more Docker options
         },
         "prune": {

package/docs/cli/security.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot security` (audit and fix common security footguns)"
+summary: "CLI reference for `moltbot security` (audit and fix common security footguns)"
 read_when:
   - You want to run a quick security audit on config/state
   - You want to apply safe “fix” suggestions (chmod, tighten defaults)
 ---
 
-# `pigbot security`
+# `moltbot security`
 
 Security tools (audit + optional fixes).
 
@@ -15,9 +15,9 @@ Related:
 ## Audit
 
 ```bash
-pigbot security audit
-pigbot security audit --deep
-pigbot security audit --fix
+moltbot security audit
+moltbot security audit --deep
+moltbot security audit --fix
 ```
 
 The audit warns when multiple DM senders share the main session and recommends `session.dmScope="per-channel-peer"` for shared inboxes.

package/docs/cli/sessions.md

@@ -1,16 +1,16 @@
 ---
-summary: "CLI reference for `pigbot sessions` (list stored sessions + usage)"
+summary: "CLI reference for `moltbot sessions` (list stored sessions + usage)"
 read_when:
   - You want to list stored sessions and see recent activity
 ---
 
-# `pigbot sessions`
+# `moltbot sessions`
 
 List stored conversation sessions.
 
 ```bash
-pigbot sessions
-pigbot sessions --active 120
-pigbot sessions --json
+moltbot sessions
+moltbot sessions --active 120
+moltbot sessions --json
 ```
 

package/docs/cli/setup.md

@@ -1,13 +1,13 @@
 ---
-summary: "CLI reference for `pigbot setup` (initialize config + workspace)"
+summary: "CLI reference for `moltbot setup` (initialize config + workspace)"
 read_when:
   - You’re doing first-run setup without the full onboarding wizard
   - You want to set the default workspace path
 ---
 
-# `pigbot setup`
+# `moltbot setup`
 
-Initialize `~/.pigbot/pigbot.json` and the agent workspace.
+Initialize `~/.clawdbot/moltbot.json` and the agent workspace.
 
 Related:
 - Getting started: [Getting started](/start/getting-started)
@@ -16,13 +16,13 @@ Related:
 ## Examples
 
 ```bash
-pigbot setup
-pigbot setup --workspace ~/clawd
+moltbot setup
+moltbot setup --workspace ~/clawd
 ```
 
 To run the wizard via setup:
 
 ```bash
-pigbot setup --wizard
+moltbot setup --wizard
 ```
 

package/docs/cli/skills.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot skills` (list/info/check) and skill eligibility"
+summary: "CLI reference for `moltbot skills` (list/info/check) and skill eligibility"
 read_when:
   - You want to see which skills are available and ready to run
   - You want to debug missing binaries/env/config for skills
 ---
 
-# `pigbot skills`
+# `moltbot skills`
 
 Inspect skills (bundled + workspace + managed overrides) and see what’s eligible vs missing requirements.
 
@@ -17,9 +17,9 @@ Related:
 ## Commands
 
 ```bash
-pigbot skills list
-pigbot skills list --eligible
-pigbot skills info <name>
-pigbot skills check
+moltbot skills list
+moltbot skills list --eligible
+moltbot skills info <name>
+moltbot skills check
 ```
 

package/docs/cli/status.md

@@ -1,19 +1,19 @@
 ---
-summary: "CLI reference for `pigbot status` (diagnostics, probes, usage snapshots)"
+summary: "CLI reference for `moltbot status` (diagnostics, probes, usage snapshots)"
 read_when:
   - You want a quick diagnosis of channel health + recent session recipients
   - You want a pasteable “all” status for debugging
 ---
 
-# `pigbot status`
+# `moltbot status`
 
 Diagnostics for channels + sessions.
 
 ```bash
-pigbot status
-pigbot status --all
-pigbot status --deep
-pigbot status --usage
+moltbot status
+moltbot status --all
+moltbot status --deep
+moltbot status --usage
 ```
 
 Notes:
@@ -21,4 +21,4 @@ Notes:
 - Output includes per-agent session stores when multiple agents are configured.
 - Overview includes Gateway + node host service install/runtime status when available.
 - Overview includes update channel + git SHA (for source checkouts).
-- Update info surfaces in the Overview; if an update is available, status prints a hint to run `pigbot update` (see [Updating](/install/updating)).
+- Update info surfaces in the Overview; if an update is available, status prints a hint to run `moltbot update` (see [Updating](/install/updating)).

package/docs/cli/system.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `pigbot system` (system events, heartbeat, presence)"
+summary: "CLI reference for `moltbot system` (system events, heartbeat, presence)"
 read_when:
   - You want to enqueue a system event without creating a cron job
   - You need to enable or disable heartbeats
   - You want to inspect system presence entries
 ---
 
-# `pigbot system`
+# `moltbot system`
 
 System-level helpers for the Gateway: enqueue system events, control heartbeats,
 and view presence.
@@ -14,10 +14,10 @@ and view presence.
 ## Common commands
 
 ```bash
-pigbot system event --text "Check for urgent follow-ups" --mode now
-pigbot system heartbeat enable
-pigbot system heartbeat last
-pigbot system presence
+moltbot system event --text "Check for urgent follow-ups" --mode now
+moltbot system heartbeat enable
+moltbot system heartbeat last
+moltbot system presence
 ```
 
 ## `system event`

package/docs/cli/tui.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot tui` (terminal UI connected to the Gateway)"
+summary: "CLI reference for `moltbot tui` (terminal UI connected to the Gateway)"
 read_when:
   - You want a terminal UI for the Gateway (remote-friendly)
   - You want to pass url/token/session from scripts
 ---
 
-# `pigbot tui`
+# `moltbot tui`
 
 Open the terminal UI connected to the Gateway.
 
@@ -15,8 +15,8 @@ Related:
 ## Examples
 
 ```bash
-pigbot tui
-pigbot tui --url ws://127.0.0.1:18789 --token <token>
-pigbot tui --session main --deliver
+moltbot tui
+moltbot tui --url ws://127.0.0.1:18789 --token <token>
+moltbot tui --session main --deliver
 ```
 

package/docs/cli/uninstall.md

@@ -1,17 +1,17 @@
 ---
-summary: "CLI reference for `pigbot uninstall` (remove gateway service + local data)"
+summary: "CLI reference for `moltbot uninstall` (remove gateway service + local data)"
 read_when:
   - You want to remove the gateway service and/or local state
   - You want a dry-run first
 ---
 
-# `pigbot uninstall`
+# `moltbot uninstall`
 
 Uninstall the gateway service + local data (CLI remains).
 
 ```bash
-pigbot uninstall
-pigbot uninstall --all --yes
-pigbot uninstall --dry-run
+moltbot uninstall
+moltbot uninstall --all --yes
+moltbot uninstall --dry-run
 ```
 

package/docs/cli/update.md

@@ -1,28 +1,28 @@
 ---
-summary: "CLI reference for `pigbot update` (safe-ish source update + gateway auto-restart)"
+summary: "CLI reference for `moltbot update` (safe-ish source update + gateway auto-restart)"
 read_when:
   - You want to update a source checkout safely
   - You need to understand `--update` shorthand behavior
 ---
 
-# `pigbot update`
+# `moltbot update`
 
-Safely update Pigbot and switch between stable/beta/dev channels.
+Safely update Moltbot and switch between stable/beta/dev channels.
 
 If you installed via **npm/pnpm** (global install, no git metadata), updates happen via the package manager flow in [Updating](/install/updating).
 
 ## Usage
 
 ```bash
-pigbot update
-pigbot update status
-pigbot update wizard
-pigbot update --channel beta
-pigbot update --channel dev
-pigbot update --tag beta
-pigbot update --no-restart
-pigbot update --json
-pigbot --update
+moltbot update
+moltbot update status
+moltbot update wizard
+moltbot update --channel beta
+moltbot update --channel dev
+moltbot update --tag beta
+moltbot update --no-restart
+moltbot update --json
+moltbot --update
 ```
 
 ## Options
@@ -40,9 +40,9 @@ Note: downgrades require confirmation because older versions can break configura
 Show the active update channel + git tag/branch/SHA (for source checkouts), plus update availability.
 
 ```bash
-pigbot update status
-pigbot update status --json
-pigbot update status --timeout 10
+moltbot update status
+moltbot update status --json
+moltbot update status --timeout 10
 ```
 
 Options:
@@ -57,10 +57,10 @@ offers to create one.
 
 ## What it does
 
-When you switch channels explicitly (`--channel ...`), Pigbot also keeps the
+When you switch channels explicitly (`--channel ...`), Moltbot also keeps the
 install method aligned:
 
-- `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.
 
@@ -81,16 +81,16 @@ High-level:
 5. Rebases onto the selected commit (dev only).
 6. Installs deps (pnpm preferred; npm fallback).
 7. Builds + builds the Control UI.
-8. Runs `pigbot doctor` as the final “safe update” check.
+8. Runs `moltbot doctor` as the final “safe update” check.
 9. Syncs plugins to the active channel (dev uses bundled extensions; stable/beta uses npm) and updates npm-installed plugins.
 
 ## `--update` shorthand
 
-`pigbot --update` rewrites to `pigbot update` (useful for shells and launcher scripts).
+`moltbot --update` rewrites to `moltbot update` (useful for shells and launcher scripts).
 
 ## See also
 
-- `pigbot doctor` (offers to run update first on git checkouts)
+- `moltbot doctor` (offers to run update first on git checkouts)
 - [Development channels](/install/development-channels)
 - [Updating](/install/updating)
 - [CLI reference](/cli)

package/docs/cli/voicecall.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot voicecall` (voice-call plugin command surface)"
+summary: "CLI reference for `moltbot voicecall` (voice-call plugin command surface)"
 read_when:
   - You use the voice-call plugin and want the CLI entry points
   - You want quick examples for `voicecall call|continue|status|tail|expose`
 ---
 
-# `pigbot voicecall`
+# `moltbot voicecall`
 
 `voicecall` is a plugin-provided command. It only appears if the voice-call plugin is installed and enabled.
 
@@ -15,18 +15,18 @@ Primary doc:
 ## Common commands
 
 ```bash
-pigbot voicecall status --call-id <id>
-pigbot voicecall call --to "+15555550123" --message "Hello" --mode notify
-pigbot voicecall continue --call-id <id> --message "Any questions?"
-pigbot voicecall end --call-id <id>
+moltbot voicecall status --call-id <id>
+moltbot voicecall call --to "+15555550123" --message "Hello" --mode notify
+moltbot voicecall continue --call-id <id> --message "Any questions?"
+moltbot voicecall end --call-id <id>
 ```
 
 ## Exposing webhooks (Tailscale)
 
 ```bash
-pigbot voicecall expose --mode serve
-pigbot voicecall expose --mode funnel
-pigbot voicecall unexpose
+moltbot voicecall expose --mode serve
+moltbot voicecall expose --mode funnel
+moltbot voicecall unexpose
 ```
 
 Security note: only expose the webhook endpoint to networks you trust. Prefer Tailscale Serve over Funnel when possible.

package/docs/cli/webhooks.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `pigbot webhooks` (webhook helpers + Gmail Pub/Sub)"
+summary: "CLI reference for `moltbot webhooks` (webhook helpers + Gmail Pub/Sub)"
 read_when:
-  - You want to wire Gmail Pub/Sub events into Pigbot
+  - You want to wire Gmail Pub/Sub events into Moltbot
   - You want webhook helper commands
 ---
 
-# `pigbot webhooks`
+# `moltbot webhooks`
 
 Webhook helpers and integrations (Gmail Pub/Sub, webhook helpers).
 
@@ -16,8 +16,8 @@ Related:
 ## Gmail
 
 ```bash
-pigbot webhooks gmail setup --account you@example.com
-pigbot webhooks gmail run
+moltbot webhooks gmail setup --account you@example.com
+moltbot webhooks gmail run
 ```
 
 See [Gmail Pub/Sub documentation](/automation/gmail-pubsub) for details.

package/docs/concepts/agent-loop.md

@@ -3,13 +3,13 @@ summary: "Agent loop lifecycle, streams, and wait semantics"
 read_when:
   - You need an exact walkthrough of the agent loop or lifecycle events
 ---
-# Agent Loop (Pigbot)
+# Agent Loop (Moltbot)
 
 An agentic loop is the full “real” run of an agent: intake → context assembly → model inference →
 tool execution → streaming replies → persistence. It’s the authoritative path that turns a message
 into actions and a final reply, while keeping session state consistent.
 
-In Pigbot, a loop is a single, serialized run per session that emits lifecycle and stream events
+In Moltbot, a loop is a single, serialized run per session that emits lifecycle and stream events
 as the model thinks, calls tools, and streams output. This doc explains how that authentic loop is
 wired end-to-end.
 
@@ -30,7 +30,7 @@ wired end-to-end.
    - subscribes to pi events and streams assistant/tool deltas
    - enforces timeout -> aborts run if exceeded
    - returns payloads + usage metadata
-4) `subscribeEmbeddedPiSession` bridges pi-agent-core events to Pigbot `agent` stream:
+4) `subscribeEmbeddedPiSession` bridges pi-agent-core events to Moltbot `agent` stream:
    - tool events => `stream: "tool"`
    - assistant deltas => `stream: "assistant"`
    - lifecycle events => `stream: "lifecycle"` (`phase: "start" | "end" | "error"`)
@@ -51,12 +51,12 @@ wired end-to-end.
 - A session write lock is acquired; `SessionManager` is opened and prepared before streaming.
 
 ## Prompt assembly + system prompt
-- System prompt is built from Pigbot’s base prompt, skills prompt, bootstrap context, and per-run overrides.
+- System prompt is built from Moltbot’s base prompt, skills prompt, bootstrap context, and per-run overrides.
 - Model-specific limits and compaction reserve tokens are enforced.
 - See [System prompt](/concepts/system-prompt) for what the model sees.
 
 ## Hook points (where you can intercept)
-Pigbot has two hook systems:
+Moltbot has two hook systems:
 - **Internal hooks** (Gateway hooks): event-driven scripts for commands and lifecycle events.
 - **Plugin hooks**: extension points inside the agent/tool lifecycle and gateway pipeline.