@poolzin/pool-bot 1.28.0 → 2026.1.26

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
+clawdbot status
+clawdbot status --all
+clawdbot gateway probe
+clawdbot logs --follow
+clawdbot doctor
 ```
 
 If the gateway is reachable, deep probes:
 
 ```bash
-moltbot status --deep
+clawdbot status --deep
 ```
 
 ## Common “it broke” cases
 
-### `moltbot: command not found`
+### `clawdbot: command not found`
 
 Almost always a Node/npm PATH issue. Start here:
 
@@ -38,13 +38,13 @@ 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://clawd.bot/install.sh | bash -s -- --verbose
 ```
 
 For beta installs:
 
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose
+curl -fsSL https://clawd.bot/install.sh | bash -s -- --beta --verbose
 ```
 
 You can also set `CLAWDBOT_VERBOSE=1` instead of the flag.
@@ -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.clawd.bot` 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.clawd.bot` via Xfinity Advanced Security.
+Disable Advanced Security or add `docs.clawd.bot` 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: `clawdbot 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
+clawdbot status --all
 ```
 
-If you can, include the relevant log tail from `moltbot logs --follow`.
+If you can, include the relevant log tail from `clawdbot 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,
-Pool Bot logs a warning and keeps the normal `SOUL.md`.
+Clawdbot 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
+clawdbot 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 Pool Bot.
+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 Clawdbot.
 
 ## 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 Pool Bot. See [Webhook Hooks](/automation/webhook) or use `moltbot webhooks` for Gmail helper commands.
+- **Webhooks**: external HTTP webhooks that let other systems trigger work in Clawdbot. See [Webhook Hooks](/automation/webhook) or use `clawdbot webhooks` for Gmail helper commands.
   
 Hooks can also be bundled inside plugins; see [Plugins](/plugin#plugin-hooks).
 
@@ -31,13 +31,13 @@ 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 Pool Bot's behavior without modifying core code
+- Extend Clawdbot's behavior without modifying core code
 
 ## Getting Started
 
 ### Bundled Hooks
 
-Pool Bot ships with four bundled hooks that are automatically discovered:
+Clawdbot 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`
@@ -47,30 +47,30 @@ Pool Bot ships with four bundled hooks that are automatically discovered:
 List available hooks:
 
 ```bash
-moltbot hooks list
+clawdbot hooks list
 ```
 
 Enable a hook:
 
 ```bash
-moltbot hooks enable session-memory
+clawdbot hooks enable session-memory
 ```
 
 Check hook status:
 
 ```bash
-moltbot hooks check
+clawdbot hooks check
 ```
 
 Get detailed information:
 
 ```bash
-moltbot hooks info session-memory
+clawdbot 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 (`clawdbot onboard`), you'll be prompted to enable recommended hooks. The wizard automatically discovers eligible hooks and presents them for selection.
 
 ## Hook Discovery
 
@@ -78,7 +78,7 @@ Hooks are automatically discovered from three directories (in order of precedenc
 
 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 Pool Bot)
+3. **Bundled hooks**: `<clawdbot>/dist/hooks/bundled/` (shipped with Clawdbot)
 
 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 `clawdbot.hooks` in
 `package.json`. Install them with:
 
 ```bash
-moltbot hooks install <path-or-spec>
+clawdbot hooks install <path-or-spec>
 ```
 
 Example `package.json`:
@@ -105,7 +105,7 @@ Example `package.json`:
 {
   "name": "@acme/my-hooks",
   "version": "0.1.0",
-  "moltbot": {
+  "clawdbot": {
     "hooks": ["./hooks/my-hook", "./hooks/other-hook"]
   }
 }
@@ -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.clawd.bot/hooks#my-hook
+metadata: {"clawdbot":{"emoji":"🔗","events":["command:new"],"requires":{"bins":["node"]}}}
 ---
 
 # My Hook
@@ -209,7 +209,7 @@ Each event includes:
     senderId?: string,
     workspaceDir?: string,
     bootstrapFiles?: WorkspaceBootstrapFile[],
-    cfg?: Pool BotConfig
+    cfg?: ClawdbotConfig
   }
 }
 ```
@@ -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 Pool Bot persists them.
+These hooks are not event-stream listeners; they let plugins synchronously adjust tool results before Clawdbot 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).
 
@@ -271,7 +271,7 @@ cd ~/.clawdbot/hooks/my-hook
 ---
 name: my-hook
 description: "Does something useful"
-metadata: {"moltbot":{"emoji":"🎯","events":["command:new"]}}
+metadata: {"clawdbot":{"emoji":"🎯","events":["command:new"]}}
 ---
 
 # My Custom Hook
@@ -300,10 +300,10 @@ export default handler;
 
 ```bash
 # Verify hook is discovered
-moltbot hooks list
+clawdbot hooks list
 
 # Enable it
-moltbot hooks enable my-hook
+clawdbot 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
+clawdbot hooks list
 
 # Show only eligible hooks
-moltbot hooks list --eligible
+clawdbot hooks list --eligible
 
 # Verbose output (show missing requirements)
-moltbot hooks list --verbose
+clawdbot hooks list --verbose
 
 # JSON output
-moltbot hooks list --json
+clawdbot hooks list --json
 ```
 
 ### Hook Information
 
 ```bash
 # Show detailed info about a hook
-moltbot hooks info session-memory
+clawdbot hooks info session-memory
 
 # JSON output
-moltbot hooks info session-memory --json
+clawdbot hooks info session-memory --json
 ```
 
 ### Check Eligibility
 
 ```bash
 # Show eligibility summary
-moltbot hooks check
+clawdbot hooks check
 
 # JSON output
-moltbot hooks check --json
+clawdbot hooks check --json
 ```
 
 ### Enable/Disable
 
 ```bash
 # Enable a hook
-moltbot hooks enable session-memory
+clawdbot hooks enable session-memory
 
 # Disable a hook
-moltbot hooks disable command-logger
+clawdbot hooks disable command-logger
 ```
 
 ## Bundled Hooks
@@ -475,7 +475,7 @@ Saves session context to memory when you issue `/new`.
 **Enable**:
 
 ```bash
-moltbot hooks enable session-memory
+clawdbot hooks enable session-memory
 ```
 
 ### command-logger
@@ -516,7 +516,7 @@ grep '"action":"new"' ~/.clawdbot/logs/commands.log | jq .
 **Enable**:
 
 ```bash
-moltbot hooks enable command-logger
+clawdbot 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
+clawdbot 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
+clawdbot 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: {"clawdbot":{"events":["command:new"]}}  # Specific
 ```
 
 Rather than:
 
 ```yaml
-metadata: {"moltbot":{"events":["command"]}}      # General - more overhead
+metadata: {"clawdbot":{"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
+clawdbot 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
+clawdbot hooks info my-hook
 ```
 
 Look for missing requirements in the output.
@@ -777,7 +777,7 @@ Session reset
 
 3. List all discovered hooks:
    ```bash
-   moltbot hooks list
+   clawdbot hooks list
    ```
 
 ### Hook Not Eligible
@@ -785,7 +785,7 @@ Session reset
 Check requirements:
 
 ```bash
-moltbot hooks info my-hook
+clawdbot hooks info my-hook
 ```
 
 Look for missing:
@@ -798,7 +798,7 @@ Look for missing:
 
 1. Verify hook is enabled:
    ```bash
-   moltbot hooks list
+   clawdbot hooks list
    # Should show ✓ next to enabled hooks
    ```
 
@@ -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: {"clawdbot":{"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
+   clawdbot 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/clawdbot/clawdbot/tree/main/src/hooks/bundled)
 - [Webhook Hooks](/automation/webhook)
 - [Configuration](/gateway/configuration#hooks)

package/docs/index.md

@@ -1,14 +1,14 @@
 ---
-summary: "Top-level overview of Pool Bot, features, and purpose"
+summary: "Top-level overview of Clawdbot, features, and purpose"
 read_when:
-  - Introducing Pool Bot to newcomers
+  - Introducing Clawdbot to newcomers
 ---
-# Pool Bot 🦞
+# Clawdbot 🦞
 
 > *"EXFOLIATE! EXFOLIATE!"* — A space lobster, probably
 
 <p align="center">
-  <img src="whatsapp-clawd.jpg" alt="Pool Bot" width="420" />
+  <img src="whatsapp-clawd.jpg" alt="Clawdbot" width="420" />
 </p>
 
 <p align="center">
@@ -18,23 +18,23 @@ read_when:
 </p>
 
 <p align="center">
-  <a href="https://github.com/moltbot/moltbot">GitHub</a> ·
-  <a href="https://github.com/moltbot/moltbot/releases">Releases</a> ·
+  <a href="https://github.com/clawdbot/clawdbot">GitHub</a> ·
+  <a href="https://github.com/clawdbot/clawdbot/releases">Releases</a> ·
   <a href="/">Docs</a> ·
-  <a href="/start/clawd">Pool Bot assistant setup</a>
+  <a href="/start/clawd">Clawdbot assistant setup</a>
 </p>
 
-Pool Bot 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.
-Pool Bot also powers [Clawd](https://clawd.me), the space‑lobster assistant.
+Clawdbot 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.
+Clawdbot 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) (`moltbot onboard`)
+- **Guided setup (recommended):** [Wizard](/start/wizard) (`clawdbot 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: `moltbot gateway`.
+immediately. If it fails, start the Gateway first: `clawdbot 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
-  │                           │    /__moltbot__/canvas/ (Canvas host)
+  │                           │    /__clawdbot__/canvas/ (Canvas host)
   └───────────┬───────────────┘
               │
               ├─ Pi agent (RPC)
-              ├─ CLI (moltbot …)
+              ├─ CLI (clawdbot …)
               ├─ Chat UI (SwiftUI)
-              ├─ macOS app (Pool Bot.app)
+              ├─ macOS app (Clawdbot.app)
               ├─ iOS node via Gateway WS + pairing
               └─ Android node via Gateway WS + pairing
 ```
 
-Most operations flow through the **Gateway** (`moltbot gateway`), a single long-running process that owns channel connections and the WebSocket control plane.
+Most operations flow through the **Gateway** (`clawdbot 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 `moltbot gateway --bind tailnet --token ...` (token is required for non-loopback binds).
+  - For Tailnet access, run `clawdbot 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 `/__moltbot__/canvas/` for node WebViews; see [Gateway configuration](/gateway/configuration) (`canvasHost`).
+- **Canvas host**: HTTP file server on `canvasHost.port` (default `18793`), serving `/__clawdbot__/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 moltbot@latest
-# or: pnpm add -g moltbot@latest
+npm install -g clawdbot@latest
+# or: pnpm add -g clawdbot@latest
 
 # Onboard + install the service (launchd/systemd user service)
-moltbot onboard --install-daemon
+clawdbot onboard --install-daemon
 
 # Pair WhatsApp Web (shows QR)
-moltbot channels login
+clawdbot channels login
 
 # Gateway runs via the service after onboarding; manual run is still possible:
-moltbot gateway --port 18789
+clawdbot gateway --port 18789
 ```
 
-Switching between npm and git installs later is easy: install the other flavor and run `moltbot doctor` to update the gateway service entrypoint.
+Switching between npm and git installs later is easy: install the other flavor and run `clawdbot doctor` to update the gateway service entrypoint.
 
 From source (development):
 
 ```bash
-git clone https://github.com/moltbot/moltbot.git
-cd moltbot
+git clone https://github.com/clawdbot/clawdbot.git
+cd clawdbot
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
-moltbot onboard --install-daemon
+clawdbot onboard --install-daemon
 ```
 
-If you don’t have a global install yet, run the onboarding step via `pnpm moltbot ...` from the repo.
+If you don’t have a global install yet, run the onboarding step via `pnpm clawdbot ...` from the repo.
 
 Multi-instance quickstart (optional):
 
 ```bash
 CLAWDBOT_CONFIG_PATH=~/.clawdbot/a.json \
 CLAWDBOT_STATE_DIR=~/.clawdbot-a \
-moltbot gateway --port 19001
+clawdbot gateway --port 19001
 ```
 
 Send a test message (requires a running Gateway):
 
 ```bash
-moltbot message send --target +15555550123 --message "Hello from Pool Bot"
+clawdbot message send --target +15555550123 --message "Hello from Clawdbot"
 ```
 
 ## Configuration (optional)
 
-Config lives at `~/.clawdbot/moltbot.json`.
+Config lives at `~/.clawdbot/clawdbot.json`.
 
-- If you **do nothing**, Pool Bot uses the bundled Pi binary in RPC mode with per-sender sessions.
+- If you **do nothing**, Clawdbot 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)
-  - [Pool Bot assistant setup (Clawd)](/start/clawd)
+  - [Clawdbot 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
 
-**Pool Bot = CLAW + TARDIS** — because every space lobster needs a time-and-space machine.
+**Clawdbot = CLAW + TARDIS** — because every space lobster needs a time-and-space machine.
 
 ---