@gguf/pigbot 0.0.5 → 0.0.7

package/docs/help/troubleshooting.md

@@ -12,22 +12,22 @@ read_when:
 Run these in order:
 
 ```bash
-moltbot status
-moltbot status --all
-moltbot gateway probe
-moltbot logs --follow
-moltbot doctor
+openclaw status
+openclaw status --all
+openclaw gateway probe
+openclaw logs --follow
+openclaw doctor
 ```
 
 If the gateway is reachable, deep probes:
 
 ```bash
-moltbot status --deep
+openclaw status --deep
 ```
 
 ## Common “it broke” cases
 
-### `moltbot: command not found`
+### `openclaw: command not found`
 
 Almost always a Node/npm PATH issue. Start here:
 
@@ -38,16 +38,16 @@ Almost always a Node/npm PATH issue. Start here:
 Re-run the installer in verbose mode to see the full trace and npm output:
 
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash -s -- --verbose
+curl -fsSL https://openclaw.bot/install.sh | bash -s -- --verbose
 ```
 
 For beta installs:
 
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose
+curl -fsSL https://openclaw.bot/install.sh | bash -s -- --beta --verbose
 ```
 
-You can also set `CLAWDBOT_VERBOSE=1` instead of the flag.
+You can also set `OPENCLAW_VERBOSE=1` instead of the flag.
 
 ### Gateway “unauthorized”, can’t connect, or keeps reconnecting
 
@@ -59,10 +59,10 @@ You can also set `CLAWDBOT_VERBOSE=1` instead of the flag.
 - [Gateway troubleshooting](/gateway/troubleshooting)
 - [Control UI](/web/control-ui#insecure-http)
 
-### `docs.molt.bot` shows an SSL error (Comcast/Xfinity)
+### `docs.openclaw.ai` shows an SSL error (Comcast/Xfinity)
 
-Some Comcast/Xfinity connections block `docs.molt.bot` via Xfinity Advanced Security.
-Disable Advanced Security or add `docs.molt.bot` to the allowlist, then retry.
+Some Comcast/Xfinity connections block `docs.openclaw.ai` via Xfinity Advanced Security.
+Disable Advanced Security or add `docs.openclaw.ai` to the allowlist, then retry.
 
 - Xfinity Advanced Security help: https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security
 - Quick sanity checks: try a mobile hotspot or VPN to confirm it’s ISP-level filtering
@@ -82,7 +82,7 @@ Disable Advanced Security or add `docs.molt.bot` to the allowlist, then retry.
 This usually means `agents.defaults.models` is configured as an allowlist. When it’s non-empty,
 only those provider/model keys can be selected.
 
-- Check the allowlist: `moltbot config get agents.defaults.models`
+- Check the allowlist: `openclaw config get agents.defaults.models`
 - Add the model you want (or clear the allowlist) and retry `/model`
 - Use `/models` to browse the allowed providers/models
 
@@ -91,7 +91,7 @@ only those provider/model keys can be selected.
 Paste a safe report:
 
 ```bash
-moltbot status --all
+openclaw status --all
 ```
 
-If you can, include the relevant log tail from `moltbot logs --follow`.
+If you can, include the relevant log tail from `openclaw logs --follow`.

package/docs/hooks/soul-evil.md

@@ -14,7 +14,7 @@ a purge window or by random chance. It does **not** modify files on disk.
 
 When `agent:bootstrap` runs, the hook can replace the `SOUL.md` content in memory
 before the system prompt is assembled. If `SOUL_EVIL.md` is missing or empty,
-Moltbot logs a warning and keeps the normal `SOUL.md`.
+OpenClaw logs a warning and keeps the normal `SOUL.md`.
 
 Sub-agent runs do **not** include `SOUL.md` in their bootstrap files, so this hook
 has no effect on sub-agents.
@@ -22,7 +22,7 @@ has no effect on sub-agents.
 ## Enable
 
 ```bash
-moltbot hooks enable soul-evil
+openclaw hooks enable soul-evil
 ```
 
 Then set the config:

package/docs/hooks.md

@@ -6,14 +6,14 @@ read_when:
 ---
 # Hooks
 
-Hooks provide an extensible event-driven system for automating actions in response to agent commands and events. Hooks are automatically discovered from directories and can be managed via CLI commands, similar to how skills work in Moltbot.
+Hooks provide an extensible event-driven system for automating actions in response to agent commands and events. Hooks are automatically discovered from directories and can be managed via CLI commands, similar to how skills work in OpenClaw.
 
 ## Getting Oriented
 
 Hooks are small scripts that run when something happens. There are two kinds:
 
 - **Hooks** (this page): run inside the Gateway when agent events fire, like `/new`, `/reset`, `/stop`, or lifecycle events.
-- **Webhooks**: external HTTP webhooks that let other systems trigger work in Moltbot. See [Webhook Hooks](/automation/webhook) or use `moltbot webhooks` for Gmail helper commands.
+- **Webhooks**: external HTTP webhooks that let other systems trigger work in OpenClaw. See [Webhook Hooks](/automation/webhook) or use `openclaw webhooks` for Gmail helper commands.
   
 Hooks can also be bundled inside plugins; see [Plugins](/plugin#plugin-hooks).
 
@@ -31,54 +31,54 @@ The hooks system allows you to:
 - Save session context to memory when `/new` is issued
 - Log all commands for auditing
 - Trigger custom automations on agent lifecycle events
-- Extend Moltbot's behavior without modifying core code
+- Extend OpenClaw's behavior without modifying core code
 
 ## Getting Started
 
 ### Bundled Hooks
 
-Moltbot ships with four bundled hooks that are automatically discovered:
+OpenClaw ships with four bundled hooks that are automatically discovered:
 
-- **💾 session-memory**: Saves session context to your agent workspace (default `~/clawd/memory/`) when you issue `/new`
-- **📝 command-logger**: Logs all command events to `~/.clawdbot/logs/commands.log`
+- **💾 session-memory**: Saves session context to your agent workspace (default `~/.openclaw/workspace/memory/`) when you issue `/new`
+- **📝 command-logger**: Logs all command events to `~/.openclaw/logs/commands.log`
 - **🚀 boot-md**: Runs `BOOT.md` when the gateway starts (requires internal hooks enabled)
 - **😈 soul-evil**: Swaps injected `SOUL.md` content with `SOUL_EVIL.md` during a purge window or by random chance
 
 List available hooks:
 
 ```bash
-moltbot hooks list
+openclaw hooks list
 ```
 
 Enable a hook:
 
 ```bash
-moltbot hooks enable session-memory
+openclaw hooks enable session-memory
 ```
 
 Check hook status:
 
 ```bash
-moltbot hooks check
+openclaw hooks check
 ```
 
 Get detailed information:
 
 ```bash
-moltbot hooks info session-memory
+openclaw hooks info session-memory
 ```
 
 ### Onboarding
 
-During onboarding (`moltbot onboard`), you'll be prompted to enable recommended hooks. The wizard automatically discovers eligible hooks and presents them for selection.
+During onboarding (`openclaw onboard`), you'll be prompted to enable recommended hooks. The wizard automatically discovers eligible hooks and presents them for selection.
 
 ## Hook Discovery
 
 Hooks are automatically discovered from three directories (in order of precedence):
 
 1. **Workspace hooks**: `<workspace>/hooks/` (per-agent, highest precedence)
-2. **Managed hooks**: `~/.clawdbot/hooks/` (user-installed, shared across workspaces)
-3. **Bundled hooks**: `<moltbot>/dist/hooks/bundled/` (shipped with Moltbot)
+2. **Managed hooks**: `~/.openclaw/hooks/` (user-installed, shared across workspaces)
+3. **Bundled hooks**: `<openclaw>/dist/hooks/bundled/` (shipped with OpenClaw)
 
 Managed hook directories can be either a **single hook** or a **hook pack** (package directory).
 
@@ -92,11 +92,11 @@ my-hook/
 
 ## Hook Packs (npm/archives)
 
-Hook packs are standard npm packages that export one or more hooks via `moltbot.hooks` in
+Hook packs are standard npm packages that export one or more hooks via `openclaw.hooks` in
 `package.json`. Install them with:
 
 ```bash
-moltbot hooks install <path-or-spec>
+openclaw hooks install <path-or-spec>
 ```
 
 Example `package.json`:
@@ -105,14 +105,14 @@ Example `package.json`:
 {
   "name": "@acme/my-hooks",
   "version": "0.1.0",
-  "moltbot": {
+  "openclaw": {
     "hooks": ["./hooks/my-hook", "./hooks/other-hook"]
   }
 }
 ```
 
 Each entry points to a hook directory containing `HOOK.md` and `handler.ts` (or `index.ts`).
-Hook packs can ship dependencies; they will be installed under `~/.clawdbot/hooks/<id>`.
+Hook packs can ship dependencies; they will be installed under `~/.openclaw/hooks/<id>`.
 
 ## Hook Structure
 
@@ -124,8 +124,8 @@ The `HOOK.md` file contains metadata in YAML frontmatter plus Markdown documenta
 ---
 name: my-hook
 description: "Short description of what this hook does"
-homepage: https://docs.molt.bot/hooks#my-hook
-metadata: {"moltbot":{"emoji":"🔗","events":["command:new"],"requires":{"bins":["node"]}}}
+homepage: https://docs.openclaw.ai/hooks#my-hook
+metadata: {"openclaw":{"emoji":"🔗","events":["command:new"],"requires":{"bins":["node"]}}}
 ---
 
 # My Hook
@@ -149,7 +149,7 @@ No configuration needed.
 
 ### Metadata Fields
 
-The `metadata.clawdbot` object supports:
+The `metadata.openclaw` object supports:
 
 - **`emoji`**: Display emoji for CLI (e.g., `"💾"`)
 - **`events`**: Array of events to listen for (e.g., `["command:new", "command:reset"]`)
@@ -209,7 +209,7 @@ Each event includes:
     senderId?: string,
     workspaceDir?: string,
     bootstrapFiles?: WorkspaceBootstrapFile[],
-    cfg?: MoltbotConfig
+    cfg?: OpenClawConfig
   }
 }
 ```
@@ -237,7 +237,7 @@ Triggered when the gateway starts:
 
 ### Tool Result Hooks (Plugin API)
 
-These hooks are not event-stream listeners; they let plugins synchronously adjust tool results before Moltbot persists them.
+These hooks are not event-stream listeners; they let plugins synchronously adjust tool results before OpenClaw persists them.
 
 - **`tool_result_persist`**: transform tool results before they are written to the session transcript. Must be synchronous; return the updated tool result payload or `undefined` to keep it as-is. See [Agent Loop](/concepts/agent-loop).
 
@@ -256,13 +256,13 @@ Planned event types:
 ### 1. Choose Location
 
 - **Workspace hooks** (`<workspace>/hooks/`): Per-agent, highest precedence
-- **Managed hooks** (`~/.clawdbot/hooks/`): Shared across workspaces
+- **Managed hooks** (`~/.openclaw/hooks/`): Shared across workspaces
 
 ### 2. Create Directory Structure
 
 ```bash
-mkdir -p ~/.clawdbot/hooks/my-hook
-cd ~/.clawdbot/hooks/my-hook
+mkdir -p ~/.openclaw/hooks/my-hook
+cd ~/.openclaw/hooks/my-hook
 ```
 
 ### 3. Create HOOK.md
@@ -271,7 +271,7 @@ cd ~/.clawdbot/hooks/my-hook
 ---
 name: my-hook
 description: "Does something useful"
-metadata: {"moltbot":{"emoji":"🎯","events":["command:new"]}}
+metadata: {"openclaw":{"emoji":"🎯","events":["command:new"]}}
 ---
 
 # My Custom Hook
@@ -300,10 +300,10 @@ export default handler;
 
 ```bash
 # Verify hook is discovered
-moltbot hooks list
+openclaw hooks list
 
 # Enable it
-moltbot hooks enable my-hook
+openclaw hooks enable my-hook
 
 # Restart your gateway process (menu bar app restart on macOS, or restart your dev process)
 
@@ -397,46 +397,46 @@ The old config format still works for backwards compatibility:
 
 ```bash
 # List all hooks
-moltbot hooks list
+openclaw hooks list
 
 # Show only eligible hooks
-moltbot hooks list --eligible
+openclaw hooks list --eligible
 
 # Verbose output (show missing requirements)
-moltbot hooks list --verbose
+openclaw hooks list --verbose
 
 # JSON output
-moltbot hooks list --json
+openclaw hooks list --json
 ```
 
 ### Hook Information
 
 ```bash
 # Show detailed info about a hook
-moltbot hooks info session-memory
+openclaw hooks info session-memory
 
 # JSON output
-moltbot hooks info session-memory --json
+openclaw hooks info session-memory --json
 ```
 
 ### Check Eligibility
 
 ```bash
 # Show eligibility summary
-moltbot hooks check
+openclaw hooks check
 
 # JSON output
-moltbot hooks check --json
+openclaw hooks check --json
 ```
 
 ### Enable/Disable
 
 ```bash
 # Enable a hook
-moltbot hooks enable session-memory
+openclaw hooks enable session-memory
 
 # Disable a hook
-moltbot hooks disable command-logger
+openclaw hooks disable command-logger
 ```
 
 ## Bundled Hooks
@@ -449,7 +449,7 @@ Saves session context to memory when you issue `/new`.
 
 **Requirements**: `workspace.dir` must be configured
 
-**Output**: `<workspace>/memory/YYYY-MM-DD-slug.md` (defaults to `~/clawd`)
+**Output**: `<workspace>/memory/YYYY-MM-DD-slug.md` (defaults to `~/.openclaw/workspace`)
 
 **What it does**:
 1. Uses the pre-reset session entry to locate the correct transcript
@@ -475,7 +475,7 @@ Saves session context to memory when you issue `/new`.
 **Enable**:
 
 ```bash
-moltbot hooks enable session-memory
+openclaw hooks enable session-memory
 ```
 
 ### command-logger
@@ -486,7 +486,7 @@ Logs all command events to a centralized audit file.
 
 **Requirements**: None
 
-**Output**: `~/.clawdbot/logs/commands.log`
+**Output**: `~/.openclaw/logs/commands.log`
 
 **What it does**:
 1. Captures event details (command action, timestamp, session key, sender ID, source)
@@ -504,19 +504,19 @@ Logs all command events to a centralized audit file.
 
 ```bash
 # View recent commands
-tail -n 20 ~/.clawdbot/logs/commands.log
+tail -n 20 ~/.openclaw/logs/commands.log
 
 # Pretty-print with jq
-cat ~/.clawdbot/logs/commands.log | jq .
+cat ~/.openclaw/logs/commands.log | jq .
 
 # Filter by action
-grep '"action":"new"' ~/.clawdbot/logs/commands.log | jq .
+grep '"action":"new"' ~/.openclaw/logs/commands.log | jq .
 ```
 
 **Enable**:
 
 ```bash
-moltbot hooks enable command-logger
+openclaw hooks enable command-logger
 ```
 
 ### soul-evil
@@ -532,7 +532,7 @@ Swaps injected `SOUL.md` content with `SOUL_EVIL.md` during a purge window or by
 **Enable**:
 
 ```bash
-moltbot hooks enable soul-evil
+openclaw hooks enable soul-evil
 ```
 
 **Config**:
@@ -572,7 +572,7 @@ Internal hooks must be enabled for this to run.
 **Enable**:
 
 ```bash
-moltbot hooks enable boot-md
+openclaw hooks enable boot-md
 ```
 
 ## Best Practices
@@ -629,13 +629,13 @@ const handler: HookHandler = async (event) => {
 Specify exact events in metadata when possible:
 
 ```yaml
-metadata: {"moltbot":{"events":["command:new"]}}  # Specific
+metadata: {"openclaw":{"events":["command:new"]}}  # Specific
 ```
 
 Rather than:
 
 ```yaml
-metadata: {"moltbot":{"events":["command"]}}      # General - more overhead
+metadata: {"openclaw":{"events":["command"]}}      # General - more overhead
 ```
 
 ## Debugging
@@ -655,7 +655,7 @@ Registered hook: boot-md -> gateway:startup
 List all discovered hooks:
 
 ```bash
-moltbot hooks list --verbose
+openclaw hooks list --verbose
 ```
 
 ### Check Registration
@@ -674,7 +674,7 @@ const handler: HookHandler = async (event) => {
 Check why a hook isn't eligible:
 
 ```bash
-moltbot hooks info my-hook
+openclaw hooks info my-hook
 ```
 
 Look for missing requirements in the output.
@@ -690,7 +690,7 @@ Monitor gateway logs to see hook execution:
 ./scripts/clawlog.sh -f
 
 # Other platforms
-tail -f ~/.clawdbot/gateway.log
+tail -f ~/.openclaw/gateway.log
 ```
 
 ### Test Hooks Directly
@@ -765,19 +765,19 @@ Session reset
 
 1. Check directory structure:
    ```bash
-   ls -la ~/.clawdbot/hooks/my-hook/
+   ls -la ~/.openclaw/hooks/my-hook/
    # Should show: HOOK.md, handler.ts
    ```
 
 2. Verify HOOK.md format:
    ```bash
-   cat ~/.clawdbot/hooks/my-hook/HOOK.md
+   cat ~/.openclaw/hooks/my-hook/HOOK.md
    # Should have YAML frontmatter with name and metadata
    ```
 
 3. List all discovered hooks:
    ```bash
-   moltbot hooks list
+   openclaw hooks list
    ```
 
 ### Hook Not Eligible
@@ -785,7 +785,7 @@ Session reset
 Check requirements:
 
 ```bash
-moltbot hooks info my-hook
+openclaw hooks info my-hook
 ```
 
 Look for missing:
@@ -798,7 +798,7 @@ Look for missing:
 
 1. Verify hook is enabled:
    ```bash
-   moltbot hooks list
+   openclaw hooks list
    # Should show ✓ next to enabled hooks
    ```
 
@@ -844,8 +844,8 @@ node -e "import('./path/to/handler.ts').then(console.log)"
 
 1. Create hook directory:
    ```bash
-   mkdir -p ~/.clawdbot/hooks/my-hook
-   mv ./hooks/handlers/my-handler.ts ~/.clawdbot/hooks/my-hook/handler.ts
+   mkdir -p ~/.openclaw/hooks/my-hook
+   mv ./hooks/handlers/my-handler.ts ~/.openclaw/hooks/my-hook/handler.ts
    ```
 
 2. Create HOOK.md:
@@ -853,7 +853,7 @@ node -e "import('./path/to/handler.ts').then(console.log)"
    ---
    name: my-hook
    description: "My custom hook"
-   metadata: {"moltbot":{"emoji":"🎯","events":["command:new"]}}
+   metadata: {"openclaw":{"emoji":"🎯","events":["command:new"]}}
    ---
 
    # My Hook
@@ -877,7 +877,7 @@ node -e "import('./path/to/handler.ts').then(console.log)"
 
 4. Verify and restart your gateway process:
    ```bash
-   moltbot hooks list
+   openclaw hooks list
    # Should show: 🎯 my-hook ✓
    ```
 
@@ -891,6 +891,6 @@ node -e "import('./path/to/handler.ts').then(console.log)"
 ## See Also
 
 - [CLI Reference: hooks](/cli/hooks)
-- [Bundled Hooks README](https://github.com/moltbot/moltbot/tree/main/src/hooks/bundled)
+- [Bundled Hooks README](https://github.com/openclaw/openclaw/tree/main/src/hooks/bundled)
 - [Webhook Hooks](/automation/webhook)
 - [Configuration](/gateway/configuration#hooks)