@poolzin/pool-bot 2026.1.26 → 2026.1.30

package/docs/index.md

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

package/docs/install/ansible.md

@@ -1,5 +1,5 @@
 ---
-summary: "Automated, hardened Clawdbot installation with Ansible, Tailscale VPN, and firewall isolation"
+summary: "Automated, hardened Pool Bot installation with Ansible, Tailscale VPN, and firewall isolation"
 read_when:
   - You want automated server deployment with security hardening
   - You need firewall-isolated setup with VPN access
@@ -8,19 +8,19 @@ read_when:
 
 # Ansible Installation
 
-The recommended way to deploy Clawdbot to production servers is via **[clawdbot-ansible](https://github.com/clawdbot/clawdbot-ansible)** — an automated installer with security-first architecture.
+The recommended way to deploy Pool Bot to production servers is via **[poolbot-ansible](https://github.com/poolbot/poolbot-ansible)** — an automated installer with security-first architecture.
 
 ## Quick Start
 
 One-command install:
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/clawdbot/clawdbot-ansible/main/install.sh | bash
+curl -fsSL https://raw.githubusercontent.com/poolbot/poolbot-ansible/main/install.sh | bash
 ```
 
-> **📦 Full guide: [github.com/clawdbot/clawdbot-ansible](https://github.com/clawdbot/clawdbot-ansible)**
+> **📦 Full guide: [github.com/poolbot/poolbot-ansible](https://github.com/poolbot/poolbot-ansible)**
 >
-> The clawdbot-ansible repo is the source of truth for Ansible deployment. This page is a quick overview.
+> The poolbot-ansible repo is the source of truth for Ansible deployment. This page is a quick overview.
 
 ## What You Get
 
@@ -46,22 +46,22 @@ The Ansible playbook installs and configures:
 2. **UFW firewall** (SSH + Tailscale ports only)
 3. **Docker CE + Compose V2** (for agent sandboxes)
 4. **Node.js 22.x + pnpm** (runtime dependencies)
-5. **Clawdbot** (host-based, not containerized)
+5. **Pool Bot** (host-based, not containerized)
 6. **Systemd service** (auto-start with security hardening)
 
 Note: The gateway runs **directly on the host** (not in Docker), but agent sandboxes use Docker for isolation. See [Sandboxing](/gateway/sandboxing) for details.
 
 ## Post-Install Setup
 
-After installation completes, switch to the clawdbot user:
+After installation completes, switch to the poolbot user:
 
 ```bash
-sudo -i -u clawdbot
+sudo -i -u poolbot
 ```
 
 The post-install script will guide you through:
 
-1. **Onboarding wizard**: Configure Clawdbot settings
+1. **Onboarding wizard**: Configure Pool Bot settings
 2. **Provider login**: Connect WhatsApp/Telegram/Discord/Signal
 3. **Gateway testing**: Verify the installation
 4. **Tailscale setup**: Connect to your VPN mesh
@@ -70,17 +70,17 @@ The post-install script will guide you through:
 
 ```bash
 # Check service status
-sudo systemctl status clawdbot
+sudo systemctl status poolbot
 
 # View live logs
-sudo journalctl -u clawdbot -f
+sudo journalctl -u poolbot -f
 
 # Restart gateway
-sudo systemctl restart clawdbot
+sudo systemctl restart poolbot
 
-# Provider login (run as clawdbot user)
-sudo -i -u clawdbot
-clawdbot channels login
+# Provider login (run as poolbot user)
+sudo -i -u poolbot
+poolbot channels login
 ```
 
 ## Security Architecture
@@ -117,8 +117,8 @@ If you prefer manual control over the automation:
 sudo apt update && sudo apt install -y ansible git
 
 # 2. Clone repository
-git clone https://github.com/clawdbot/clawdbot-ansible.git
-cd clawdbot-ansible
+git clone https://github.com/poolbot/poolbot-ansible.git
+cd poolbot-ansible
 
 # 3. Install Ansible collections
 ansible-galaxy collection install -r requirements.yml
@@ -126,18 +126,18 @@ ansible-galaxy collection install -r requirements.yml
 # 4. Run playbook
 ./run-playbook.sh
 
-# Or run directly (then manually execute /tmp/clawdbot-setup.sh after)
+# Or run directly (then manually execute /tmp/poolbot-setup.sh after)
 # ansible-playbook playbook.yml --ask-become-pass
 ```
 
-## Updating Clawdbot
+## Updating Pool Bot
 
-The Ansible installer sets up Clawdbot for manual updates. See [Updating](/install/updating) for the standard update flow.
+The Ansible installer sets up Pool Bot for manual updates. See [Updating](/install/updating) for the standard update flow.
 
 To re-run the Ansible playbook (e.g., for configuration changes):
 
 ```bash
-cd clawdbot-ansible
+cd poolbot-ansible
 ./run-playbook.sh
 ```
 
@@ -156,14 +156,14 @@ If you're locked out:
 
 ```bash
 # Check logs
-sudo journalctl -u clawdbot -n 100
+sudo journalctl -u poolbot -n 100
 
 # Verify permissions
-sudo ls -la /opt/clawdbot
+sudo ls -la /opt/poolbot
 
 # Test manual start
-sudo -i -u clawdbot
-cd ~/clawdbot
+sudo -i -u poolbot
+cd ~/poolbot
 pnpm start
 ```
 
@@ -174,32 +174,32 @@ pnpm start
 sudo systemctl status docker
 
 # Check sandbox image
-sudo docker images | grep clawdbot-sandbox
+sudo docker images | grep poolbot-sandbox
 
 # Build sandbox image if missing
-cd /opt/clawdbot/clawdbot
-sudo -u clawdbot ./scripts/sandbox-setup.sh
+cd /opt/poolbot/poolbot
+sudo -u poolbot ./scripts/sandbox-setup.sh
 ```
 
 ### Provider login fails
 
-Make sure you're running as the `clawdbot` user:
+Make sure you're running as the `poolbot` user:
 
 ```bash
-sudo -i -u clawdbot
-clawdbot channels login
+sudo -i -u poolbot
+poolbot channels login
 ```
 
 ## Advanced Configuration
 
 For detailed security architecture and troubleshooting:
-- [Security Architecture](https://github.com/clawdbot/clawdbot-ansible/blob/main/docs/security.md)
-- [Technical Details](https://github.com/clawdbot/clawdbot-ansible/blob/main/docs/architecture.md)
-- [Troubleshooting Guide](https://github.com/clawdbot/clawdbot-ansible/blob/main/docs/troubleshooting.md)
+- [Security Architecture](https://github.com/poolbot/poolbot-ansible/blob/main/docs/security.md)
+- [Technical Details](https://github.com/poolbot/poolbot-ansible/blob/main/docs/architecture.md)
+- [Troubleshooting Guide](https://github.com/poolbot/poolbot-ansible/blob/main/docs/troubleshooting.md)
 
 ## Related
 
-- [clawdbot-ansible](https://github.com/clawdbot/clawdbot-ansible) — full deployment guide
+- [poolbot-ansible](https://github.com/poolbot/poolbot-ansible) — full deployment guide
 - [Docker](/install/docker) — containerized gateway setup
 - [Sandboxing](/gateway/sandboxing) — agent sandbox configuration
 - [Multi-Agent Sandbox & Tools](/multi-agent-sandbox-tools) — per-agent isolation

package/docs/install/development-channels.md

@@ -9,7 +9,7 @@ read_when:
 
 Last updated: 2026-01-21
 
-Clawdbot ships three update channels:
+Pool Bot ships three update channels:
 
 - **stable**: npm dist-tag `latest`.
 - **beta**: npm dist-tag `beta` (builds under test).
@@ -23,9 +23,9 @@ without changing the version number — dist-tags are the source of truth for np
 Git checkout:
 
 ```bash
-clawdbot update --channel stable
-clawdbot update --channel beta
-clawdbot update --channel dev
+poolbot update --channel stable
+poolbot update --channel beta
+poolbot update --channel dev
 ```
 
 - `stable`/`beta` check out the latest matching tag (often the same tag).
@@ -34,17 +34,17 @@ clawdbot update --channel dev
 npm/pnpm global install:
 
 ```bash
-clawdbot update --channel stable
-clawdbot update --channel beta
-clawdbot update --channel dev
+poolbot update --channel stable
+poolbot update --channel beta
+poolbot update --channel dev
 ```
 
 This updates via the corresponding npm dist-tag (`latest`, `beta`, `dev`).
 
-When you **explicitly** switch channels with `--channel`, Clawdbot also aligns
+When you **explicitly** switch channels with `--channel`, Pool Bot also aligns
 the install method:
 
-- `dev` ensures a git checkout (default `~/clawdbot`, override with `CLAWDBOT_GIT_DIR`),
+- `dev` ensures a git checkout (default `~/poolbot`, 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.
 
@@ -52,7 +52,7 @@ Tip: if you want stable + dev in parallel, keep two clones and point your gatewa
 
 ## Plugins and channels
 
-When you switch channels with `clawdbot update`, Clawdbot also syncs plugin sources:
+When you switch channels with `poolbot update`, Pool Bot also syncs plugin sources:
 
 - `dev` prefers bundled plugins from the git checkout.
 - `stable` and `beta` restore npm-installed plugin packages.

package/docs/install/docker.md

@@ -1,5 +1,5 @@
 ---
-summary: "Optional Docker-based setup and onboarding for Clawdbot"
+summary: "Optional Docker-based setup and onboarding for Pool Bot"
 read_when:
   - You want a containerized gateway instead of local installs
   - You are validating the Docker flow
@@ -11,12 +11,12 @@ Docker is **optional**. Use it only if you want a containerized gateway or to va
 
 ## Is Docker right for me?
 
-- **Yes**: you want an isolated, throwaway gateway environment or to run Clawdbot on a host without local installs.
+- **Yes**: you want an isolated, throwaway gateway environment or to run Pool Bot on a host without local installs.
 - **No**: you’re running on your own machine and just want the fastest dev loop. Use the normal install flow instead.
 - **Sandboxing note**: agent sandboxing uses Docker too, but it does **not** require the full gateway to run in Docker. See [Sandboxing](/gateway/sandboxing).
 
 This guide covers:
-- Containerized Gateway (full Clawdbot in Docker)
+- Containerized Gateway (full Pool Bot in Docker)
 - Per-session Agent Sandbox (host gateway + Docker-isolated agent tools)
 
 Sandboxing details: [Sandboxing](/gateway/sandboxing)
@@ -53,7 +53,7 @@ After it finishes:
 - Paste the token into the Control UI (Settings → token).
 
 It writes config/workspace on the host:
-- `~/.clawdbot/`
+- `~/.poolbot/`
 - `~/clawd`
 
 Running on a VPS? See [Hetzner (Docker VPS)](/platforms/hetzner).
@@ -61,9 +61,9 @@ Running on a VPS? See [Hetzner (Docker VPS)](/platforms/hetzner).
 ### Manual flow (compose)
 
 ```bash
-docker build -t clawdbot:local -f Dockerfile .
-docker compose run --rm clawdbot-cli onboard
-docker compose up -d clawdbot-gateway
+docker build -t poolbot:local -f Dockerfile .
+docker compose run --rm poolbot-cli onboard
+docker compose up -d poolbot-gateway
 ```
 
 ### Extra mounts (optional)
@@ -71,7 +71,7 @@ docker compose up -d clawdbot-gateway
 If you want to mount additional host directories into the containers, set
 `CLAWDBOT_EXTRA_MOUNTS` before running `docker-setup.sh`. This accepts a
 comma-separated list of Docker bind mounts and applies them to both
-`clawdbot-gateway` and `clawdbot-cli` by generating `docker-compose.extra.yml`.
+`poolbot-gateway` and `poolbot-cli` by generating `docker-compose.extra.yml`.
 
 Example:
 
@@ -97,14 +97,14 @@ named volume here (not a bind path); for bind mounts, use
 Example:
 
 ```bash
-export CLAWDBOT_HOME_VOLUME="clawdbot_home"
+export CLAWDBOT_HOME_VOLUME="poolbot_home"
 ./docker-setup.sh
 ```
 
 You can combine this with extra mounts:
 
 ```bash
-export CLAWDBOT_HOME_VOLUME="clawdbot_home"
+export CLAWDBOT_HOME_VOLUME="poolbot_home"
 export CLAWDBOT_EXTRA_MOUNTS="$HOME/.codex:/home/node/.codex:ro,$HOME/github:/home/node/github:rw"
 ./docker-setup.sh
 ```
@@ -172,17 +172,17 @@ Use the CLI container to configure channels, then restart the gateway if needed.
 
 WhatsApp (QR):
 ```bash
-docker compose run --rm clawdbot-cli channels login
+docker compose run --rm poolbot-cli channels login
 ```
 
 Telegram (bot token):
 ```bash
-docker compose run --rm clawdbot-cli channels add --channel telegram --token "<token>"
+docker compose run --rm poolbot-cli channels add --channel telegram --token "<token>"
 ```
 
 Discord (bot token):
 ```bash
-docker compose run --rm clawdbot-cli channels add --channel discord --token "<token>"
+docker compose run --rm poolbot-cli channels add --channel discord --token "<token>"
 ```
 
 Docs: [WhatsApp](/channels/whatsapp), [Telegram](/channels/telegram), [Discord](/channels/discord)
@@ -190,7 +190,7 @@ Docs: [WhatsApp](/channels/whatsapp), [Telegram](/channels/telegram), [Discord](
 ### Health check
 
 ```bash
-docker compose exec clawdbot-gateway node dist/index.js health --token "$CLAWDBOT_GATEWAY_TOKEN"
+docker compose exec poolbot-gateway node dist/index.js health --token "$CLAWDBOT_GATEWAY_TOKEN"
 ```
 
 ### E2E smoke test (Docker)
@@ -208,7 +208,7 @@ pnpm test:docker:qr
 ### Notes
 
 - Gateway bind defaults to `lan` for container use.
-- The gateway container is the source of truth for sessions (`~/.clawdbot/agents/<agentId>/sessions/`).
+- The gateway container is the source of truth for sessions (`~/.poolbot/agents/<agentId>/sessions/`).
 
 ## Agent Sandbox (host gateway + Docker tools)
 
@@ -242,9 +242,9 @@ precedence, and troubleshooting.
 
 ### Default behavior
 
-- Image: `clawdbot-sandbox:bookworm-slim`
+- Image: `poolbot-sandbox:bookworm-slim`
 - One container per agent
-- Agent workspace access: `workspaceAccess: "none"` (default) uses `~/.clawdbot/sandboxes`
+- Agent workspace access: `workspaceAccess: "none"` (default) uses `~/.poolbot/sandboxes`
   - `"ro"` keeps the sandbox workspace at `/workspace` and mounts the agent workspace read-only at `/agent` (disables `write`/`edit`/`apply_patch`)
   - `"rw"` mounts the agent workspace read/write at `/workspace`
 - Auto-prune: idle > 24h OR age > 7d
@@ -258,9 +258,9 @@ If you plan to install packages in `setupCommand`, note:
 - Default `docker.network` is `"none"` (no egress).
 - `readOnlyRoot: true` blocks package installs.
 - `user` must be root for `apt-get` (omit `user` or set `user: "0:0"`).
-Clawdbot auto-recreates containers when `setupCommand` (or docker config) changes
+Pool Bot auto-recreates containers when `setupCommand` (or docker config) changes
 unless the container was **recently used** (within ~5 minutes). Hot containers
-log a warning with the exact `clawdbot sandbox recreate ...` command.
+log a warning with the exact `poolbot sandbox recreate ...` command.
 
 ```json5
 {
@@ -270,9 +270,9 @@ log a warning with the exact `clawdbot sandbox recreate ...` command.
         mode: "non-main", // off | non-main | all
         scope: "agent", // session | agent | shared (agent is default)
         workspaceAccess: "none", // none | ro | rw
-        workspaceRoot: "~/.clawdbot/sandboxes",
+        workspaceRoot: "~/.poolbot/sandboxes",
         docker: {
-          image: "clawdbot-sandbox:bookworm-slim",
+          image: "poolbot-sandbox:bookworm-slim",
           workdir: "/workspace",
           readOnlyRoot: true,
           tmpfs: ["/tmp", "/var/tmp", "/run"],
@@ -290,7 +290,7 @@ log a warning with the exact `clawdbot sandbox recreate ...` command.
             nproc: 256
           },
           seccompProfile: "/path/to/seccomp.json",
-          apparmorProfile: "clawdbot-sandbox",
+          apparmorProfile: "poolbot-sandbox",
           dns: ["1.1.1.1", "8.8.8.8"],
           extraHosts: ["internal.service:10.0.0.5"]
         },
@@ -325,7 +325,7 @@ Multi-agent: override `agents.defaults.sandbox.{docker,browser,prune}.*` per age
 scripts/sandbox-setup.sh
 ```
 
-This builds `clawdbot-sandbox:bookworm-slim` using `Dockerfile.sandbox`.
+This builds `poolbot-sandbox:bookworm-slim` using `Dockerfile.sandbox`.
 
 ### Sandbox common image (optional)
 If you want a sandbox image with common build tooling (Node, Go, Rust, etc.), build the common image:
@@ -334,11 +334,11 @@ If you want a sandbox image with common build tooling (Node, Go, Rust, etc.), bu
 scripts/sandbox-common-setup.sh
 ```
 
-This builds `clawdbot-sandbox-common:bookworm-slim`. To use it:
+This builds `poolbot-sandbox-common:bookworm-slim`. To use it:
 
 ```json5
 {
-  agents: { defaults: { sandbox: { docker: { image: "clawdbot-sandbox-common:bookworm-slim" } } } }
+  agents: { defaults: { sandbox: { docker: { image: "poolbot-sandbox-common:bookworm-slim" } } } }
 }
 ```
 
@@ -350,7 +350,7 @@ To run the browser tool inside the sandbox, build the browser image:
 scripts/sandbox-browser-setup.sh
 ```
 
-This builds `clawdbot-sandbox-browser:bookworm-slim` using
+This builds `poolbot-sandbox-browser:bookworm-slim` using
 `Dockerfile.sandbox-browser`. The container runs Chromium with CDP enabled and
 an optional noVNC observer (headful via Xvfb).
 
@@ -379,7 +379,7 @@ Custom browser image:
 {
   agents: {
     defaults: {
-      sandbox: { browser: { image: "my-clawdbot-browser" } }
+      sandbox: { browser: { image: "my-poolbot-browser" } }
     }
   }
 }
@@ -398,14 +398,14 @@ Prune rules (`agents.defaults.sandbox.prune`) apply to browser containers too.
 Build your own image and point config to it:
 
 ```bash
-docker build -t my-clawdbot-sbx -f Dockerfile.sandbox .
+docker build -t my-poolbot-sbx -f Dockerfile.sandbox .
 ```
 
 ```json5
 {
   agents: {
     defaults: {
-      sandbox: { docker: { image: "my-clawdbot-sbx" } }
+      sandbox: { docker: { image: "my-poolbot-sbx" } }
     }
   }
 }
@@ -437,11 +437,11 @@ Example:
 
 ## Troubleshooting
 
-- Image missing: build with [`scripts/sandbox-setup.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/sandbox-setup.sh) or set `agents.defaults.sandbox.docker.image`.
+- Image missing: build with [`scripts/sandbox-setup.sh`](https://github.com/poolbot/poolbot/blob/main/scripts/sandbox-setup.sh) or set `agents.defaults.sandbox.docker.image`.
 - Container not running: it will auto-create per session on demand.
 - Permission errors in sandbox: set `docker.user` to a UID:GID that matches your
   mounted workspace ownership (or chown the workspace folder).
-- Custom tools not found: Clawdbot runs commands with `sh -lc` (login shell), which
+- Custom tools not found: Pool Bot runs commands with `sh -lc` (login shell), which
   sources `/etc/profile` and may reset PATH. Set `docker.env.PATH` to prepend your
   custom tool paths (e.g., `/custom/bin:/usr/local/share/npm-global/bin`), or add
   a script under `/etc/profile.d/` in your Dockerfile.