@poolzin/pool-bot 1.28.0 → 2026.1.26

package/docs/nodes/media-understanding.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Media Understanding (Inbound) — 2026-01-17
 
-Pool Bot can **summarize inbound media** (image/audio/video) before the reply pipeline runs. It auto‑detects when local tools or provider keys are available, and can be disabled or customized. If understanding is off, models still receive the original files/URLs as usual.
+Clawdbot can **summarize inbound media** (image/audio/video) before the reply pipeline runs. It auto‑detects when local tools or provider keys are available, and can be disabled or customized. If understanding is off, models still receive the original files/URLs as usual.
 
 ## Goals
 - Optional: pre‑digest inbound media into short text for faster routing + better command parsing.
@@ -106,12 +106,12 @@ Rules:
 - If media exceeds `maxBytes`, that model is skipped and the **next model is tried**.
 - If the model returns more than `maxChars`, output is trimmed.
 - `prompt` defaults to simple “Describe the {media}.” plus the `maxChars` guidance (image/video only).
-- If `<capability>.enabled: true` but no models are configured, Pool Bot tries the
+- If `<capability>.enabled: true` but no models are configured, Clawdbot tries the
   **active reply model** when its provider supports the capability.
 
 ### Auto-detect media understanding (default)
 If `tools.media.<capability>.enabled` is **not** set to `false` and you haven’t
-configured models, Pool Bot auto-detects in this order and **stops at the first
+configured models, Clawdbot auto-detects in this order and **stops at the first
 working option**:
 
 1) **Local CLIs** (audio only; if installed)
@@ -140,7 +140,7 @@ Note: Binary detection is best-effort across macOS/Linux/Windows; ensure the CLI
 
 ## Capabilities (optional)
 If you set `capabilities`, the entry only runs for those media types. For shared
-lists, Pool Bot can infer defaults:
+lists, Clawdbot can infer defaults:
 - `openai`, `anthropic`, `minimax`: **image**
 - `google` (Gemini API): **image + audio + video**
 - `groq`: **audio**
@@ -149,7 +149,7 @@ lists, Pool Bot can infer defaults:
 For CLI entries, **set `capabilities` explicitly** to avoid surprising matches.
 If you omit `capabilities`, the entry is eligible for the list it appears in.
 
-## Provider support matrix (Pool Bot integrations)
+## Provider support matrix (Clawdbot integrations)
 | Capability | Provider integration | Notes |
 |------------|----------------------|-------|
 | Image | OpenAI / Anthropic / Google / others via `pi-ai` | Any image-capable model in the registry works. |

package/docs/nodes/talk.md

@@ -40,7 +40,7 @@ Supported keys:
 - `seed`, `normalize`, `lang`, `output_format`, `latency_tier`
 - `once`
 
-## Config (`~/.clawdbot/moltbot.json`)
+## Config (`~/.clawdbot/clawdbot.json`)
 ```json5
 {
   "talk": {

package/docs/nodes/voicewake.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Voice Wake (Global Wake Words)
 
-Pool Bot treats **wake words as a single global list** owned by the **Gateway**.
+Clawdbot treats **wake words as a single global list** owned by the **Gateway**.
 
 - There are **no per-node custom wake words**.
 - **Any node/app UI may edit** the list; changes are persisted by the Gateway and broadcast to everyone.

package/docs/perplexity.md

@@ -7,7 +7,7 @@ read_when:
 
 # Perplexity Sonar
 
-Pool Bot can use Perplexity Sonar for the `web_search` tool. You can connect
+Clawdbot can use Perplexity Sonar for the `web_search` tool. You can connect
 through Perplexity’s direct API or via OpenRouter.
 
 ## API options
@@ -64,7 +64,7 @@ If both `PERPLEXITY_API_KEY` and `OPENROUTER_API_KEY` are set, set
 `tools.web.search.perplexity.baseUrl` (or `tools.web.search.perplexity.apiKey`)
 to disambiguate.
 
-If no base URL is set, Pool Bot chooses a default based on the API key source:
+If no base URL is set, Clawdbot chooses a default based on the API key source:
 
 - `PERPLEXITY_API_KEY` or `pplx-...` → direct Perplexity (`https://api.perplexity.ai`)
 - `OPENROUTER_API_KEY` or `sk-or-...` → OpenRouter (`https://openrouter.ai/api/v1`)

package/docs/platforms/android.md

@@ -31,12 +31,12 @@ Android connects directly to the Gateway WebSocket (default `ws://<host>:18789`)
   - Same LAN with mDNS/NSD, **or**
   - Same Tailscale tailnet using Wide-Area Bonjour / unicast DNS-SD (see below), **or**
   - Manual gateway host/port (fallback)
-- You can run the CLI (`poolbot`) on the gateway machine (or via SSH).
+- You can run the CLI (`clawdbot`) on the gateway machine (or via SSH).
 
 ### 1) Start the Gateway
 
 ```bash
-poolbot gateway --port 18789 --verbose
+clawdbot gateway --port 18789 --verbose
 ```
 
 Confirm in logs you see something like:
@@ -44,7 +44,7 @@ Confirm in logs you see something like:
 
 For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to the tailnet IP:
 
-- Set `gateway.bind: "tailnet"` in `~/.clawdbot/poolbot.json` on the gateway host.
+- Set `gateway.bind: "tailnet"` in `~/.clawdbot/clawdbot.json` on the gateway host.
 - Restart the Gateway / macOS menubar app.
 
 ### 2) Verify discovery (optional)
@@ -52,7 +52,7 @@ For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to
 From the gateway machine:
 
 ```bash
-dns-sd -B _poolbot-gw._tcp local.
+dns-sd -B _clawdbot-gw._tcp local.
 ```
 
 More debugging notes: [Bonjour](/gateway/bonjour).
@@ -61,8 +61,8 @@ More debugging notes: [Bonjour](/gateway/bonjour).
 
 Android NSD/mDNS discovery won’t cross networks. If your Android node and the gateway are on different networks but connected via Tailscale, use Wide-Area Bonjour / unicast DNS-SD instead:
 
-1) Set up a DNS-SD zone (example `poolbot.internal.`) on the gateway host and publish `_poolbot-gw._tcp` records.
-2) Configure Tailscale split DNS for `poolbot.internal` pointing at that DNS server.
+1) Set up a DNS-SD zone (example `clawdbot.internal.`) on the gateway host and publish `_clawdbot-gw._tcp` records.
+2) Configure Tailscale split DNS for `clawdbot.internal` pointing at that DNS server.
 
 Details and example CoreDNS config: [Bonjour](/gateway/bonjour).
 
@@ -84,8 +84,8 @@ After the first successful pairing, Android auto-reconnects on launch:
 On the gateway machine:
 
 ```bash
-poolbot nodes pending
-poolbot nodes approve <requestId>
+clawdbot nodes pending
+clawdbot nodes approve <requestId>
 ```
 
 Pairing details: [Gateway pairing](/gateway/pairing).
@@ -94,11 +94,11 @@ Pairing details: [Gateway pairing](/gateway/pairing).
 
 - Via nodes status:
   ```bash
-  poolbot nodes status
+  clawdbot nodes status
   ```
 - Via Gateway:
   ```bash
-  poolbot gateway call node.list --params "{}"
+  clawdbot gateway call node.list --params "{}"
   ```
 
 ### 6) Chat + history
@@ -122,13 +122,13 @@ Note: nodes use the standalone canvas host on `canvasHost.port` (default `18793`
 2) Navigate the node to it (LAN):
 
 ```bash
-poolbot nodes invoke --node "<Android Node>" --command canvas.navigate --params '{"url":"http://<gateway-hostname>.local:18793/__poolbot__/canvas/"}'
+clawdbot nodes invoke --node "<Android Node>" --command canvas.navigate --params '{"url":"http://<gateway-hostname>.local:18793/__clawdbot__/canvas/"}'
 ```
 
-Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://<gateway-magicdns>:18793/__poolbot__/canvas/`.
+Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://<gateway-magicdns>:18793/__clawdbot__/canvas/`.
 
 This server injects a live-reload client into HTML and reloads on file changes.
-The A2UI host lives at `http://<gateway-host>:18793/__poolbot__/a2ui/`.
+The A2UI host lives at `http://<gateway-host>:18793/__clawdbot__/a2ui/`.
 
 Canvas commands (foreground only):
 - `canvas.eval`, `canvas.snapshot`, `canvas.navigate` (use `{"url":""}` or `{"url":"/"}` to return to the default scaffold). `canvas.snapshot` returns `{ format, base64 }` (default `format="jpeg"`).

package/docs/platforms/exe-dev.md

@@ -1,5 +1,5 @@
 ---
-summary: "Run Pool Bot Gateway on exe.dev (VM + HTTPS proxy) for remote access"
+summary: "Run Clawdbot Gateway on exe.dev (VM + HTTPS proxy) for remote access"
 read_when:
   - You want a cheap always-on Linux host for the Gateway
   - You want remote Control UI access without running your own VPS
@@ -7,7 +7,7 @@ read_when:
 
 # exe.dev
 
-Goal: Pool Bot Gateway running on an exe.dev VM, reachable from your laptop via:
+Goal: Clawdbot Gateway running on an exe.dev VM, reachable from your laptop via:
 - **exe.dev HTTPS proxy** (easy, no tunnel) or
 - **SSH tunnel** (most secure; loopback-only Gateway)
 
@@ -17,8 +17,8 @@ If you’re on any other Linux VPS, the same steps apply — you just won’t us
 
 ## Beginner quick path
 
-1) Create VM → install Node 22 → install Pool Bot  
-2) Run `poolbot onboard --install-daemon`  
+1) Create VM → install Node 22 → install Clawdbot  
+2) Run `clawdbot onboard --install-daemon`  
 3) Tunnel from laptop (`ssh -N -L 18789:127.0.0.1:18789 …`)  
 4) Open `http://127.0.0.1:18789/` and paste your token
 
@@ -34,16 +34,16 @@ If you’re on any other Linux VPS, the same steps apply — you just won’t us
 From your laptop:
 
 ```bash
-ssh exe.dev new --name=poolbot
+ssh exe.dev new --name=clawdbot
 ```
 
 Then connect:
 
 ```bash
-ssh poolbot.exe.xyz
+ssh clawdbot.exe.xyz
 ```
 
-Tip: keep this VM **stateful**. Pool Bot stores state under `~/.clawdbot/` and `~/clawd/`.
+Tip: keep this VM **stateful**. Clawdbot stores state under `~/.clawdbot/` and `~/clawd/`.
 
 ## 2) Install prerequisites (on the VM)
 
@@ -69,13 +69,13 @@ curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
 sudo apt-get install -y nodejs
 ```
 
-## 3) Install Pool Bot
+## 3) Install Clawdbot
 
 Recommended on servers: npm global install.
 
 ```bash
-npm i -g poolbot@latest
-poolbot --version
+npm i -g clawdbot@latest
+clawdbot --version
 ```
 
 If native deps fail to install (rare; usually `sharp`), add build tools:
@@ -89,12 +89,12 @@ sudo apt-get install -y build-essential python3
 Run the onboarding wizard on the VM:
 
 ```bash
-poolbot onboard --install-daemon
+clawdbot onboard --install-daemon
 ```
 
 It can set up:
 - `~/clawd` workspace bootstrap
-- `~/.clawdbot/poolbot.json` config
+- `~/.clawdbot/clawdbot.json` config
 - model auth profiles
 - model provider config/login
 - Linux systemd **user** service (service)
@@ -108,7 +108,7 @@ If you’re doing OAuth on a headless VM: do OAuth on a normal machine first, th
 Keep Gateway on loopback (default) and tunnel it from your laptop:
 
 ```bash
-ssh -N -L 18789:127.0.0.1:18789 poolbot.exe.xyz
+ssh -N -L 18789:127.0.0.1:18789 clawdbot.exe.xyz
 ```
 
 Open locally:
@@ -122,10 +122,10 @@ To let exe.dev proxy traffic to the VM, bind the Gateway to the LAN interface an
 
 ```bash
 export CLAWDBOT_GATEWAY_TOKEN="$(openssl rand -hex 32)"
-poolbot gateway --bind lan --port 8080 --token "$CLAWDBOT_GATEWAY_TOKEN"
+clawdbot gateway --bind lan --port 8080 --token "$CLAWDBOT_GATEWAY_TOKEN"
 ```
 
-For service runs, persist it in `~/.clawdbot/poolbot.json`:
+For service runs, persist it in `~/.clawdbot/clawdbot.json`:
 
 ```json5
 {
@@ -145,11 +145,11 @@ Notes:
 Then point exe.dev’s proxy at `8080` (or whatever port you chose) and open your VM’s HTTPS URL:
 
 ```bash
-ssh exe.dev share port poolbot 8080
+ssh exe.dev share port clawdbot 8080
 ```
 
 Open:
-- `https://poolbot.exe.xyz/`
+- `https://clawdbot.exe.xyz/`
 
 In the Control UI, paste the token (UI → Settings → token). The UI sends it as `connect.params.auth.token`.
 
@@ -161,10 +161,10 @@ Control UI details: [Control UI](/web/control-ui)
 
 ## 6) Keep it running (service)
 
-On Linux, Pool Bot uses a systemd **user** service. After `--install-daemon`, verify:
+On Linux, Clawdbot uses a systemd **user** service. After `--install-daemon`, verify:
 
 ```bash
-systemctl --user status poolbot-gateway[-<profile>].service
+systemctl --user status clawdbot-gateway[-<profile>].service
 ```
 
 If the service dies after logout, enable lingering:
@@ -178,10 +178,10 @@ More: [Linux](/platforms/linux)
 ## 7) Updates
 
 ```bash
-npm i -g poolbot@latest
-poolbot doctor
-poolbot gateway restart
-poolbot health
+npm i -g clawdbot@latest
+clawdbot doctor
+clawdbot gateway restart
+clawdbot health
 ```
 
 Guide: [Updating](/install/updating)

package/docs/platforms/fly.md

@@ -1,11 +1,11 @@
 ---
 title: Fly.io
-description: Deploy Pool Bot on Fly.io
+description: Deploy Clawdbot on Fly.io
 ---
 
 # Fly.io Deployment
 
-**Goal:** Pool Bot Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access.
+**Goal:** Clawdbot Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access.
 
 ## What you need
 
@@ -25,26 +25,24 @@ description: Deploy Pool Bot on Fly.io
 
 ```bash
 # Clone the repo
-git clone https://github.com/poolbot/poolbot.git
-cd poolbot
+git clone https://github.com/clawdbot/clawdbot.git
+cd clawdbot
 
 # Create a new Fly app (pick your own name)
-fly apps create my-poolbot
+fly apps create my-clawdbot
 
 # Create a persistent volume (1GB is usually enough)
-fly volumes create poolbot_data --size 1 --region iad
+fly volumes create clawdbot_data --size 1 --region iad
 ```
 
 **Tip:** Choose a region close to you. Common options: `lhr` (London), `iad` (Virginia), `sjc` (San Jose).
 
 ## 2) Configure fly.toml
 
-Edit `fly.toml` to match your app name and requirements.
-
-**Security note:** The default config exposes a public URL. For a hardened deployment with no public IP, see [Private Deployment](#private-deployment-hardened) or use `fly.private.toml`.
+Edit `fly.toml` to match your app name and requirements:
 
 ```toml
-app = "my-poolbot"  # Your app name
+app = "my-clawdbot"  # Your app name
 primary_region = "iad"
 
 [build]
@@ -72,7 +70,7 @@ primary_region = "iad"
   memory = "2048mb"
 
 [mounts]
-  source = "poolbot_data"
+  source = "clawdbot_data"
   destination = "/data"
 ```
 
@@ -106,7 +104,6 @@ fly secrets set DISCORD_BOT_TOKEN=MTQ...
 **Notes:**
 - Non-loopback binds (`--bind lan`) require `CLAWDBOT_GATEWAY_TOKEN` for security.
 - Treat these tokens like passwords.
-- **Prefer env vars over config file** for all API keys and tokens. This keeps secrets out of `poolbot.json` where they could be accidentally exposed or logged.
 
 ## 4) Deploy
 
@@ -139,7 +136,7 @@ fly ssh console
 Create the config directory and file:
 ```bash
 mkdir -p /data
-cat > /data/poolbot.json << 'EOF'
+cat > /data/clawdbot.json << 'EOF'
 {
   "agents": {
     "defaults": {
@@ -185,13 +182,13 @@ cat > /data/poolbot.json << 'EOF'
     "bind": "auto"
   },
   "meta": {
-    "lastTouchedVersion": "2026.1.26"
+    "lastTouchedVersion": "2026.1.24"
   }
 }
 EOF
 ```
 
-**Note:** With `CLAWDBOT_STATE_DIR=/data`, the config path is `/data/poolbot.json`.
+**Note:** With `CLAWDBOT_STATE_DIR=/data`, the config path is `/data/clawdbot.json`.
 
 **Note:** The Discord token can come from either:
 - Environment variable: `DISCORD_BOT_TOKEN` (recommended for secrets)
@@ -214,7 +211,7 @@ Open in browser:
 fly open
 ```
 
-Or visit `https://my-poolbot.fly.dev/`
+Or visit `https://my-clawdbot.fly.dev/`
 
 Paste your gateway token (the one from `CLAWDBOT_GATEWAY_TOKEN`) to authenticate.
 
@@ -278,11 +275,11 @@ The lock file is at `/data/gateway.*.lock` (not in a subdirectory).
 
 ### Config Not Being Read
 
-If using `--allow-unconfigured`, the gateway creates a minimal config. Your custom config at `/data/poolbot.json` should be read on restart.
+If using `--allow-unconfigured`, the gateway creates a minimal config. Your custom config at `/data/clawdbot.json` should be read on restart.
 
 Verify the config exists:
 ```bash
-fly ssh console --command "cat /data/poolbot.json"
+fly ssh console --command "cat /data/clawdbot.json"
 ```
 
 ### Writing Config via SSH
@@ -291,16 +288,16 @@ The `fly ssh console -C` command doesn't support shell redirection. To write a c
 
 ```bash
 # Use echo + tee (pipe from local to remote)
-echo '{"your":"config"}' | fly ssh console -C "tee /data/poolbot.json"
+echo '{"your":"config"}' | fly ssh console -C "tee /data/clawdbot.json"
 
 # Or use sftp
 fly sftp shell
-> put /local/path/config.json /data/poolbot.json
+> put /local/path/config.json /data/clawdbot.json
 ```
 
 **Note:** `fly sftp` may fail if the file already exists. Delete first:
 ```bash
-fly ssh console --command "rm /data/poolbot.json"
+fly ssh console --command "rm /data/clawdbot.json"
 ```
 
 ### State Not Persisting
@@ -340,114 +337,6 @@ fly machine update <machine-id> --vm-memory 2048 --command "node dist/index.js g
 
 **Note:** After `fly deploy`, the machine command may reset to what's in `fly.toml`. If you made manual changes, re-apply them after deploy.
 
-## Private Deployment (Hardened)
-
-By default, Fly allocates public IPs, making your gateway accessible at `https://your-app.fly.dev`. This is convenient but means your deployment is discoverable by internet scanners (Shodan, Censys, etc.).
-
-For a hardened deployment with **no public exposure**, use the private template.
-
-### When to use private deployment
-
-- You only make **outbound** calls/messages (no inbound webhooks)
-- You use **ngrok or Tailscale** tunnels for any webhook callbacks
-- You access the gateway via **SSH, proxy, or WireGuard** instead of browser
-- You want the deployment **hidden from internet scanners**
-
-### Setup
-
-Use `fly.private.toml` instead of the standard config:
-
-```bash
-# Deploy with private config
-fly deploy -c fly.private.toml
-```
-
-Or convert an existing deployment:
-
-```bash
-# List current IPs
-fly ips list -a my-poolbot
-
-# Release public IPs
-fly ips release <public-ipv4> -a my-poolbot
-fly ips release <public-ipv6> -a my-poolbot
-
-# Switch to private config so future deploys don't re-allocate public IPs
-# (remove [http_service] or deploy with the private template)
-fly deploy -c fly.private.toml
-
-# Allocate private-only IPv6
-fly ips allocate-v6 --private -a my-poolbot
-```
-
-After this, `fly ips list` should show only a `private` type IP:
-```
-VERSION  IP                   TYPE             REGION
-v6       fdaa:x:x:x:x::x      private          global
-```
-
-### Accessing a private deployment
-
-Since there's no public URL, use one of these methods:
-
-**Option 1: Local proxy (simplest)**
-```bash
-# Forward local port 3000 to the app
-fly proxy 3000:3000 -a my-poolbot
-
-# Then open http://localhost:3000 in browser
-```
-
-**Option 2: WireGuard VPN**
-```bash
-# Create WireGuard config (one-time)
-fly wireguard create
-
-# Import to WireGuard client, then access via internal IPv6
-# Example: http://[fdaa:x:x:x:x::x]:3000
-```
-
-**Option 3: SSH only**
-```bash
-fly ssh console -a my-poolbot
-```
-
-### Webhooks with private deployment
-
-If you need webhook callbacks (Twilio, Telnyx, etc.) without public exposure:
-
-1. **ngrok tunnel** - Run ngrok inside the container or as a sidecar
-2. **Tailscale Funnel** - Expose specific paths via Tailscale
-3. **Outbound-only** - Some providers (Twilio) work fine for outbound calls without webhooks
-
-Example voice-call config with ngrok:
-```json
-{
-  "plugins": {
-    "entries": {
-      "voice-call": {
-        "enabled": true,
-        "config": {
-          "provider": "twilio",
-          "tunnel": { "provider": "ngrok" }
-        }
-      }
-    }
-  }
-}
-```
-
-The ngrok tunnel runs inside the container and provides a public webhook URL without exposing the Fly app itself.
-
-### Security benefits
-
-| Aspect | Public | Private |
-|--------|--------|---------|
-| Internet scanners | Discoverable | Hidden |
-| Direct attacks | Possible | Blocked |
-| Control UI access | Browser | Proxy/VPN |
-| Webhook delivery | Direct | Via tunnel |
-
 ## Notes
 
 - Fly.io uses **x86 architecture** (not ARM)

package/docs/platforms/hetzner.md

@@ -1,25 +1,25 @@
 ---
-summary: "Run Pool Bot Gateway 24/7 on a cheap Hetzner VPS (Docker) with durable state and baked-in binaries"
+summary: "Run Clawdbot Gateway 24/7 on a cheap Hetzner VPS (Docker) with durable state and baked-in binaries"
 read_when:
-  - You want Pool Bot running 24/7 on a cloud VPS (not your laptop)
+  - You want Clawdbot running 24/7 on a cloud VPS (not your laptop)
   - You want a production-grade, always-on Gateway on your own VPS
   - You want full control over persistence, binaries, and restart behavior
-  - You are running Pool Bot in Docker on Hetzner or a similar provider
+  - You are running Clawdbot in Docker on Hetzner or a similar provider
 ---
 
-# Pool Bot on Hetzner (Docker, Production VPS Guide)
+# Clawdbot on Hetzner (Docker, Production VPS Guide)
 
 ## Goal
-Run a persistent Pool Bot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior.
+Run a persistent Clawdbot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior.
 
-If you want “Pool Bot 24/7 for ~$5”, this is the simplest reliable setup.
+If you want “Clawdbot 24/7 for ~$5”, this is the simplest reliable setup.
 Hetzner pricing changes; pick the smallest Debian/Ubuntu VPS and scale up if you hit OOMs.
 
 ## What are we doing (simple terms)?
 
 - Rent a small Linux server (Hetzner VPS)
 - Install Docker (isolated app runtime)
-- Start the Pool Bot Gateway in Docker
+- Start the Clawdbot Gateway in Docker
 - Persist `~/.clawdbot` + `~/clawd` on the host (survives restarts/rebuilds)
 - Access the Control UI from your laptop via an SSH tunnel
 
@@ -37,7 +37,7 @@ For the generic Docker flow, see [Docker](/install/docker).
 
 1) Provision Hetzner VPS  
 2) Install Docker  
-3) Clone Pool Bot repository  
+3) Clone Clawdbot repository  
 4) Create persistent host directories  
 5) Configure `.env` and `docker-compose.yml`  
 6) Bake required binaries into the image  
@@ -93,11 +93,11 @@ docker compose version
 
 ---
 
-## 3) Clone the Pool Bot repository
+## 3) Clone the Clawdbot repository
 
 ```bash
-git clone https://github.com/poolbot/poolbot.git
-cd poolbot
+git clone https://github.com/clawdbot/clawdbot.git
+cd clawdbot
 ```
 
 This guide assumes you will build a custom image to guarantee binary persistence.
@@ -125,7 +125,7 @@ chown -R 1000:1000 /root/clawd
 Create `.env` in the repository root.
 
 ```bash
-CLAWDBOT_IMAGE=poolbot:latest
+CLAWDBOT_IMAGE=clawdbot:latest
 CLAWDBOT_GATEWAY_TOKEN=change-me-now
 CLAWDBOT_GATEWAY_BIND=lan
 CLAWDBOT_GATEWAY_PORT=18789
@@ -153,7 +153,7 @@ Create or update `docker-compose.yml`.
 
 ```yaml
 services:
-  poolbot-gateway:
+  clawdbot-gateway:
     image: ${CLAWDBOT_IMAGE}
     build: .
     restart: unless-stopped
@@ -259,15 +259,15 @@ CMD ["node","dist/index.js"]
 
 ```bash
 docker compose build
-docker compose up -d poolbot-gateway
+docker compose up -d clawdbot-gateway
 ```
 
 Verify binaries:
 
 ```bash
-docker compose exec poolbot-gateway which gog
-docker compose exec poolbot-gateway which goplaces
-docker compose exec poolbot-gateway which wacli
+docker compose exec clawdbot-gateway which gog
+docker compose exec clawdbot-gateway which goplaces
+docker compose exec clawdbot-gateway which wacli
 ```
 
 Expected output:
@@ -283,7 +283,7 @@ Expected output:
 ## 9) Verify Gateway
 
 ```bash
-docker compose logs -f poolbot-gateway
+docker compose logs -f clawdbot-gateway
 ```
 
 Success:
@@ -308,12 +308,12 @@ Paste your gateway token.
 
 ## What persists where (source of truth)
 
-Pool Bot runs in Docker, but Docker is not the source of truth.
+Clawdbot runs in Docker, but Docker is not the source of truth.
 All long-lived state must survive restarts, rebuilds, and reboots.
 
 | Component | Location | Persistence mechanism | Notes |
 |---|---|---|---|
-| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `poolbot.json`, tokens |
+| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `clawdbot.json`, tokens |
 | Model auth profiles | `/home/node/.clawdbot/` | Host volume mount | OAuth tokens, API keys |
 | Skill configs | `/home/node/.clawdbot/skills/` | Host volume mount | Skill-level state |
 | Agent workspace | `/home/node/clawd/` | Host volume mount | Code and agent artifacts |