@poolzin/pool-bot 2026.1.26 → 2026.1.30

package/docs/install/index.md

@@ -1,7 +1,7 @@
 ---
-summary: "Install Clawdbot (recommended installer, global install, or from source)"
+summary: "Install Pool Bot (recommended installer, global install, or from source)"
 read_when:
-  - Installing Clawdbot
+  - Installing Pool Bot
   - You want to install from GitHub
 ---
 
@@ -12,19 +12,19 @@ Use the installer unless you have a reason not to. It sets up the CLI and runs o
 ## Quick install (recommended)
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash
+curl -fsSL https://molt.bot/install.sh | bash
 ```
 
 Windows (PowerShell):
 
 ```powershell
-iwr -useb https://clawd.bot/install.ps1 | iex
+iwr -useb https://molt.bot/install.ps1 | iex
 ```
 
 Next step (if you skipped onboarding):
 
 ```bash
-clawdbot onboard --install-daemon
+poolbot onboard --install-daemon
 ```
 
 ## System requirements
@@ -37,16 +37,16 @@ clawdbot onboard --install-daemon
 
 ### 1) Installer script (recommended)
 
-Installs `clawdbot` globally via npm and runs onboarding.
+Installs `poolbot` globally via npm and runs onboarding.
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash
+curl -fsSL https://molt.bot/install.sh | bash
 ```
 
 Installer flags:
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --help
+curl -fsSL https://molt.bot/install.sh | bash -s -- --help
 ```
 
 Details: [Installer internals](/install/installer).
@@ -54,7 +54,7 @@ Details: [Installer internals](/install/installer).
 Non-interactive (skip onboarding):
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --no-onboard
+curl -fsSL https://molt.bot/install.sh | bash -s -- --no-onboard
 ```
 
 ### 2) Global install (manual)
@@ -62,13 +62,13 @@ curl -fsSL https://clawd.bot/install.sh | bash -s -- --no-onboard
 If you already have Node:
 
 ```bash
-npm install -g clawdbot@latest
+npm install -g poolbot@latest
 ```
 
 If you have libvips installed globally (common on macOS via Homebrew) and `sharp` fails to install, force prebuilt binaries:
 
 ```bash
-SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g clawdbot@latest
+SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g poolbot@latest
 ```
 
 If you see `sharp: Please add node-gyp to your dependencies`, either install build tooling (macOS: Xcode CLT + `npm install -g node-gyp`) or use the `SHARP_IGNORE_GLOBAL_LIBVIPS=1` workaround above to skip the native build.
@@ -76,27 +76,27 @@ If you see `sharp: Please add node-gyp to your dependencies`, either install bui
 Or:
 
 ```bash
-pnpm add -g clawdbot@latest
+pnpm add -g poolbot@latest
 ```
 
 Then:
 
 ```bash
-clawdbot onboard --install-daemon
+poolbot onboard --install-daemon
 ```
 
 ### 3) From source (contributors/dev)
 
 ```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
 ```
 
-Tip: if you don’t have a global install yet, run repo commands via `pnpm clawdbot ...`.
+Tip: if you don’t have a global install yet, run repo commands via `pnpm poolbot ...`.
 
 ### 4) Other install options
 
@@ -107,32 +107,32 @@ Tip: if you don’t have a global install yet, run repo commands via `pnpm clawd
 
 ## After install
 
-- Run onboarding: `clawdbot onboard --install-daemon`
-- Quick check: `clawdbot doctor`
-- Check gateway health: `clawdbot status` + `clawdbot health`
-- Open the dashboard: `clawdbot dashboard`
+- Run onboarding: `poolbot onboard --install-daemon`
+- Quick check: `poolbot doctor`
+- Check gateway health: `poolbot status` + `poolbot health`
+- Open the dashboard: `poolbot dashboard`
 
 ## Install method: npm vs git (installer)
 
 The installer supports two methods:
 
-- `npm` (default): `npm install -g clawdbot@latest`
+- `npm` (default): `npm install -g poolbot@latest`
 - `git`: clone/build from GitHub and run from a source checkout
 
 ### CLI flags
 
 ```bash
 # Explicit npm
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method npm
+curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method npm
 
 # Install from GitHub (source checkout)
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git
+curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git
 ```
 
 Common flags:
 
 - `--install-method npm|git`
-- `--git-dir <path>` (default: `~/clawdbot`)
+- `--git-dir <path>` (default: `~/poolbot`)
 - `--no-git-update` (skip `git pull` when using an existing checkout)
 - `--no-prompt` (disable prompts; required in CI/automation)
 - `--dry-run` (print what would happen; make no changes)
@@ -150,7 +150,7 @@ Equivalent env vars (useful for automation):
 - `CLAWDBOT_NO_ONBOARD=1`
 - `SHARP_IGNORE_GLOBAL_LIBVIPS=0|1` (default: `1`; avoids `sharp` building against system libvips)
 
-## Troubleshooting: `clawdbot` not found (PATH)
+## Troubleshooting: `poolbot` not found (PATH)
 
 Quick diagnosis:
 
@@ -161,7 +161,7 @@ npm prefix -g
 echo "$PATH"
 ```
 
-If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `clawdbot`).
+If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `poolbot`).
 
 Fix: add it to your shell startup file (zsh: `~/.zshrc`, bash: `~/.bashrc`):
 
@@ -177,4 +177,5 @@ Then open a new terminal (or `rehash` in zsh / `hash -r` in bash).
 ## Update / uninstall
 
 - Updates: [Updating](/install/updating)
+- Migrate to a new machine: [Migrating](/install/migrating)
 - Uninstall: [Uninstall](/install/uninstall)

package/docs/install/installer.md

@@ -1,32 +1,32 @@
 ---
 summary: "How the installer scripts work (install.sh + install-cli.sh), flags, and automation"
 read_when:
-  - You want to understand `clawd.bot/install.sh`
+  - You want to understand `molt.bot/install.sh`
   - You want to automate installs (CI / headless)
   - You want to install from a GitHub checkout
 ---
 
 # Installer internals
 
-Clawdbot ships two installer scripts (served from `clawd.bot`):
+Pool Bot ships two installer scripts (served from `molt.bot`):
 
-- `https://clawd.bot/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout)
-- `https://clawd.bot/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node)
- - `https://clawd.bot/install.ps1` — Windows PowerShell installer (npm by default; optional git install)
+- `https://molt.bot/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout)
+- `https://molt.bot/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node)
+ - `https://molt.bot/install.ps1` — Windows PowerShell installer (npm by default; optional git install)
 
 To see the current flags/behavior, run:
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --help
+curl -fsSL https://molt.bot/install.sh | bash -s -- --help
 ```
 
 Windows (PowerShell) help:
 
 ```powershell
-& ([scriptblock]::Create((iwr -useb https://clawd.bot/install.ps1))) -?
+& ([scriptblock]::Create((iwr -useb https://molt.bot/install.ps1))) -?
 ```
 
-If the installer completes but `clawdbot` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity).
+If the installer completes but `poolbot` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity).
 
 ## install.sh (recommended)
 
@@ -35,22 +35,22 @@ What it does (high level):
 - Detect OS (macOS / Linux / WSL).
 - Ensure Node.js **22+** (macOS via Homebrew; Linux via NodeSource).
 - Choose install method:
-  - `npm` (default): `npm install -g clawdbot@latest`
+  - `npm` (default): `npm install -g poolbot@latest`
   - `git`: clone/build a source checkout and install a wrapper script
 - On Linux: avoid global npm permission errors by switching npm’s prefix to `~/.npm-global` when needed.
-- If upgrading an existing install: runs `clawdbot doctor --non-interactive` (best effort).
-- For git installs: runs `clawdbot doctor --non-interactive` after install/update (best effort).
+- If upgrading an existing install: runs `poolbot doctor --non-interactive` (best effort).
+- For git installs: runs `poolbot doctor --non-interactive` after install/update (best effort).
 - Mitigates `sharp` native install gotchas by defaulting `SHARP_IGNORE_GLOBAL_LIBVIPS=1` (avoids building against system libvips).
 
 If you *want* `sharp` to link against a globally-installed libvips (or you’re debugging), set:
 
 ```bash
-SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://clawd.bot/install.sh | bash
+SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://molt.bot/install.sh | bash
 ```
 
 ### Discoverability / “git install” prompt
 
-If you run the installer while **already inside a Clawdbot source checkout** (detected via `package.json` + `pnpm-workspace.yaml`), it prompts:
+If you run the installer while **already inside a Pool Bot source checkout** (detected via `package.json` + `pnpm-workspace.yaml`), it prompts:
 
 - update and use this checkout (`git`)
 - or migrate to the global npm install (`npm`)
@@ -73,12 +73,12 @@ On some Linux setups (especially after installing Node via the system package ma
 
 ## install-cli.sh (non-root CLI installer)
 
-This script installs `clawdbot` into a prefix (default: `~/.clawdbot`) and also installs a dedicated Node runtime under that prefix, so it can work on machines where you don’t want to touch the system Node/npm.
+This script installs `poolbot` into a prefix (default: `~/.poolbot`) and also installs a dedicated Node runtime under that prefix, so it can work on machines where you don’t want to touch the system Node/npm.
 
 Help:
 
 ```bash
-curl -fsSL https://clawd.bot/install-cli.sh | bash -s -- --help
+curl -fsSL https://molt.bot/install-cli.sh | bash -s -- --help
 ```
 
 ## install.ps1 (Windows PowerShell)
@@ -87,22 +87,22 @@ What it does (high level):
 
 - Ensure Node.js **22+** (winget/Chocolatey/Scoop or manual).
 - Choose install method:
-  - `npm` (default): `npm install -g clawdbot@latest`
+  - `npm` (default): `npm install -g poolbot@latest`
   - `git`: clone/build a source checkout and install a wrapper script
-- Runs `clawdbot doctor --non-interactive` on upgrades and git installs (best effort).
+- Runs `poolbot doctor --non-interactive` on upgrades and git installs (best effort).
 
 Examples:
 
 ```powershell
-iwr -useb https://clawd.bot/install.ps1 | iex
+iwr -useb https://molt.bot/install.ps1 | iex
 ```
 
 ```powershell
-iwr -useb https://clawd.bot/install.ps1 | iex -InstallMethod git
+iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git
 ```
 
 ```powershell
-iwr -useb https://clawd.bot/install.ps1 | iex -InstallMethod git -GitDir "C:\\clawdbot"
+iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git -GitDir "C:\\poolbot"
 ```
 
 Environment variables:
@@ -118,5 +118,5 @@ Git for Windows link (`https://git-scm.com/download/win`) and exit.
 Common Windows issues:
 
 - **npm error spawn git / ENOENT**: install Git for Windows and reopen PowerShell, then rerun the installer.
-- **"clawdbot" is not recognized**: your npm global bin folder is not on PATH. Most systems use
+- **"poolbot" is not recognized**: your npm global bin folder is not on PATH. Most systems use
   `%AppData%\\npm`. You can also run `npm config get prefix` and add `\\bin` to PATH, then reopen PowerShell.

package/docs/install/migrating.md

@@ -0,0 +1,190 @@
+---
+summary: "Move (migrate) a Pool Bot install from one machine to another"
+read_when:
+  - You are moving Pool Bot to a new laptop/server
+  - You want to preserve sessions, auth, and channel logins (WhatsApp, etc.)
+---
+# Migrating Pool Bot to a new machine
+
+This guide migrates a Pool Bot Gateway from one machine to another **without redoing onboarding**.
+
+The migration is simple conceptually:
+
+- Copy the **state directory** (`$CLAWDBOT_STATE_DIR`, default: `~/.poolbot/`) — this includes config, auth, sessions, and channel state.
+- Copy your **workspace** (`~/clawd/` by default) — this includes your agent files (memory, prompts, etc.).
+
+But there are common footguns around **profiles**, **permissions**, and **partial copies**.
+
+## Before you start (what you are migrating)
+
+### 1) Identify your state directory
+
+Most installs use the default:
+
+- **State dir:** `~/.poolbot/`
+
+But it may be different if you use:
+
+- `--profile <name>` (often becomes `~/.poolbot-<profile>/`)
+- `CLAWDBOT_STATE_DIR=/some/path`
+
+If you’re not sure, run on the **old** machine:
+
+```bash
+poolbot status
+```
+
+Look for mentions of `CLAWDBOT_STATE_DIR` / profile in the output. If you run multiple gateways, repeat for each profile.
+
+### 2) Identify your workspace
+
+Common defaults:
+
+- `~/clawd/` (recommended workspace)
+- a custom folder you created
+
+Your workspace is where files like `MEMORY.md`, `USER.md`, and `memory/*.md` live.
+
+### 3) Understand what you will preserve
+
+If you copy **both** the state dir and workspace, you keep:
+
+- Gateway configuration (`poolbot.json`)
+- Auth profiles / API keys / OAuth tokens
+- Session history + agent state
+- Channel state (e.g. WhatsApp login/session)
+- Your workspace files (memory, skills notes, etc.)
+
+If you copy **only** the workspace (e.g., via Git), you do **not** preserve:
+
+- sessions
+- credentials
+- channel logins
+
+Those live under `$CLAWDBOT_STATE_DIR`.
+
+## Migration steps (recommended)
+
+### Step 0 — Make a backup (old machine)
+
+On the **old** machine, stop the gateway first so files aren’t changing mid-copy:
+
+```bash
+poolbot gateway stop
+```
+
+(Optional but recommended) archive the state dir and workspace:
+
+```bash
+# Adjust paths if you use a profile or custom locations
+cd ~
+tar -czf poolbot-state.tgz .poolbot
+
+tar -czf clawd-workspace.tgz clawd
+```
+
+If you have multiple profiles/state dirs (e.g. `~/.poolbot-main`, `~/.poolbot-work`), archive each.
+
+### Step 1 — Install Pool Bot on the new machine
+
+On the **new** machine, install the CLI (and Node if needed):
+
+- See: [Install](/install)
+
+At this stage, it’s OK if onboarding creates a fresh `~/.poolbot/` — you will overwrite it in the next step.
+
+### Step 2 — Copy the state dir + workspace to the new machine
+
+Copy **both**:
+
+- `$CLAWDBOT_STATE_DIR` (default `~/.poolbot/`)
+- your workspace (default `~/clawd/`)
+
+Common approaches:
+
+- `scp` the tarballs and extract
+- `rsync -a` over SSH
+- external drive
+
+After copying, ensure:
+
+- Hidden directories were included (e.g. `.poolbot/`)
+- File ownership is correct for the user running the gateway
+
+### Step 3 — Run Doctor (migrations + service repair)
+
+On the **new** machine:
+
+```bash
+poolbot doctor
+```
+
+Doctor is the “safe boring” command. It repairs services, applies config migrations, and warns about mismatches.
+
+Then:
+
+```bash
+poolbot gateway restart
+poolbot status
+```
+
+## Common footguns (and how to avoid them)
+
+### Footgun: profile / state-dir mismatch
+
+If you ran the old gateway with a profile (or `CLAWDBOT_STATE_DIR`), and the new gateway uses a different one, you’ll see symptoms like:
+
+- config changes not taking effect
+- channels missing / logged out
+- empty session history
+
+Fix: run the gateway/service using the **same** profile/state dir you migrated, then rerun:
+
+```bash
+poolbot doctor
+```
+
+### Footgun: copying only `poolbot.json`
+
+`poolbot.json` is not enough. Many providers store state under:
+
+- `$CLAWDBOT_STATE_DIR/credentials/`
+- `$CLAWDBOT_STATE_DIR/agents/<agentId>/...`
+
+Always migrate the entire `$CLAWDBOT_STATE_DIR` folder.
+
+### Footgun: permissions / ownership
+
+If you copied as root or changed users, the gateway may fail to read credentials/sessions.
+
+Fix: ensure the state dir + workspace are owned by the user running the gateway.
+
+### Footgun: migrating between remote/local modes
+
+- If your UI (WebUI/TUI) points at a **remote** gateway, the remote host owns the session store + workspace.
+- Migrating your laptop won’t move the remote gateway’s state.
+
+If you’re in remote mode, migrate the **gateway host**.
+
+### Footgun: secrets in backups
+
+`$CLAWDBOT_STATE_DIR` contains secrets (API keys, OAuth tokens, WhatsApp creds). Treat backups like production secrets:
+
+- store encrypted
+- avoid sharing over insecure channels
+- rotate keys if you suspect exposure
+
+## Verification checklist
+
+On the new machine, confirm:
+
+- `poolbot status` shows the gateway running
+- Your channels are still connected (e.g. WhatsApp doesn’t require re-pair)
+- The dashboard opens and shows existing sessions
+- Your workspace files (memory, configs) are present
+
+## Related
+
+- [Doctor](/gateway/doctor)
+- [Gateway troubleshooting](/gateway/troubleshooting)
+- [Where does Pool Bot store its data?](/help/faq#where-does-poolbot-store-its-data)

package/docs/install/nix.md

@@ -1,5 +1,5 @@
 ---
-summary: "Install Clawdbot declaratively with Nix"
+summary: "Install Pool Bot declaratively with Nix"
 read_when:
   - You want reproducible, rollback-able installs
   - You're already using Nix/NixOS/Home Manager
@@ -8,30 +8,30 @@ read_when:
 
 # Nix Installation
 
-The recommended way to run Clawdbot with Nix is via **[nix-clawdbot](https://github.com/clawdbot/nix-clawdbot)** — a batteries-included Home Manager module.
+The recommended way to run Pool Bot with Nix is via **[nix-poolbot](https://github.com/poolbot/nix-poolbot)** — a batteries-included Home Manager module.
 
 ## Quick Start
 
 Paste this to your AI agent (Claude, Cursor, etc.):
 
 ```text
-I want to set up nix-clawdbot on my Mac.
-Repository: github:clawdbot/nix-clawdbot
+I want to set up nix-poolbot on my Mac.
+Repository: github:poolbot/nix-poolbot
 
 What I need you to do:
 1. Check if Determinate Nix is installed (if not, install it)
-2. Create a local flake at ~/code/clawdbot-local using templates/agent-first/flake.nix
+2. Create a local flake at ~/code/poolbot-local using templates/agent-first/flake.nix
 3. Help me create a Telegram bot (@BotFather) and get my chat ID (@userinfobot)
 4. Set up secrets (bot token, Anthropic key) - plain files at ~/.secrets/ is fine
 5. Fill in the template placeholders and run home-manager switch
 6. Verify: launchd running, bot responds to messages
 
-Reference the nix-clawdbot README for module options.
+Reference the nix-poolbot README for module options.
 ```
 
-> **📦 Full guide: [github.com/clawdbot/nix-clawdbot](https://github.com/clawdbot/nix-clawdbot)**
+> **📦 Full guide: [github.com/poolbot/nix-poolbot](https://github.com/poolbot/nix-poolbot)**
 >
-> The nix-clawdbot repo is the source of truth for Nix installation. This page is just a quick overview.
+> The nix-poolbot repo is the source of truth for Nix installation. This page is just a quick overview.
 
 ## What you get
 
@@ -44,9 +44,9 @@ Reference the nix-clawdbot README for module options.
 
 ## Nix Mode Runtime Behavior
 
-When `CLAWDBOT_NIX_MODE=1` is set (automatic with nix-clawdbot):
+When `CLAWDBOT_NIX_MODE=1` is set (automatic with nix-poolbot):
 
-Clawdbot supports a **Nix mode** that makes configuration deterministic and disables auto-install flows.
+Pool Bot supports a **Nix mode** that makes configuration deterministic and disables auto-install flows.
 Enable it by exporting:
 
 ```bash
@@ -57,15 +57,15 @@ On macOS, the GUI app does not automatically inherit shell env vars. You can
 also enable Nix mode via defaults:
 
 ```bash
-defaults write com.clawdbot.mac clawdbot.nixMode -bool true
+defaults write com.poolbot.mac poolbot.nixMode -bool true
 ```
 
 ### Config + state paths
 
-Clawdbot reads JSON5 config from `CLAWDBOT_CONFIG_PATH` and stores mutable data in `CLAWDBOT_STATE_DIR`.
+Pool Bot reads JSON5 config from `CLAWDBOT_CONFIG_PATH` and stores mutable data in `CLAWDBOT_STATE_DIR`.
 
-- `CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`)
-- `CLAWDBOT_CONFIG_PATH` (default: `$CLAWDBOT_STATE_DIR/clawdbot.json`)
+- `CLAWDBOT_STATE_DIR` (default: `~/.poolbot`)
+- `CLAWDBOT_CONFIG_PATH` (default: `$CLAWDBOT_STATE_DIR/poolbot.json`)
 
 When running under Nix, set these explicitly to Nix-managed locations so runtime state and config
 stay out of the immutable store.
@@ -81,15 +81,15 @@ stay out of the immutable store.
 The macOS packaging flow expects a stable Info.plist template at:
 
 ```
-apps/macos/Sources/Clawdbot/Resources/Info.plist
+apps/macos/Sources/Pool Bot/Resources/Info.plist
 ```
 
-[`scripts/package-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields
+[`scripts/package-mac-app.sh`](https://github.com/poolbot/poolbot/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields
 (bundle ID, version/build, Git SHA, Sparkle keys). This keeps the plist deterministic for SwiftPM
 packaging and Nix builds (which do not rely on a full Xcode toolchain).
 
 ## Related
 
-- [nix-clawdbot](https://github.com/clawdbot/nix-clawdbot) — full setup guide
+- [nix-poolbot](https://github.com/poolbot/nix-poolbot) — full setup guide
 - [Wizard](/start/wizard) — non-Nix CLI setup
 - [Docker](/install/docker) — containerized setup

package/docs/install/node.md

@@ -1,16 +1,17 @@
 ---
+title: "Node.js + npm (PATH sanity)"
 summary: "Node.js + npm install sanity: versions, PATH, and global installs"
 read_when:
-  - You installed Clawdbot but `clawdbot` is “command not found”
-  - You’re setting up Node.js/npm on a new machine
-  - `npm install -g ...` fails with permissions or PATH issues
+  - "You installed Pool Bot but `poolbot` is “command not found”"
+  - "You’re setting up Node.js/npm on a new machine"
+  - "npm install -g ... fails with permissions or PATH issues"
 ---
 
 # Node.js + npm (PATH sanity)
 
-Clawdbot’s runtime baseline is **Node 22+**.
+Pool Bot’s runtime baseline is **Node 22+**.
 
-If you can run `npm install -g clawdbot@latest` but later see `clawdbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
+If you can run `npm install -g poolbot@latest` but later see `poolbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH.
 
 ## Quick diagnosis
 
@@ -23,7 +24,7 @@ npm prefix -g
 echo "$PATH"
 ```
 
-If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `clawdbot`).
+If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `poolbot`).
 
 ## Fix: put npm’s global bin dir on PATH