@poolzin/pool-bot 2026.1.26 → 2026.1.30

package/docs/help/faq.md

@@ -1,5 +1,5 @@
 ---
-summary: "Frequently asked questions about Clawdbot setup, configuration, and usage"
+summary: "Frequently asked questions about Pool Bot setup, configuration, and usage"
 ---
 # FAQ
 
@@ -9,7 +9,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 
 - [Quick start and first-run setup](#quick-start-and-firstrun-setup)
   - [Im stuck whats the fastest way to get unstuck?](#im-stuck-whats-the-fastest-way-to-get-unstuck)
-  - [What’s the recommended way to install and set up Clawdbot?](#whats-the-recommended-way-to-install-and-set-up-clawdbot)
+  - [What’s the recommended way to install and set up Pool Bot?](#whats-the-recommended-way-to-install-and-set-up-poolbot)
   - [How do I open the dashboard after onboarding?](#how-do-i-open-the-dashboard-after-onboarding)
   - [How do I authenticate the dashboard (token) on localhost vs remote?](#how-do-i-authenticate-the-dashboard-token-on-localhost-vs-remote)
   - [What runtime do I need?](#what-runtime-do-i-need)
@@ -18,16 +18,16 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [It is stuck on "wake up my friend" / onboarding will not hatch. What now?](#it-is-stuck-on-wake-up-my-friend-onboarding-will-not-hatch-what-now)
   - [Can I migrate my setup to a new machine (Mac mini) without redoing onboarding?](#can-i-migrate-my-setup-to-a-new-machine-mac-mini-without-redoing-onboarding)
   - [Where do I see what’s new in the latest version?](#where-do-i-see-whats-new-in-the-latest-version)
-  - [I can't access docs.clawd.bot (SSL error). What now?](#i-cant-access-docsclawdbot-ssl-error-what-now)
+  - [I can't access docs.molt.bot (SSL error). What now?](#i-cant-access-docspoolbot-ssl-error-what-now)
   - [What’s the difference between stable and beta?](#whats-the-difference-between-stable-and-beta)
 - [How do I install the beta version, and what’s the difference between beta and dev?](#how-do-i-install-the-beta-version-and-whats-the-difference-between-beta-and-dev)
   - [How do I try the latest bits?](#how-do-i-try-the-latest-bits)
   - [How long does install and onboarding usually take?](#how-long-does-install-and-onboarding-usually-take)
   - [Installer stuck? How do I get more feedback?](#installer-stuck-how-do-i-get-more-feedback)
-  - [Windows install says git not found or clawdbot not recognized](#windows-install-says-git-not-found-or-clawdbot-not-recognized)
+  - [Windows install says git not found or poolbot not recognized](#windows-install-says-git-not-found-or-poolbot-not-recognized)
   - [The docs didn’t answer my question - how do I get a better answer?](#the-docs-didnt-answer-my-question-how-do-i-get-a-better-answer)
-  - [How do I install Clawdbot on Linux?](#how-do-i-install-clawdbot-on-linux)
-  - [How do I install Clawdbot on a VPS?](#how-do-i-install-clawdbot-on-a-vps)
+  - [How do I install Pool Bot on Linux?](#how-do-i-install-poolbot-on-linux)
+  - [How do I install Pool Bot on a VPS?](#how-do-i-install-poolbot-on-a-vps)
   - [Where are the cloud/VPS install guides?](#where-are-the-cloudvps-install-guides)
   - [Can I ask Clawd to update itself?](#can-i-ask-clawd-to-update-itself)
   - [What does the onboarding wizard actually do?](#what-does-the-onboarding-wizard-actually-do)
@@ -45,24 +45,24 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [How do I keep hosted model traffic in a specific region?](#how-do-i-keep-hosted-model-traffic-in-a-specific-region)
   - [Do I have to buy a Mac Mini to install this?](#do-i-have-to-buy-a-mac-mini-to-install-this)
   - [Do I need a Mac mini for iMessage support?](#do-i-need-a-mac-mini-for-imessage-support)
-  - [If I buy a Mac mini to run Clawdbot, can I connect it to my MacBook Pro?](#if-i-buy-a-mac-mini-to-run-clawdbot-can-i-connect-it-to-my-macbook-pro)
+  - [If I buy a Mac mini to run Pool Bot, can I connect it to my MacBook Pro?](#if-i-buy-a-mac-mini-to-run-poolbot-can-i-connect-it-to-my-macbook-pro)
   - [Can I use Bun?](#can-i-use-bun)
   - [Telegram: what goes in `allowFrom`?](#telegram-what-goes-in-allowfrom)
-  - [Can multiple people use one WhatsApp number with different Clawdbots?](#can-multiple-people-use-one-whatsapp-number-with-different-clawdbots)
+  - [Can multiple people use one WhatsApp number with different Pool Bots?](#can-multiple-people-use-one-whatsapp-number-with-different-poolbots)
   - [Can I run a "fast chat" agent and an "Opus for coding" agent?](#can-i-run-a-fast-chat-agent-and-an-opus-for-coding-agent)
   - [Does Homebrew work on Linux?](#does-homebrew-work-on-linux)
   - [What’s the difference between the hackable (git) install and npm install?](#whats-the-difference-between-the-hackable-git-install-and-npm-install)
   - [Can I switch between npm and git installs later?](#can-i-switch-between-npm-and-git-installs-later)
   - [Should I run the Gateway on my laptop or a VPS?](#should-i-run-the-gateway-on-my-laptop-or-a-vps)
-  - [How important is it to run Clawdbot on a dedicated machine?](#how-important-is-it-to-run-clawdbot-on-a-dedicated-machine)
+  - [How important is it to run Pool Bot on a dedicated machine?](#how-important-is-it-to-run-poolbot-on-a-dedicated-machine)
   - [What are the minimum VPS requirements and recommended OS?](#what-are-the-minimum-vps-requirements-and-recommended-os)
-  - [Can I run Clawdbot in a VM and what are the requirements](#can-i-run-clawdbot-in-a-vm-and-what-are-the-requirements)
-- [What is Clawdbot?](#what-is-clawdbot)
-  - [What is Clawdbot, in one paragraph?](#what-is-clawdbot-in-one-paragraph)
+  - [Can I run Pool Bot in a VM and what are the requirements](#can-i-run-poolbot-in-a-vm-and-what-are-the-requirements)
+- [What is Pool Bot?](#what-is-poolbot)
+  - [What is Pool Bot, in one paragraph?](#what-is-poolbot-in-one-paragraph)
   - [What’s the value proposition?](#whats-the-value-proposition)
   - [I just set it up what should I do first](#i-just-set-it-up-what-should-i-do-first)
-  - [What are the top five everyday use cases for Clawdbot](#what-are-the-top-five-everyday-use-cases-for-clawdbot)
-  - [Can Clawdbot help with lead gen outreach ads and blogs for a SaaS](#can-clawdbot-help-with-lead-gen-outreach-ads-and-blogs-for-a-saas)
+  - [What are the top five everyday use cases for Pool Bot](#what-are-the-top-five-everyday-use-cases-for-poolbot)
+  - [Can Pool Bot help with lead gen outreach ads and blogs for a SaaS](#can-poolbot-help-with-lead-gen-outreach-ads-and-blogs-for-a-saas)
   - [What are the advantages vs Claude Code for web development?](#what-are-the-advantages-vs-claude-code-for-web-development)
 - [Skills and automation](#skills-and-automation)
   - [How do I customize skills without keeping the repo dirty?](#how-do-i-customize-skills-without-keeping-the-repo-dirty)
@@ -71,7 +71,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [The bot freezes while doing heavy work. How do I offload that?](#the-bot-freezes-while-doing-heavy-work-how-do-i-offload-that)
   - [Cron or reminders do not fire. What should I check?](#cron-or-reminders-do-not-fire-what-should-i-check)
   - [How do I install skills on Linux?](#how-do-i-install-skills-on-linux)
-  - [Can Clawdbot run tasks on a schedule or continuously in the background?](#can-clawdbot-run-tasks-on-a-schedule-or-continuously-in-the-background)
+  - [Can Pool Bot run tasks on a schedule or continuously in the background?](#can-poolbot-run-tasks-on-a-schedule-or-continuously-in-the-background)
   - [Can I run Apple/macOS-only skills from Linux?](#can-i-run-applemacosonly-skills-from-linux)
   - [Do you have a Notion or HeyGen integration?](#do-you-have-a-notion-or-heygen-integration)
   - [How do I install the Chrome extension for browser takeover?](#how-do-i-install-the-chrome-extension-for-browser-takeover)
@@ -83,11 +83,11 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [Does memory persist forever? What are the limits?](#does-memory-persist-forever-what-are-the-limits)
   - [Does semantic memory search require an OpenAI API key?](#does-semantic-memory-search-require-an-openai-api-key)
 - [Where things live on disk](#where-things-live-on-disk)
-  - [Is all data used with Clawdbot saved locally?](#is-all-data-used-with-clawdbot-saved-locally)
-  - [Where does Clawdbot store its data?](#where-does-clawdbot-store-its-data)
+  - [Is all data used with Pool Bot saved locally?](#is-all-data-used-with-poolbot-saved-locally)
+  - [Where does Pool Bot store its data?](#where-does-poolbot-store-its-data)
   - [Where should AGENTS.md / SOUL.md / USER.md / MEMORY.md live?](#where-should-agentsmd-soulmd-usermd-memorymd-live)
   - [What’s the recommended backup strategy?](#whats-the-recommended-backup-strategy)
-  - [How do I completely uninstall Clawdbot?](#how-do-i-completely-uninstall-clawdbot)
+  - [How do I completely uninstall Pool Bot?](#how-do-i-completely-uninstall-poolbot)
   - [Can agents work outside the workspace?](#can-agents-work-outside-the-workspace)
   - [I’m in remote mode - where is the session store?](#im-in-remote-mode-where-is-the-session-store)
 - [Config basics](#config-basics)
@@ -98,13 +98,13 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [How do I enable web search (and web fetch)?](#how-do-i-enable-web-search-and-web-fetch)
   - [config.apply wiped my config. How do I recover and avoid this?](#configapply-wiped-my-config-how-do-i-recover-and-avoid-this)
   - [How do I run a central Gateway with specialized workers across devices?](#how-do-i-run-a-central-gateway-with-specialized-workers-across-devices)
-  - [Can the Clawdbot browser run headless?](#can-the-clawdbot-browser-run-headless)
+  - [Can the Pool Bot browser run headless?](#can-the-poolbot-browser-run-headless)
   - [How do I use Brave for browser control?](#how-do-i-use-brave-for-browser-control)
 - [Remote gateways + nodes](#remote-gateways-nodes)
   - [How do commands propagate between Telegram, the gateway, and nodes?](#how-do-commands-propagate-between-telegram-the-gateway-and-nodes)
   - [How can my agent access my computer if the Gateway is hosted remotely?](#how-can-my-agent-access-my-computer-if-the-gateway-is-hosted-remotely)
   - [Tailscale is connected but I get no replies. What now?](#tailscale-is-connected-but-i-get-no-replies-what-now)
-  - [Can two Clawdbots talk to each other (local + VPS)?](#can-two-clawdbots-talk-to-each-other-local-vps)
+  - [Can two Pool Bots talk to each other (local + VPS)?](#can-two-poolbots-talk-to-each-other-local-vps)
   - [Do I need separate VPSes for multiple agents](#do-i-need-separate-vpses-for-multiple-agents)
   - [Is there a benefit to using a node on my personal laptop instead of SSH from a VPS?](#is-there-a-benefit-to-using-a-node-on-my-personal-laptop-instead-of-ssh-from-a-vps)
   - [Do nodes run a gateway service?](#do-nodes-run-a-gateway-service)
@@ -114,21 +114,21 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [How do I connect a Mac node to a remote Gateway (Tailscale Serve)?](#how-do-i-connect-a-mac-node-to-a-remote-gateway-tailscale-serve)
   - [Should I install on a second laptop or just add a node?](#should-i-install-on-a-second-laptop-or-just-add-a-node)
 - [Env vars and .env loading](#env-vars-and-env-loading)
-  - [How does Clawdbot load environment variables?](#how-does-clawdbot-load-environment-variables)
+  - [How does Pool Bot load environment variables?](#how-does-poolbot-load-environment-variables)
   - [“I started the Gateway via the service and my env vars disappeared.” What now?](#i-started-the-gateway-via-the-service-and-my-env-vars-disappeared-what-now)
   - [I set `COPILOT_GITHUB_TOKEN`, but models status shows “Shell env: off.” Why?](#i-set-copilotgithubtoken-but-models-status-shows-shell-env-off-why)
 - [Sessions & multiple chats](#sessions-multiple-chats)
   - [How do I start a fresh conversation?](#how-do-i-start-a-fresh-conversation)
   - [Do sessions reset automatically if I never send `/new`?](#do-sessions-reset-automatically-if-i-never-send-new)
-  - [Is there a way to make a team of Clawdbots one CEO and many agents](#is-there-a-way-to-make-a-team-of-clawdbots-one-ceo-and-many-agents)
+  - [Is there a way to make a team of Pool Bots one CEO and many agents](#is-there-a-way-to-make-a-team-of-poolbots-one-ceo-and-many-agents)
   - [Why did context get truncated mid-task? How do I prevent it?](#why-did-context-get-truncated-midtask-how-do-i-prevent-it)
-  - [How do I completely reset Clawdbot but keep it installed?](#how-do-i-completely-reset-clawdbot-but-keep-it-installed)
+  - [How do I completely reset Pool Bot but keep it installed?](#how-do-i-completely-reset-poolbot-but-keep-it-installed)
   - [I’m getting “context too large” errors - how do I reset or compact?](#im-getting-context-too-large-errors-how-do-i-reset-or-compact)
   - [Why am I seeing “LLM request rejected: messages.N.content.X.tool_use.input: Field required”?](#why-am-i-seeing-llm-request-rejected-messagesncontentxtooluseinput-field-required)
   - [Why am I getting heartbeat messages every 30 minutes?](#why-am-i-getting-heartbeat-messages-every-30-minutes)
   - [Do I need to add a “bot account” to a WhatsApp group?](#do-i-need-to-add-a-bot-account-to-a-whatsapp-group)
   - [How do I get the JID of a WhatsApp group?](#how-do-i-get-the-jid-of-a-whatsapp-group)
-  - [Why doesn’t Clawdbot reply in a group?](#why-doesnt-clawdbot-reply-in-a-group)
+  - [Why doesn’t Pool Bot reply in a group?](#why-doesnt-poolbot-reply-in-a-group)
   - [Do groups/threads share context with DMs?](#do-groupsthreads-share-context-with-dms)
   - [How many workspaces and agents can I create?](#how-many-workspaces-and-agents-can-i-create)
   - [Can I run multiple bots or chats at the same time (Slack), and how should I set that up?](#can-i-run-multiple-bots-or-chats-at-the-same-time-slack-and-how-should-i-set-that-up)
@@ -158,10 +158,10 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [OAuth vs API key: what’s the difference?](#oauth-vs-api-key-whats-the-difference)
 - [Gateway: ports, “already running”, and remote mode](#gateway-ports-already-running-and-remote-mode)
   - [What port does the Gateway use?](#what-port-does-the-gateway-use)
-  - [Why does `clawdbot gateway status` say `Runtime: running` but `RPC probe: failed`?](#why-does-clawdbot-gateway-status-say-runtime-running-but-rpc-probe-failed)
-  - [Why does `clawdbot gateway status` show `Config (cli)` and `Config (service)` different?](#why-does-clawdbot-gateway-status-show-config-cli-and-config-service-different)
+  - [Why does `poolbot gateway status` say `Runtime: running` but `RPC probe: failed`?](#why-does-poolbot-gateway-status-say-runtime-running-but-rpc-probe-failed)
+  - [Why does `poolbot gateway status` show `Config (cli)` and `Config (service)` different?](#why-does-poolbot-gateway-status-show-config-cli-and-config-service-different)
   - [What does “another gateway instance is already listening” mean?](#what-does-another-gateway-instance-is-already-listening-mean)
-  - [How do I run Clawdbot in remote mode (client connects to a Gateway elsewhere)?](#how-do-i-run-clawdbot-in-remote-mode-client-connects-to-a-gateway-elsewhere)
+  - [How do I run Pool Bot in remote mode (client connects to a Gateway elsewhere)?](#how-do-i-run-poolbot-in-remote-mode-client-connects-to-a-gateway-elsewhere)
   - [The Control UI says “unauthorized” (or keeps reconnecting). What now?](#the-control-ui-says-unauthorized-or-keeps-reconnecting-what-now)
   - [I set `gateway.bind: "tailnet"` but it can’t bind / nothing listens](#i-set-gatewaybind-tailnet-but-it-cant-bind-nothing-listens)
   - [Can I run multiple Gateways on the same host?](#can-i-run-multiple-gateways-on-the-same-host)
@@ -169,18 +169,18 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 - [Logging and debugging](#logging-and-debugging)
   - [Where are logs?](#where-are-logs)
   - [How do I start/stop/restart the Gateway service?](#how-do-i-startstoprestart-the-gateway-service)
-  - [I closed my terminal on Windows - how do I restart Clawdbot?](#i-closed-my-terminal-on-windows-how-do-i-restart-clawdbot)
+  - [I closed my terminal on Windows - how do I restart Pool Bot?](#i-closed-my-terminal-on-windows-how-do-i-restart-poolbot)
   - [The Gateway is up but replies never arrive. What should I check?](#the-gateway-is-up-but-replies-never-arrive-what-should-i-check)
   - ["Disconnected from gateway: no reason" - what now?](#disconnected-from-gateway-no-reason-what-now)
   - [Telegram setMyCommands fails with network errors. What should I check?](#telegram-setmycommands-fails-with-network-errors-what-should-i-check)
   - [TUI shows no output. What should I check?](#tui-shows-no-output-what-should-i-check)
   - [How do I completely stop then start the Gateway?](#how-do-i-completely-stop-then-start-the-gateway)
-  - [ELI5: `clawdbot gateway restart` vs `clawdbot gateway`](#eli5-clawdbot-gateway-restart-vs-clawdbot-gateway)
+  - [ELI5: `poolbot gateway restart` vs `poolbot gateway`](#eli5-poolbot-gateway-restart-vs-poolbot-gateway)
   - [What’s the fastest way to get more details when something fails?](#whats-the-fastest-way-to-get-more-details-when-something-fails)
 - [Media & attachments](#media-attachments)
   - [My skill generated an image/PDF, but nothing was sent](#my-skill-generated-an-imagepdf-but-nothing-was-sent)
 - [Security and access control](#security-and-access-control)
-  - [Is it safe to expose Clawdbot to inbound DMs?](#is-it-safe-to-expose-clawdbot-to-inbound-dms)
+  - [Is it safe to expose Pool Bot to inbound DMs?](#is-it-safe-to-expose-poolbot-to-inbound-dms)
   - [Is prompt injection only a concern for public bots?](#is-prompt-injection-only-a-concern-for-public-bots)
   - [Should my bot have its own email GitHub account or phone number](#should-my-bot-have-its-own-email-github-account-or-phone-number)
   - [Can I give it autonomy over my text messages and is that safe](#can-i-give-it-autonomy-over-my-text-messages-and-is-that-safe)
@@ -197,48 +197,48 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 
 1) **Quick status (first check)**
    ```bash
-   clawdbot status
+   poolbot status
    ```
    Fast local summary: OS + update, gateway/service reachability, agents/sessions, provider config + runtime issues (when gateway is reachable).
 
 2) **Pasteable report (safe to share)**
    ```bash
-   clawdbot status --all
+   poolbot status --all
    ```
    Read-only diagnosis with log tail (tokens redacted).
 
 3) **Daemon + port state**
    ```bash
-   clawdbot gateway status
+   poolbot gateway status
    ```
    Shows supervisor runtime vs RPC reachability, the probe target URL, and which config the service likely used.
 
 4) **Deep probes**
    ```bash
-   clawdbot status --deep
+   poolbot status --deep
    ```
    Runs gateway health checks + provider probes (requires a reachable gateway). See [Health](/gateway/health).
 
 5) **Tail the latest log**
    ```bash
-   clawdbot logs --follow
+   poolbot logs --follow
    ```
    If RPC is down, fall back to:
    ```bash
-   tail -f "$(ls -t /tmp/clawdbot/clawdbot-*.log | head -1)"
+   tail -f "$(ls -t /tmp/poolbot/poolbot-*.log | head -1)"
    ```
    File logs are separate from service logs; see [Logging](/logging) and [Troubleshooting](/gateway/troubleshooting).
 
 6) **Run the doctor (repairs)**
    ```bash
-   clawdbot doctor
+   poolbot doctor
    ```
    Repairs/migrates config/state + runs health checks. See [Doctor](/gateway/doctor).
 
 7) **Gateway snapshot**
    ```bash
-   clawdbot health --json
-   clawdbot health --verbose   # shows the target URL + config path on errors
+   poolbot health --json
+   poolbot health --verbose   # shows the target URL + config path on errors
    ```
    Asks the running gateway for a full snapshot (WS-only). See [Health](/gateway/health).
 
@@ -258,10 +258,10 @@ setup (PATH, services, permissions, auth files). Give them the **full source che
 the hackable (git) install:
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git
+curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git
 ```
 
-This installs Clawdbot **from a git checkout**, so the agent can read the code + docs and
+This installs Pool Bot **from a git checkout**, so the agent can read the code + docs and
 reason about the exact version you are running. You can always switch back to stable later
 by re-running the installer without `--install-method git`.
 
@@ -269,35 +269,35 @@ Tip: ask the agent to **plan and supervise** the fix (step-by-step), then execut
 necessary commands. That keeps changes small and easier to audit.
 
 If you discover a real bug or fix, please file a GitHub issue or send a PR:
-https://github.com/clawdbot/clawdbot/issues
-https://github.com/clawdbot/clawdbot/pulls
+https://github.com/poolbot/poolbot/issues
+https://github.com/poolbot/poolbot/pulls
 
 Start with these commands (share outputs when asking for help):
 
 ```bash
-clawdbot status
-clawdbot models status
-clawdbot doctor
+poolbot status
+poolbot models status
+poolbot doctor
 ```
 
 What they do:
-- `clawdbot status`: quick snapshot of gateway/agent health + basic config.
-- `clawdbot models status`: checks provider auth + model availability.
-- `clawdbot doctor`: validates and repairs common config/state issues.
+- `poolbot status`: quick snapshot of gateway/agent health + basic config.
+- `poolbot models status`: checks provider auth + model availability.
+- `poolbot doctor`: validates and repairs common config/state issues.
 
-Other useful CLI checks: `clawdbot status --all`, `clawdbot logs --follow`,
-`clawdbot gateway status`, `clawdbot health --verbose`.
+Other useful CLI checks: `poolbot status --all`, `poolbot logs --follow`,
+`poolbot gateway status`, `poolbot health --verbose`.
 
 Quick debug loop: [First 60 seconds if something's broken](#first-60-seconds-if-somethings-broken).
 Install docs: [Install](/install), [Installer flags](/install/installer), [Updating](/install/updating).
 
-### Whats the recommended way to install and set up Clawdbot
+### Whats the recommended way to install and set up Pool Bot
 
 The repo recommends running from source and using the onboarding wizard:
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash
-clawdbot onboard --install-daemon
+curl -fsSL https://molt.bot/install.sh | bash
+poolbot onboard --install-daemon
 ```
 
 The wizard can also build UI assets automatically. After onboarding, you typically run the Gateway on port **18789**.
@@ -305,15 +305,15 @@ The wizard can also build UI assets automatically. After onboarding, you typical
 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 build
 pnpm ui:build # auto-installs UI deps on first run
-clawdbot onboard
+poolbot onboard
 ```
 
-If you don’t have a global install yet, run it via `pnpm clawdbot onboard`.
+If you don’t have a global install yet, run it via `pnpm poolbot onboard`.
 
 ### How do I open the dashboard after onboarding
 
@@ -323,13 +323,13 @@ The wizard now opens your browser with a tokenized dashboard URL right after onb
 
 **Localhost (same machine):**
 - Open `http://127.0.0.1:18789/`.
-- If it asks for auth, run `clawdbot dashboard` and use the tokenized link (`?token=...`).
+- If it asks for auth, run `poolbot dashboard` and use the tokenized link (`?token=...`).
 - The token is the same value as `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`) and is stored by the UI after first load.
 
 **Not on localhost:**
-- **Tailscale Serve** (recommended): keep bind loopback, run `clawdbot gateway --tailscale serve`, open `https://<magicdns>/`. If `gateway.auth.allowTailscale` is `true`, identity headers satisfy auth (no token).
-- **Tailnet bind**: run `clawdbot gateway --bind tailnet --token "<token>"`, open `http://<tailscale-ip>:18789/`, paste token in dashboard settings.
-- **SSH tunnel**: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/?token=...` from `clawdbot dashboard`.
+- **Tailscale Serve** (recommended): keep bind loopback, run `poolbot gateway --tailscale serve`, open `https://<magicdns>/`. If `gateway.auth.allowTailscale` is `true`, identity headers satisfy auth (no token).
+- **Tailnet bind**: run `poolbot gateway --bind tailnet --token "<token>"`, open `http://<tailscale-ip>:18789/`, paste token in dashboard settings.
+- **SSH tunnel**: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/?token=...` from `poolbot dashboard`.
 
 See [Dashboard](/web/dashboard) and [Web surfaces](/web) for bind modes and auth details.
 
@@ -367,17 +367,17 @@ and tokens stay at 0, the agent never ran.
 
 1) Restart the Gateway:
 ```bash
-clawdbot gateway restart
+poolbot gateway restart
 ```
 2) Check status + auth:
 ```bash
-clawdbot status
-clawdbot models status
-clawdbot logs --follow
+poolbot status
+poolbot models status
+poolbot logs --follow
 ```
 3) If it still hangs, run:
 ```bash
-clawdbot doctor
+poolbot doctor
 ```
 
 If the Gateway is remote, ensure the tunnel/Tailscale connection is up and that the UI
@@ -389,40 +389,40 @@ Yes. Copy the **state directory** and **workspace**, then run Doctor once. This
 keeps your bot “exactly the same” (memory, session history, auth, and channel
 state) as long as you copy **both** locations:
 
-1) Install Clawdbot on the new machine.
-2) Copy `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`) from the old machine.
+1) Install Pool Bot on the new machine.
+2) Copy `$CLAWDBOT_STATE_DIR` (default: `~/.poolbot`) from the old machine.
 3) Copy your workspace (default: `~/clawd`).
-4) Run `clawdbot doctor` and restart the Gateway service.
+4) Run `poolbot doctor` and restart the Gateway service.
 
 That preserves config, auth profiles, WhatsApp creds, sessions, and memory. If you’re in
 remote mode, remember the gateway host owns the session store and workspace.
 
 **Important:** if you only commit/push your workspace to GitHub, you’re backing
 up **memory + bootstrap files**, but **not** session history or auth. Those live
-under `~/.clawdbot/` (for example `~/.clawdbot/agents/<agentId>/sessions/`).
+under `~/.poolbot/` (for example `~/.poolbot/agents/<agentId>/sessions/`).
 
-Related: [Where things live on disk](/help/faq#where-does-clawdbot-store-its-data),
+Related: [Migrating](/install/migrating), [Where things live on disk](/help/faq#where-does-poolbot-store-its-data),
 [Agent workspace](/concepts/agent-workspace), [Doctor](/gateway/doctor),
 [Remote mode](/gateway/remote).
 
 ### Where do I see whats new in the latest version
 
 Check the GitHub changelog:  
-https://github.com/clawdbot/clawdbot/blob/main/CHANGELOG.md
+https://github.com/poolbot/poolbot/blob/main/CHANGELOG.md
 
 Newest entries are at the top. If the top section is marked **Unreleased**, the next dated
 section is the latest shipped version. Entries are grouped by **Highlights**, **Changes**, and
 **Fixes** (plus docs/other sections when needed).
 
-### I cant access docsclawdbot SSL error What now
+### I cant access docspoolbot SSL error What now
 
-Some Comcast/Xfinity connections incorrectly block `docs.clawd.bot` via Xfinity
-Advanced Security. Disable it or allowlist `docs.clawd.bot`, then retry. More
-detail: [Troubleshooting](/help/troubleshooting#docsclawdbot-shows-an-ssl-error-comcastxfinity).
+Some Comcast/Xfinity connections incorrectly block `docs.molt.bot` via Xfinity
+Advanced Security. Disable it or allowlist `docs.molt.bot`, then retry. More
+detail: [Troubleshooting](/help/troubleshooting#docspoolbot-shows-an-ssl-error-comcastxfinity).
 Please help us unblock it by reporting here: https://spa.xfinity.com/check_url_status.
 
 If you still can't reach the site, the docs are mirrored on GitHub:
-https://github.com/clawdbot/clawdbot/tree/main/docs
+https://github.com/poolbot/poolbot/tree/main/docs
 
 ### Whats the difference between stable and beta
 
@@ -435,7 +435,7 @@ that same version to `latest`**. That’s why beta and stable can point at the
 **same version**.
 
 See what changed:  
-https://github.com/clawdbot/clawdbot/blob/main/CHANGELOG.md
+https://github.com/poolbot/poolbot/blob/main/CHANGELOG.md
 
 ### How do I install the beta version and whats the difference between beta and dev
 
@@ -445,15 +445,15 @@ https://github.com/clawdbot/clawdbot/blob/main/CHANGELOG.md
 One‑liners (macOS/Linux):
 
 ```bash
-curl -fsSL --proto '=https' --tlsv1.2 https://clawd.bot/install.sh | bash -s -- --beta
+curl -fsSL --proto '=https' --tlsv1.2 https://molt.bot/install.sh | bash -s -- --beta
 ```
 
 ```bash
-curl -fsSL --proto '=https' --tlsv1.2 https://clawd.bot/install.sh | bash -s -- --install-method git
+curl -fsSL --proto '=https' --tlsv1.2 https://molt.bot/install.sh | bash -s -- --install-method git
 ```
 
 Windows installer (PowerShell):
-https://clawd.bot/install.ps1
+https://molt.bot/install.ps1
 
 More detail: [Development channels](/install/development-channels) and [Installer flags](/install/installer).
 
@@ -472,20 +472,20 @@ Two options:
 
 1) **Dev channel (git checkout):**
 ```bash
-clawdbot update --channel dev
+poolbot update --channel dev
 ```
 This switches to the `main` branch and updates from source.
 
 2) **Hackable install (from the installer site):**
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git
+curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git
 ```
 That gives you a local repo you can edit, then update via git.
 
 If you prefer a clean clone manually, use:
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/poolbot/poolbot.git
+cd poolbot
 pnpm install
 pnpm build
 ```
@@ -498,24 +498,24 @@ Docs: [Update](/cli/update), [Development channels](/install/development-channel
 Re-run the installer with **verbose output**:
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --verbose
+curl -fsSL https://molt.bot/install.sh | bash -s -- --verbose
 ```
 
 Beta install with verbose:
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --beta --verbose
+curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose
 ```
 
 For a hackable (git) install:
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git --verbose
+curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git --verbose
 ```
 
 More options: [Installer flags](/install/installer).
 
-### Windows install says git not found or clawdbot not recognized
+### Windows install says git not found or poolbot not recognized
 
 Two common Windows issues:
 
@@ -523,7 +523,7 @@ Two common Windows issues:
 - Install **Git for Windows** and make sure `git` is on your PATH.
 - Close and reopen PowerShell, then re-run the installer.
 
-**2) clawdbot is not recognized after install**
+**2) poolbot is not recognized after install**
 - Your npm global bin folder is not on PATH.
 - Check the path:
   ```powershell
@@ -541,12 +541,12 @@ Use the **hackable (git) install** so you have the full source and docs locally,
 your bot (or Claude/Codex) *from that folder* so it can read the repo and answer precisely.
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git
+curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git
 ```
 
 More detail: [Install](/install) and [Installer flags](/install/installer).
 
-### How do I install Clawdbot on Linux
+### How do I install Pool Bot on Linux
 
 Short answer: follow the Linux guide, then run the onboarding wizard.
 
@@ -554,7 +554,7 @@ Short answer: follow the Linux guide, then run the onboarding wizard.
 - Full walkthrough: [Getting Started](/start/getting-started).
 - Installer + updates: [Install & updates](/install/updating).
 
-### How do I install Clawdbot on a VPS
+### How do I install Pool Bot on a VPS
 
 Any Linux VPS works. Install on the server, then use SSH/Tailscale to reach the Gateway.
 
@@ -566,7 +566,6 @@ Remote access: [Gateway remote](/gateway/remote).
 We keep a **hosting hub** with the common providers. Pick one and follow the guide:
 
 - [VPS hosting](/vps) (all providers in one place)
-- [Railway](/railway) (one‑click, browser‑based setup)
 - [Fly.io](/platforms/fly)
 - [Hetzner](/platforms/hetzner)
 - [exe.dev](/platforms/exe-dev)
@@ -591,25 +590,25 @@ can prompt for confirmation. Safer: run updates from a shell as the operator.
 Use the CLI:
 
 ```bash
-clawdbot update
-clawdbot update status
-clawdbot update --channel stable|beta|dev
-clawdbot update --tag <dist-tag|version>
-clawdbot update --no-restart
+poolbot update
+poolbot update status
+poolbot update --channel stable|beta|dev
+poolbot update --tag <dist-tag|version>
+poolbot update --no-restart
 ```
 
 If you must automate from an agent:
 
 ```bash
-clawdbot update --yes --no-restart
-clawdbot gateway restart
+poolbot update --yes --no-restart
+poolbot gateway restart
 ```
 
 Docs: [Update](/cli/update), [Updating](/install/updating).
 
 ### What does the onboarding wizard actually do
 
-`clawdbot onboard` is the recommended setup path. In **local mode** it walks you through:
+`poolbot onboard` is the recommended setup path. In **local mode** it walks you through:
 
 - **Model/auth setup** (Anthropic **setup-token** recommended for Claude subscriptions, OpenAI Codex OAuth supported, API keys optional, LM Studio local models supported)
 - **Workspace** location + bootstrap files
@@ -622,7 +621,7 @@ It also warns if your configured model is unknown or missing auth.
 
 ### Do I need a Claude or OpenAI subscription to run this
 
-No. You can run Clawdbot with **API keys** (Anthropic/OpenAI/others) or with
+No. You can run Pool Bot with **API keys** (Anthropic/OpenAI/others) or with
 **local‑only models** so your data stays on your device. Subscriptions (Claude
 Pro/Max or OpenAI Codex) are optional ways to authenticate those providers.
 
@@ -631,7 +630,7 @@ Docs: [Anthropic](/providers/anthropic), [OpenAI](/providers/openai),
 
 ### Can I use Claude Max subscription without an API key
 
-Yes. You can authenticate with **Claude Code CLI OAuth** or a **setup-token**
+Yes. You can authenticate with a **setup-token**
 instead of an API key. This is the subscription path.
 
 Claude Pro/Max subscriptions **do not include an API key**, so this is the
@@ -641,11 +640,7 @@ If you want the most explicit, supported path, use an Anthropic API key.
 
 ### How does Anthropic setuptoken auth work
 
-`claude setup-token` generates a **token string** via the Claude Code CLI (it is not available in the web console). You can run it on **any machine**. If Claude Code CLI credentials are present on the gateway host, Clawdbot can reuse them; otherwise choose **Anthropic token (paste setup-token)** and paste the string. The token is stored as an auth profile for the **anthropic** provider and used like an API key or OAuth profile. More detail: [OAuth](/concepts/oauth).
-
-Clawdbot keeps `auth.profiles["anthropic:claude-cli"].mode` set to `"oauth"` so
-the profile accepts both OAuth and setup-token credentials; older `"token"` mode
-entries auto-migrate.
+`claude setup-token` generates a **token string** via the Claude Code CLI (it is not available in the web console). You can run it on **any machine**. Choose **Anthropic token (paste setup-token)** in the wizard or paste it with `poolbot models auth paste-token --provider anthropic`. The token is stored as an auth profile for the **anthropic** provider and used like an API key (no auto-refresh). More detail: [OAuth](/concepts/oauth).
 
 ### Where do I find an Anthropic setuptoken
 
@@ -655,11 +650,11 @@ It is **not** in the Anthropic Console. The setup-token is generated by the **Cl
 claude setup-token
 ```
 
-Copy the token it prints, then choose **Anthropic token (paste setup-token)** in the wizard. If you want to run it on the gateway host, use `clawdbot models auth setup-token --provider anthropic`. If you ran `claude setup-token` elsewhere, paste it on the gateway host with `clawdbot models auth paste-token --provider anthropic`. See [Anthropic](/providers/anthropic).
+Copy the token it prints, then choose **Anthropic token (paste setup-token)** in the wizard. If you want to run it on the gateway host, use `poolbot models auth setup-token --provider anthropic`. If you ran `claude setup-token` elsewhere, paste it on the gateway host with `poolbot models auth paste-token --provider anthropic`. See [Anthropic](/providers/anthropic).
 
-### Do you support Claude subscription auth Claude Code OAuth
+### Do you support Claude subscription auth (Claude Pro/Max)
 
-Yes. Clawdbot can **reuse Claude Code CLI credentials** (OAuth) and also supports **setup-token**. If you have a Claude subscription, we recommend **setup-token** for long‑running setups (requires Claude Pro/Max + the `claude` CLI). You can generate it anywhere and paste it on the gateway host. OAuth reuse is supported, but avoid logging in separately via Clawdbot and Claude Code to prevent token conflicts. See [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth).
+Yes — via **setup-token**. Pool Bot no longer reuses Claude Code CLI OAuth tokens; use a setup-token or an Anthropic API key. Generate the token anywhere and paste it on the gateway host. See [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth).
 
 Note: Claude subscription access is governed by Anthropic’s terms. For production or multi‑user workloads, API keys are usually the safer choice.
 
@@ -670,7 +665,7 @@ use a **Claude subscription** (setup‑token or Claude Code OAuth), wait for the
 reset or upgrade your plan. If you use an **Anthropic API key**, check the Anthropic Console
 for usage/billing and raise limits as needed.
 
-Tip: set a **fallback model** so Clawdbot can keep replying while a provider is rate‑limited.
+Tip: set a **fallback model** so Pool Bot can keep replying while a provider is rate‑limited.
 See [Models](/cli/models) and [OAuth](/concepts/oauth).
 
 ### Is AWS Bedrock supported
@@ -679,29 +674,28 @@ Yes - via pi‑ai’s **Amazon Bedrock (Converse)** provider with **manual confi
 
 ### How does Codex auth work
 
-Clawdbot supports **OpenAI Code (Codex)** via OAuth or by reusing your Codex CLI login (`~/.codex/auth.json`). The wizard can import the CLI login or run the OAuth flow and will set the default model to `openai-codex/gpt-5.2` when appropriate. See [Model providers](/concepts/model-providers) and [Wizard](/start/wizard).
+Pool Bot supports **OpenAI Code (Codex)** via OAuth (ChatGPT sign-in). The wizard can run the OAuth flow and will set the default model to `openai-codex/gpt-5.2` when appropriate. See [Model providers](/concepts/model-providers) and [Wizard](/start/wizard).
 
 ### Do you support OpenAI subscription auth Codex OAuth
 
-Yes. Clawdbot fully supports **OpenAI Code (Codex) subscription OAuth** and can also reuse an
-existing Codex CLI login (`~/.codex/auth.json`) on the gateway host. The onboarding wizard
-can import the CLI login or run the OAuth flow for you.
+Yes. Pool Bot fully supports **OpenAI Code (Codex) subscription OAuth**. The onboarding wizard
+can run the OAuth flow for you.
 
 See [OAuth](/concepts/oauth), [Model providers](/concepts/model-providers), and [Wizard](/start/wizard).
 
 ### How do I set up Gemini CLI OAuth
 
-Gemini CLI uses a **plugin auth flow**, not a client id or secret in `clawdbot.json`.
+Gemini CLI uses a **plugin auth flow**, not a client id or secret in `poolbot.json`.
 
 Steps:
-1) Enable the plugin: `clawdbot plugins enable google-gemini-cli-auth`
-2) Login: `clawdbot models auth login --provider google-gemini-cli --set-default`
+1) Enable the plugin: `poolbot plugins enable google-gemini-cli-auth`
+2) Login: `poolbot models auth login --provider google-gemini-cli --set-default`
 
 This stores OAuth tokens in auth profiles on the gateway host. Details: [Model providers](/concepts/model-providers).
 
 ### Is a local model OK for casual chats
 
-Usually no. Clawdbot needs large context + strong safety; small cards truncate and leak. If you must, run the **largest** MiniMax M2.1 build you can locally (LM Studio) and see [/gateway/local-models](/gateway/local-models). Smaller/quantized models increase prompt-injection risk - see [Security](/gateway/security).
+Usually no. Pool Bot needs large context + strong safety; small cards truncate and leak. If you must, run the **largest** MiniMax M2.1 build you can locally (LM Studio) and see [/gateway/local-models](/gateway/local-models). Smaller/quantized models increase prompt-injection risk - see [Security](/gateway/security).
 
 ### How do I keep hosted model traffic in a specific region
 
@@ -709,7 +703,7 @@ Pick region-pinned endpoints. OpenRouter exposes US-hosted options for MiniMax,
 
 ### Do I have to buy a Mac Mini to install this
 
-No. Clawdbot runs on macOS or Linux (Windows via WSL2). A Mac mini is optional - some people
+No. Pool Bot runs on macOS or Linux (Windows via WSL2). A Mac mini is optional - some people
 buy one as an always‑on host, but a small VPS, home server, or Raspberry Pi‑class box works too.
 
 You only need a Mac **for macOS‑only tools**. For iMessage, you can keep the Gateway on Linux
@@ -721,7 +715,7 @@ Docs: [iMessage](/channels/imessage), [Nodes](/nodes), [Mac remote mode](/platfo
 ### Do I need a Mac mini for iMessage support
 
 You need **some macOS device** signed into Messages. It does **not** have to be a Mac mini -
-any Mac works. Clawdbot’s iMessage integrations run on macOS (BlueBubbles or `imsg`), while
+any Mac works. Pool Bot’s iMessage integrations run on macOS (BlueBubbles or `imsg`), while
 the Gateway can run elsewhere.
 
 Common setups:
@@ -732,7 +726,7 @@ Common setups:
 Docs: [iMessage](/channels/imessage), [BlueBubbles](/channels/bluebubbles),
 [Mac remote mode](/platforms/mac/remote).
 
-### If I buy a Mac mini to run Clawdbot can I connect it to my MacBook Pro
+### If I buy a Mac mini to run Pool Bot can I connect it to my MacBook Pro
 
 Yes. The **Mac mini can run the Gateway**, and your MacBook Pro can connect as a
 **node** (companion device). Nodes don’t run the Gateway - they provide extra
@@ -741,7 +735,7 @@ capabilities like screen/camera/canvas and `system.run` on that device.
 Common pattern:
 - Gateway on the Mac mini (always‑on).
 - MacBook Pro runs the macOS app or a node host and pairs to the Gateway.
-- Use `clawdbot nodes status` / `clawdbot nodes list` to see it.
+- Use `poolbot nodes status` / `poolbot nodes list` to see it.
 
 Docs: [Nodes](/nodes), [Nodes CLI](/cli/nodes).
 
@@ -758,7 +752,7 @@ without WhatsApp/Telegram.
 `channels.telegram.allowFrom` is **the human sender’s Telegram user ID** (numeric, recommended) or `@username`. It is not the bot username.
 
 Safer (no third-party bot):
-- DM your bot, then run `clawdbot logs --follow` and read `from.id`.
+- DM your bot, then run `poolbot logs --follow` and read `from.id`.
 
 Official Bot API:
 - DM your bot, then call `https://api.telegram.org/bot<bot_token>/getUpdates` and read `message.from.id`.
@@ -768,7 +762,7 @@ Third-party (less private):
 
 See [/channels/telegram](/channels/telegram#access-control-dms--groups).
 
-### Can multiple people use one WhatsApp number with different Clawdbots
+### Can multiple people use one WhatsApp number with different Pool Bots
 
 Yes, via **multi‑agent routing**. Bind each sender’s WhatsApp **DM** (peer `kind: "dm"`, sender E.164 like `+15551234567`) to a different `agentId`, so each person gets their own workspace and session store. Replies still come from the **same WhatsApp account**, and DM access control (`channels.whatsapp.dmPolicy` / `channels.whatsapp.allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent) and [WhatsApp](/channels/whatsapp).
 
@@ -787,7 +781,7 @@ eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
 brew install <formula>
 ```
 
-If you run Clawdbot via systemd, ensure the service PATH includes `/home/linuxbrew/.linuxbrew/bin` (or your brew prefix) so `brew`-installed tools resolve in non‑login shells.
+If you run Pool Bot via systemd, ensure the service PATH includes `/home/linuxbrew/.linuxbrew/bin` (or your brew prefix) so `brew`-installed tools resolve in non‑login shells.
 Recent builds also prepend common user bin dirs on Linux systemd services (for example `~/.local/bin`, `~/.npm-global/bin`, `~/.local/share/pnpm`, `~/.bun/bin`) and honor `PNPM_HOME`, `NPM_CONFIG_PREFIX`, `BUN_INSTALL`, `VOLTA_HOME`, `ASDF_DATA_DIR`, `NVM_DIR`, and `FNM_DIR` when set.
 
 ### Whats the difference between the hackable git install and npm install
@@ -802,26 +796,26 @@ Docs: [Getting started](/start/getting-started), [Updating](/install/updating).
 ### Can I switch between npm and git installs later
 
 Yes. Install the other flavor, then run Doctor so the gateway service points at the new entrypoint.
-This **does not delete your data** - it only changes the Clawdbot code install. Your state
-(`~/.clawdbot`) and workspace (`~/clawd`) stay untouched.
+This **does not delete your data** - it only changes the Pool Bot code install. Your state
+(`~/.poolbot`) and workspace (`~/clawd`) stay untouched.
 
 From npm → git:
 
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/poolbot/poolbot.git
+cd poolbot
 pnpm install
 pnpm build
-clawdbot doctor
-clawdbot gateway restart
+poolbot doctor
+poolbot gateway restart
 ```
 
 From git → npm:
 
 ```bash
-npm install -g clawdbot@latest
-clawdbot doctor
-clawdbot gateway restart
+npm install -g poolbot@latest
+poolbot doctor
+poolbot gateway restart
 ```
 
 Doctor detects a gateway service entrypoint mismatch and offers to rewrite the service config to match the current install (use `--repair` in automation).
@@ -841,11 +835,11 @@ lowest friction and you’re okay with sleep/restarts, run it locally.
 - **Pros:** always‑on, stable network, no laptop sleep issues, easier to keep running.
 - **Cons:** often run headless (use screenshots), remote file access only, you must SSH for updates.
 
-**Clawdbot-specific note:** WhatsApp/Telegram/Slack/Mattermost (plugin)/Discord all work fine from a VPS. The only real trade-off is **headless browser** vs a visible window. See [Browser](/tools/browser).
+**Pool Bot-specific note:** WhatsApp/Telegram/Slack/Mattermost (plugin)/Discord all work fine from a VPS. The only real trade-off is **headless browser** vs a visible window. See [Browser](/tools/browser).
 
 **Recommended default:** VPS if you had gateway disconnects before. Local is great when you’re actively using the Mac and want local file access or UI automation with a visible browser.
 
-### How important is it to run Clawdbot on a dedicated machine
+### How important is it to run Pool Bot on a dedicated machine
 
 Not required, but **recommended for reliability and isolation**.
 
@@ -857,7 +851,7 @@ For security guidance, read [Security](/gateway/security).
 
 ### What are the minimum VPS requirements and recommended OS
 
-Clawdbot is lightweight. For a basic Gateway + one chat channel:
+Pool Bot is lightweight. For a basic Gateway + one chat channel:
 
 - **Absolute minimum:** 1 vCPU, 1GB RAM, ~500MB disk.
 - **Recommended:** 1-2 vCPU, 2GB RAM or more for headroom (logs, media, multiple channels). Node tools and browser automation can be resource hungry.
@@ -866,7 +860,7 @@ OS: use **Ubuntu LTS** (or any modern Debian/Ubuntu). The Linux install path is
 
 Docs: [Linux](/platforms/linux), [VPS hosting](/vps).
 
-### Can I run Clawdbot in a VM and what are the requirements
+### Can I run Pool Bot in a VM and what are the requirements
 
 Yes. Treat a VM the same as a VPS: it needs to be always on, reachable, and have enough
 RAM for the Gateway and any channels you enable.
@@ -880,15 +874,15 @@ If you are on Windows, **WSL2 is the easiest VM style setup** and has the best t
 compatibility. See [Windows](/platforms/windows), [VPS hosting](/vps).
 If you are running macOS in a VM, see [macOS VM](/platforms/macos-vm).
 
-## What is Clawdbot?
+## What is Pool Bot?
 
-### What is Clawdbot in one paragraph
+### What is Pool Bot in one paragraph
 
-Clawdbot is a personal AI assistant you run on your own devices. It replies on the messaging surfaces you already use (WhatsApp, Telegram, Slack, Mattermost (plugin), Discord, Google Chat, Signal, iMessage, WebChat) and can also do voice + a live Canvas on supported platforms. The **Gateway** is the always-on control plane; the assistant is the product.
+Pool Bot is a personal AI assistant you run on your own devices. It replies on the messaging surfaces you already use (WhatsApp, Telegram, Slack, Mattermost (plugin), Discord, Google Chat, Signal, iMessage, WebChat) and can also do voice + a live Canvas on supported platforms. The **Gateway** is the always-on control plane; the assistant is the product.
 
 ### Whats the value proposition
 
-Clawdbot is not “just a Claude wrapper.” It’s a **local-first control plane** that lets you run a
+Pool Bot is not “just a Claude wrapper.” It’s a **local-first control plane** that lets you run a
 capable assistant on **your own hardware**, reachable from the chat apps you already use, with
 stateful sessions, memory, and tools - without handing control of your workflows to a hosted
 SaaS.
@@ -919,7 +913,7 @@ Good first projects:
 It can handle large tasks, but it works best when you split them into phases and
 use sub agents for parallel work.
 
-### What are the top five everyday use cases for Clawdbot
+### What are the top five everyday use cases for Pool Bot
 
 Everyday wins usually look like:
 - **Personal briefings:** summaries of inbox, calendar, and news you care about.
@@ -928,21 +922,21 @@ Everyday wins usually look like:
 - **Browser automation:** filling forms, collecting data, and repeating web tasks.
 - **Cross device coordination:** send a task from your phone, let the Gateway run it on a server, and get the result back in chat.
 
-### Can Clawdbot help with lead gen outreach ads and blogs for a SaaS
+### Can Pool Bot help with lead gen outreach ads and blogs for a SaaS
 
 Yes for **research, qualification, and drafting**. It can scan sites, build shortlists,
 summarize prospects, and write outreach or ad copy drafts.
 
 For **outreach or ad runs**, keep a human in the loop. Avoid spam, follow local laws and
 platform policies, and review anything before it is sent. The safest pattern is to let
-Clawdbot draft and you approve.
+Pool Bot draft and you approve.
 
 Docs: [Security](/gateway/security).
 
 ### What are the advantages vs Claude Code for web development
 
-Clawdbot is a **personal assistant** and coordination layer, not an IDE replacement. Use
-Claude Code or Codex for the fastest direct coding loop inside a repo. Use Clawdbot when you
+Pool Bot is a **personal assistant** and coordination layer, not an IDE replacement. Use
+Claude Code or Codex for the fastest direct coding loop inside a repo. Use Pool Bot when you
 want durable memory, cross-device access, and tool orchestration.
 
 Advantages:
@@ -952,17 +946,17 @@ Advantages:
 - **Always-on Gateway** (run on a VPS, interact from anywhere)
 - **Nodes** for local browser/screen/camera/exec
 
-Showcase: https://clawd.bot/showcase
+Showcase: https://molt.bot/showcase
 
 ## Skills and automation
 
 ### How do I customize skills without keeping the repo dirty
 
-Use managed overrides instead of editing the repo copy. Put your changes in `~/.clawdbot/skills/<name>/SKILL.md` (or add a folder via `skills.load.extraDirs` in `~/.clawdbot/clawdbot.json`). Precedence is `<workspace>/skills` > `~/.clawdbot/skills` > bundled, so managed overrides win without touching git. Only upstream-worthy edits should live in the repo and go out as PRs.
+Use managed overrides instead of editing the repo copy. Put your changes in `~/.poolbot/skills/<name>/SKILL.md` (or add a folder via `skills.load.extraDirs` in `~/.poolbot/poolbot.json`). Precedence is `<workspace>/skills` > `~/.poolbot/skills` > bundled, so managed overrides win without touching git. Only upstream-worthy edits should live in the repo and go out as PRs.
 
 ### Can I load skills from a custom folder
 
-Yes. Add extra directories via `skills.load.extraDirs` in `~/.clawdbot/clawdbot.json` (lowest precedence). Default precedence remains: `<workspace>/skills` → `~/.clawdbot/skills` → bundled → `skills.load.extraDirs`. `clawdhub` installs into `./skills` by default, which Clawdbot treats as `<workspace>/skills`.
+Yes. Add extra directories via `skills.load.extraDirs` in `~/.poolbot/poolbot.json` (lowest precedence). Default precedence remains: `<workspace>/skills` → `~/.poolbot/skills` → bundled → `skills.load.extraDirs`. `clawdhub` installs into `./skills` by default, which Pool Bot treats as `<workspace>/skills`.
 
 ### How can I use different models for different tasks
 
@@ -998,8 +992,8 @@ Checklist:
 
 Debug:
 ```bash
-clawdbot cron run <jobId> --force
-clawdbot cron runs --id <jobId> --limit 50
+poolbot cron run <jobId> --force
+poolbot cron runs --id <jobId> --limit 50
 ```
 
 Docs: [Cron jobs](/automation/cron-jobs), [Cron vs Heartbeat](/automation/cron-vs-heartbeat).
@@ -1019,7 +1013,7 @@ npm i -g clawdhub
 pnpm add -g clawdhub
 ```
 
-### Can Clawdbot run tasks on a schedule or continuously in the background
+### Can Pool Bot run tasks on a schedule or continuously in the background
 
 Yes. Use the Gateway scheduler:
 
@@ -1032,15 +1026,15 @@ Docs: [Cron jobs](/automation/cron-jobs), [Cron vs Heartbeat](/automation/cron-v
 
 **Can I run Apple macOS only skills from Linux**
 
-Not directly. macOS skills are gated by `metadata.clawdbot.os` plus required binaries, and skills only appear in the system prompt when they are eligible on the **Gateway host**. On Linux, `darwin`-only skills (like `imsg`, `apple-notes`, `apple-reminders`) will not load unless you override the gating.
+Not directly. macOS skills are gated by `metadata.poolbot.os` plus required binaries, and skills only appear in the system prompt when they are eligible on the **Gateway host**. On Linux, `darwin`-only skills (like `imsg`, `apple-notes`, `apple-reminders`) will not load unless you override the gating.
 
 You have three supported patterns:
 
 **Option A - run the Gateway on a Mac (simplest).**  
-Run the Gateway where the macOS binaries exist, then connect from Linux in [remote mode](#how-do-i-run-clawdbot-in-remote-mode-client-connects-to-a-gateway-elsewhere) or over Tailscale. The skills load normally because the Gateway host is macOS.
+Run the Gateway where the macOS binaries exist, then connect from Linux in [remote mode](#how-do-i-run-poolbot-in-remote-mode-client-connects-to-a-gateway-elsewhere) or over Tailscale. The skills load normally because the Gateway host is macOS.
 
 **Option B - use a macOS node (no SSH).**  
-Run the Gateway on Linux, pair a macOS node (menubar app), and set **Node Run Commands** to "Always Ask" or "Always Allow" on the Mac. Clawdbot can treat macOS-only skills as eligible when the required binaries exist on the node. The agent runs those skills via the `nodes` tool. If you choose "Always Ask", approving "Always Allow" in the prompt adds that command to the allowlist.
+Run the Gateway on Linux, pair a macOS node (menubar app), and set **Node Run Commands** to "Always Ask" or "Always Allow" on the Mac. Pool Bot can treat macOS-only skills as eligible when the required binaries exist on the node. The agent runs those skills via the `nodes` tool. If you choose "Always Ask", approving "Always Allow" in the prompt adds that command to the allowlist.
 
 **Option C - proxy macOS binaries over SSH (advanced).**  
 Keep the Gateway on Linux, but make the required CLI binaries resolve to SSH wrappers that run on a Mac. Then override the skill to allow Linux so it stays eligible.
@@ -1052,17 +1046,17 @@ Keep the Gateway on Linux, but make the required CLI binaries resolve to SSH wra
    exec ssh -T user@mac-host /opt/homebrew/bin/imsg "$@"
    ```
 2) Put the wrapper on `PATH` on the Linux host (for example `~/bin/imsg`).
-3) Override the skill metadata (workspace or `~/.clawdbot/skills`) to allow Linux:
+3) Override the skill metadata (workspace or `~/.poolbot/skills`) to allow Linux:
    ```markdown
    ---
    name: imsg
    description: iMessage/SMS CLI for listing chats, history, watch, and sending.
-   metadata: {"clawdbot":{"os":["darwin","linux"],"requires":{"bins":["imsg"]}}}
+   metadata: {"poolbot":{"os":["darwin","linux"],"requires":{"bins":["imsg"]}}}
    ---
    ```
 4) Start a new session so the skills snapshot refreshes.
 
-For iMessage specifically, you can also point `channels.imessage.cliPath` at an SSH wrapper (Clawdbot only needs stdio). See [iMessage](/channels/imessage).
+For iMessage specifically, you can also point `channels.imessage.cliPath` at an SSH wrapper (Pool Bot only needs stdio). See [iMessage](/channels/imessage).
 
 ### Do you have a Notion or HeyGen integration
 
@@ -1086,22 +1080,23 @@ clawdhub install <skill-slug>
 clawdhub update --all
 ```
 
-ClawdHub installs into `./skills` under your current directory (or falls back to your configured Clawdbot workspace); Clawdbot treats that as `<workspace>/skills` on the next session. For shared skills across agents, place them in `~/.clawdbot/skills/<name>/SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [ClawdHub](/tools/clawdhub).
+ClawdHub installs into `./skills` under your current directory (or falls back to your configured Pool Bot workspace); Pool Bot treats that as `<workspace>/skills` on the next session. For shared skills across agents, place them in `~/.poolbot/skills/<name>/SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [ClawdHub](/tools/clawdhub).
 
 ### How do I install the Chrome extension for browser takeover
 
 Use the built-in installer, then load the unpacked extension in Chrome:
 
 ```bash
-clawdbot browser extension install
-clawdbot browser extension path
+poolbot browser extension install
+poolbot browser extension path
 ```
 
 Then Chrome → `chrome://extensions` → enable “Developer mode” → “Load unpacked” → pick that folder.
 
-Full guide (including remote Gateway via Tailscale + security notes): [Chrome extension](/tools/chrome-extension)
+Full guide (including remote Gateway + security notes): [Chrome extension](/tools/chrome-extension)
 
-If the Gateway runs on the same machine as Chrome (default setup), you usually **do not** need `clawdbot browser serve`.
+If the Gateway runs on the same machine as Chrome (default setup), you usually **do not** need anything extra.
+If the Gateway runs elsewhere, run a node host on the browser machine so the Gateway can proxy browser actions.
 You still need to click the extension button on the tab you want to control (it doesn’t auto-attach).
 
 ## Sandboxing and memory
@@ -1126,11 +1121,11 @@ Set `agents.defaults.sandbox.docker.binds` to `["host:path:mode"]` (e.g., `"/hom
 
 ### How does memory work
 
-Clawdbot memory is just Markdown files in the agent workspace:
+Pool Bot memory is just Markdown files in the agent workspace:
 - Daily notes in `memory/YYYY-MM-DD.md`
 - Curated long-term notes in `MEMORY.md` (main/private sessions only)
 
-Clawdbot also runs a **silent pre-compaction memory flush** to remind the model
+Pool Bot also runs a **silent pre-compaction memory flush** to remind the model
 to write durable notes before auto-compaction. This only runs when the workspace
 is writable (read-only sandboxes skip it). See [Memory](/concepts/memory).
 
@@ -1152,11 +1147,11 @@ does **not** grant embeddings access, so **signing in with Codex (OAuth or the
 Codex CLI login)** does not help for semantic memory search. OpenAI embeddings
 still need a real API key (`OPENAI_API_KEY` or `models.providers.openai.apiKey`).
 
-If you don’t set a provider explicitly, Clawdbot auto-selects a provider when it
+If you don’t set a provider explicitly, Pool Bot auto-selects a provider when it
 can resolve an API key (auth profiles, `models.providers.*.apiKey`, or env vars).
 It prefers OpenAI if an OpenAI key resolves, otherwise Gemini if a Gemini key
 resolves. If neither key is available, memory search stays disabled until you
-configure it. If you have a local model path configured and present, Clawdbot
+configure it. If you have a local model path configured and present, Pool Bot
 prefers `local`.
 
 If you’d rather stay local, set `memorySearch.provider = "local"` (and optionally
@@ -1176,12 +1171,12 @@ Docs: [Memory](/concepts/memory), [Context](/concepts/context).
 
 ## Where things live on disk
 
-### Is all data used with Clawdbot saved locally
+### Is all data used with Pool Bot saved locally
 
-No - **Clawdbot’s state is local**, but **external services still see what you send them**.
+No - **Pool Bot’s state is local**, but **external services still see what you send them**.
 
 - **Local by default:** sessions, memory files, config, and workspace live on the Gateway host
-  (`~/.clawdbot` + your workspace directory).
+  (`~/.poolbot` + your workspace directory).
 - **Remote by necessity:** messages you send to model providers (Anthropic/OpenAI/etc.) go to
   their APIs, and chat platforms (WhatsApp/Telegram/Slack/etc.) store message data on their
   servers.
@@ -1190,13 +1185,13 @@ No - **Clawdbot’s state is local**, but **external services still see what you
 
 Related: [Agent workspace](/concepts/agent-workspace), [Memory](/concepts/memory).
 
-### Where does Clawdbot store its data
+### Where does Pool Bot store its data
 
-Everything lives under `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`):
+Everything lives under `$CLAWDBOT_STATE_DIR` (default: `~/.poolbot`):
 
 | Path | Purpose |
 |------|---------|
-| `$CLAWDBOT_STATE_DIR/clawdbot.json` | Main config (JSON5) |
+| `$CLAWDBOT_STATE_DIR/poolbot.json` | Main config (JSON5) |
 | `$CLAWDBOT_STATE_DIR/credentials/oauth.json` | Legacy OAuth import (copied into auth profiles on first use) |
 | `$CLAWDBOT_STATE_DIR/agents/<agentId>/agent/auth-profiles.json` | Auth profiles (OAuth + API keys) |
 | `$CLAWDBOT_STATE_DIR/agents/<agentId>/agent/auth.json` | Runtime auth cache (managed automatically) |
@@ -1205,18 +1200,18 @@ Everything lives under `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`):
 | `$CLAWDBOT_STATE_DIR/agents/<agentId>/sessions/` | Conversation history & state (per agent) |
 | `$CLAWDBOT_STATE_DIR/agents/<agentId>/sessions/sessions.json` | Session metadata (per agent) |
 
-Legacy single‑agent path: `~/.clawdbot/agent/*` (migrated by `clawdbot doctor`).
+Legacy single‑agent path: `~/.poolbot/agent/*` (migrated by `poolbot doctor`).
 
 Your **workspace** (AGENTS.md, memory files, skills, etc.) is separate and configured via `agents.defaults.workspace` (default: `~/clawd`).
 
 ### Where should AGENTSmd SOULmd USERmd MEMORYmd live
 
-These files live in the **agent workspace**, not `~/.clawdbot`.
+These files live in the **agent workspace**, not `~/.poolbot`.
 
 - **Workspace (per agent)**: `AGENTS.md`, `SOUL.md`, `IDENTITY.md`, `USER.md`,
   `MEMORY.md` (or `memory.md`), `memory/YYYY-MM-DD.md`, optional `HEARTBEAT.md`.
-- **State dir (`~/.clawdbot`)**: config, credentials, auth profiles, sessions, logs,
-  and shared skills (`~/.clawdbot/skills`).
+- **State dir (`~/.poolbot`)**: config, credentials, auth profiles, sessions, logs,
+  and shared skills (`~/.poolbot/skills`).
 
 Default workspace is `~/clawd`, configurable via:
 
@@ -1241,13 +1236,13 @@ Put your **agent workspace** in a **private** git repo and back it up somewhere
 private (for example GitHub private). This captures memory + AGENTS/SOUL/USER
 files, and lets you restore the assistant’s “mind” later.
 
-Do **not** commit anything under `~/.clawdbot` (credentials, sessions, tokens).
+Do **not** commit anything under `~/.poolbot` (credentials, sessions, tokens).
 If you need a full restore, back up both the workspace and the state directory
 separately (see the migration question above).
 
 Docs: [Agent workspace](/concepts/agent-workspace).
 
-### How do I completely uninstall Clawdbot
+### How do I completely uninstall Pool Bot
 
 See the dedicated guide: [Uninstall](/install/uninstall).
 
@@ -1258,7 +1253,7 @@ Relative paths resolve inside the workspace, but absolute paths can access other
 host locations unless sandboxing is enabled. If you need isolation, use
 [`agents.defaults.sandbox`](/gateway/sandboxing) or per‑agent sandbox settings. If you
 want a repo to be the default working directory, point that agent’s
-`workspace` to the repo root. The Clawdbot repo is just source code; keep the
+`workspace` to the repo root. The Pool Bot repo is just source code; keep the
 workspace separate unless you intentionally want the agent to work inside it.
 
 Example (repo as default cwd):
@@ -1281,7 +1276,7 @@ Session state is owned by the **gateway host**. If you’re in remote mode, the
 
 ### What format is the config Where is it
 
-Clawdbot reads an optional **JSON5** config from `$CLAWDBOT_CONFIG_PATH` (default: `~/.clawdbot/clawdbot.json`):
+Pool Bot reads an optional **JSON5** config from `$CLAWDBOT_CONFIG_PATH` (default: `~/.poolbot/poolbot.json`):
 
 ```
 $CLAWDBOT_CONFIG_PATH
@@ -1313,7 +1308,7 @@ Notes:
 
 The wizard generates a gateway token by default (even on loopback) so **local WS clients must authenticate**. This blocks other local processes from calling the Gateway. Paste the token into the Control UI settings (or your client config) to connect.
 
-If you **really** want open loopback, remove `gateway.auth` from your config. Doctor can generate a token for you any time: `clawdbot doctor --generate-gateway-token`.
+If you **really** want open loopback, remove `gateway.auth` from your config. Doctor can generate a token for you any time: `poolbot doctor --generate-gateway-token`.
 
 ### Do I have to restart after changing config
 
@@ -1325,7 +1320,7 @@ The Gateway watches the config and supports hot‑reload:
 ### How do I enable web search and web fetch
 
 `web_fetch` works without an API key. `web_search` requires a Brave Search API
-key. **Recommended:** run `clawdbot configure --section web` to store it in
+key. **Recommended:** run `poolbot configure --section web` to store it in
 `tools.web.search.apiKey`. Environment alternative: set `BRAVE_API_KEY` for the
 Gateway process.
 
@@ -1349,7 +1344,7 @@ Gateway process.
 Notes:
 - If you use allowlists, add `web_search`/`web_fetch` or `group:web`.
 - `web_fetch` is enabled by default (unless explicitly disabled).
-- Daemons read env vars from `~/.clawdbot/.env` (or the service environment).
+- Daemons read env vars from `~/.poolbot/.env` (or the service environment).
 
 Docs: [Web tools](/tools/web).
 
@@ -1365,7 +1360,7 @@ The common pattern is **one Gateway** (e.g. Raspberry Pi) plus **nodes** and **a
 
 Docs: [Nodes](/nodes), [Remote access](/gateway/remote), [Multi-Agent Routing](/concepts/multi-agent), [Sub-agents](/tools/subagents), [TUI](/tui).
 
-### Can the Clawdbot browser run headless
+### Can the Pool Bot browser run headless
 
 Yes. It’s a config option:
 
@@ -1416,8 +1411,8 @@ Typical setup:
    so it can register as a node.
 5) Approve the node on the Gateway:
    ```bash
-   clawdbot nodes pending
-   clawdbot nodes approve <requestId>
+   poolbot nodes pending
+   poolbot nodes approve <requestId>
    ```
 
 No separate TCP bridge is required; nodes connect over the Gateway WebSocket.
@@ -1430,9 +1425,9 @@ Docs: [Nodes](/nodes), [Gateway protocol](/gateway/protocol), [macOS remote mode
 ### Tailscale is connected but I get no replies What now
 
 Check the basics:
-- Gateway is running: `clawdbot gateway status`
-- Gateway health: `clawdbot status`
-- Channel health: `clawdbot channels status`
+- Gateway is running: `poolbot gateway status`
+- Gateway health: `poolbot status`
+- Channel health: `poolbot channels status`
 
 Then verify auth and routing:
 - If you use Tailscale Serve, make sure `gateway.auth.allowTailscale` is set correctly.
@@ -1441,7 +1436,7 @@ Then verify auth and routing:
 
 Docs: [Tailscale](/gateway/tailscale), [Remote access](/gateway/remote), [Channels](/channels).
 
-### Can two Clawdbots talk to each other local VPS
+### Can two Pool Bots talk to each other local VPS
 
 Yes. There is no built-in "bot-to-bot" bridge, but you can wire it up in a few
 reliable ways:
@@ -1450,13 +1445,13 @@ reliable ways:
 Have Bot A send a message to Bot B, then let Bot B reply as usual.
 
 **CLI bridge (generic):** run a script that calls the other Gateway with
-`clawdbot agent --message ... --deliver`, targeting a chat where the other bot
-listens. If one bot is on Railway/VPS, point your CLI at that remote Gateway
+`poolbot agent --message ... --deliver`, targeting a chat where the other bot
+listens. If one bot is on a remote VPS, point your CLI at that remote Gateway
 via SSH/Tailscale (see [Remote access](/gateway/remote)).
 
 Example pattern (run from a machine that can reach the target Gateway):
 ```bash
-clawdbot agent --message "Hello from local bot" --deliver --channel telegram --reply-to <chat-id>
+poolbot agent --message "Hello from local bot" --deliver --channel telegram --reply-to <chat-id>
 ```
 
 Tip: add a guardrail so the two bots do not loop endlessly (mention-only, channel
@@ -1485,7 +1480,7 @@ setup is an always‑on host plus your laptop as a node.
 - **Safer execution controls.** `system.run` is gated by node allowlists/approvals on that laptop.
 - **More device tools.** Nodes expose `canvas`, `camera`, and `screen` in addition to `system.run`.
 - **Local browser automation.** Keep the Gateway on a VPS, but run Chrome locally and relay control
-  with the Chrome extension + `clawdbot browser serve`.
+  with the Chrome extension + a node host on the laptop.
 
 SSH is fine for ad‑hoc shell access, but nodes are simpler for ongoing agent workflows and
 device automation.
@@ -1520,14 +1515,14 @@ Yes. `config.apply` validates + writes the full config and restarts the Gateway
 else is removed.
 
 Recover:
-- Restore from backup (git or a copied `~/.clawdbot/clawdbot.json`).
-- If you have no backup, re-run `clawdbot doctor` and reconfigure channels/models.
+- Restore from backup (git or a copied `~/.poolbot/poolbot.json`).
+- If you have no backup, re-run `poolbot doctor` and reconfigure channels/models.
 - If this was unexpected, file a bug and include your last known config or any backup.
 - A local coding agent can often reconstruct a working config from logs or history.
 
 Avoid it:
-- Use `clawdbot config set` for small changes.
-- Use `clawdbot configure` for interactive edits.
+- Use `poolbot config set` for small changes.
+- Use `poolbot configure` for interactive edits.
 
 Docs: [Config](/cli/config), [Configure](/cli/configure), [Doctor](/gateway/doctor).
 
@@ -1561,7 +1556,7 @@ Minimal steps:
 
 If you want the Control UI without SSH, use Tailscale Serve on the VPS:
 ```bash
-clawdbot gateway --tailscale serve
+poolbot gateway --tailscale serve
 ```
 This keeps the gateway bound to loopback and exposes HTTPS via Tailscale. See [Tailscale](/gateway/tailscale).
 
@@ -1575,20 +1570,20 @@ Recommended setup:
    The app will tunnel the Gateway port and connect as a node.
 3) **Approve the node** on the gateway:
    ```bash
-   clawdbot nodes pending
-   clawdbot nodes approve <requestId>
+   poolbot nodes pending
+   poolbot nodes approve <requestId>
    ```
 
 Docs: [Gateway protocol](/gateway/protocol), [Discovery](/gateway/discovery), [macOS remote mode](/platforms/mac/remote).
 
 ## Env vars and .env loading
 
-### How does Clawdbot load environment variables
+### How does Pool Bot load environment variables
 
-Clawdbot reads env vars from the parent process (shell, launchd/systemd, CI, etc.) and additionally loads:
+Pool Bot reads env vars from the parent process (shell, launchd/systemd, CI, etc.) and additionally loads:
 
 - `.env` from the current working directory
-- a global fallback `.env` from `~/.clawdbot/.env` (aka `$CLAWDBOT_STATE_DIR/.env`)
+- a global fallback `.env` from `~/.poolbot/.env` (aka `$CLAWDBOT_STATE_DIR/.env`)
 
 Neither `.env` file overrides existing env vars.
 
@@ -1609,7 +1604,7 @@ See [/environment](/environment) for full precedence and sources.
 
 Two common fixes:
 
-1) Put the missing keys in `~/.clawdbot/.env` so they’re picked up even when the service doesn’t inherit your shell env.
+1) Put the missing keys in `~/.poolbot/.env` so they’re picked up even when the service doesn’t inherit your shell env.
 2) Enable shell import (opt‑in convenience):
 
 ```json5
@@ -1628,14 +1623,14 @@ This runs your login shell and imports only missing expected keys (never overrid
 
 ### I set COPILOTGITHUBTOKEN but models status shows Shell env off Why
 
-`clawdbot models status` reports whether **shell env import** is enabled. “Shell env: off”
-does **not** mean your env vars are missing - it just means Clawdbot won’t load
+`poolbot models status` reports whether **shell env import** is enabled. “Shell env: off”
+does **not** mean your env vars are missing - it just means Pool Bot won’t load
 your login shell automatically.
 
 If the Gateway runs as a service (launchd/systemd), it won’t inherit your shell
 environment. Fix by doing one of these:
 
-1) Put the token in `~/.clawdbot/.env`:
+1) Put the token in `~/.poolbot/.env`:
    ```
    COPILOT_GITHUB_TOKEN=...
    ```
@@ -1644,7 +1639,7 @@ environment. Fix by doing one of these:
 
 Then restart the gateway and recheck:
 ```bash
-clawdbot models status
+poolbot models status
 ```
 
 Copilot tokens are read from `COPILOT_GITHUB_TOKEN` (also `GH_TOKEN` / `GITHUB_TOKEN`).
@@ -1670,7 +1665,7 @@ transcripts - it just starts a new session.
 }
 ```
 
-### Is there a way to make a team of Clawdbots one CEO and many agents
+### Is there a way to make a team of Pool Bots one CEO and many agents
 
 Yes, via **multi-agent routing** and **sub-agents**. You can create one coordinator
 agent and several worker agents with their own workspaces and models.
@@ -1694,30 +1689,30 @@ What helps:
 - Use sub-agents for long or parallel work so the main chat stays smaller.
 - Pick a model with a larger context window if this happens often.
 
-### How do I completely reset Clawdbot but keep it installed
+### How do I completely reset Pool Bot but keep it installed
 
 Use the reset command:
 
 ```bash
-clawdbot reset
+poolbot reset
 ```
 
 Non-interactive full reset:
 
 ```bash
-clawdbot reset --scope full --yes --non-interactive
+poolbot reset --scope full --yes --non-interactive
 ```
 
 Then re-run onboarding:
 
 ```bash
-clawdbot onboard --install-daemon
+poolbot onboard --install-daemon
 ```
 
 Notes:
 - The onboarding wizard also offers **Reset** if it sees an existing config. See [Wizard](/start/wizard).
-- If you used profiles (`--profile` / `CLAWDBOT_PROFILE`), reset each state dir (defaults are `~/.clawdbot-<profile>`).
-- Dev reset: `clawdbot gateway --dev --reset` (dev-only; wipes dev config + credentials + sessions + workspace).
+- If you used profiles (`--profile` / `CLAWDBOT_PROFILE`), reset each state dir (defaults are `~/.poolbot-<profile>`).
+- Dev reset: `poolbot gateway --dev --reset` (dev-only; wipes dev config + credentials + sessions + workspace).
 
 ### Im getting context too large errors how do I reset or compact
 
@@ -1766,14 +1761,14 @@ Heartbeats run every **30m** by default. Tune or disable them:
 ```
 
 If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown
-headers like `# Heading`), Clawdbot skips the heartbeat run to save API calls.
+headers like `# Heading`), Pool Bot skips the heartbeat run to save API calls.
 If the file is missing, the heartbeat still runs and the model decides what to do.
 
 Per-agent overrides use `agents.list[].heartbeat`. Docs: [Heartbeat](/gateway/heartbeat).
 
 ### Do I need to add a bot account to a WhatsApp group
 
-No. Clawdbot runs on **your own account**, so if you’re in the group, Clawdbot can see it.
+No. Pool Bot runs on **your own account**, so if you’re in the group, Pool Bot can see it.
 By default, group replies are blocked until you allow senders (`groupPolicy: "allowlist"`).
 
 If you want only **you** to be able to trigger group replies:
@@ -1794,7 +1789,7 @@ If you want only **you** to be able to trigger group replies:
 Option 1 (fastest): tail logs and send a test message in the group:
 
 ```bash
-clawdbot logs --follow --json
+poolbot logs --follow --json
 ```
 
 Look for `chatId` (or `from`) ending in `@g.us`, like:
@@ -1803,12 +1798,12 @@ Look for `chatId` (or `from`) ending in `@g.us`, like:
 Option 2 (if already configured/allowlisted): list groups from config:
 
 ```bash
-clawdbot directory groups list --channel whatsapp
+poolbot directory groups list --channel whatsapp
 ```
 
 Docs: [WhatsApp](/channels/whatsapp), [Directory](/cli/directory), [Logs](/cli/logs).
 
-### Why doesnt Clawdbot reply in a group
+### Why doesnt Pool Bot reply in a group
 
 Two common causes:
 - Mention gating is on (default). You must @mention the bot (or match `mentionPatterns`).
@@ -1824,14 +1819,14 @@ Direct chats collapse to the main session by default. Groups/channels have their
 
 No hard limits. Dozens (even hundreds) are fine, but watch for:
 
-- **Disk growth:** sessions + transcripts live under `~/.clawdbot/agents/<agentId>/sessions/`.
+- **Disk growth:** sessions + transcripts live under `~/.poolbot/agents/<agentId>/sessions/`.
 - **Token cost:** more agents means more concurrent model usage.
 - **Ops overhead:** per-agent auth profiles, workspaces, and channel routing.
 
 Tips:
 - Keep one **active** workspace per agent (`agents.defaults.workspace`).
 - Prune old sessions (delete JSONL or store entries) if disk grows.
-- Use `clawdbot doctor` to spot stray workspaces and profile mismatches.
+- Use `poolbot doctor` to spot stray workspaces and profile mismatches.
 
 ### Can I run multiple bots or chats at the same time Slack and how should I set that up
 
@@ -1855,13 +1850,13 @@ Docs: [Multi‑Agent Routing](/concepts/multi-agent), [Slack](/channels/slack),
 
 ### What is the default model
 
-Clawdbot’s default model is whatever you set as:
+Pool Bot’s default model is whatever you set as:
 
 ```
 agents.defaults.model.primary
 ```
 
-Models are referenced as `provider/model` (example: `anthropic/claude-opus-4-5`). If you omit the provider, Clawdbot currently assumes `anthropic` as a temporary deprecation fallback - but you should still **explicitly** set `provider/model`.
+Models are referenced as `provider/model` (example: `anthropic/claude-opus-4-5`). If you omit the provider, Pool Bot currently assumes `anthropic` as a temporary deprecation fallback - but you should still **explicitly** set `provider/model`.
 
 ### What model do you recommend
 
@@ -1902,12 +1897,12 @@ Use **model commands** or edit only the **model** fields. Avoid full config repl
 
 Safe options:
 - `/model` in chat (quick, per-session)
-- `clawdbot models set ...` (updates just model config)
-- `clawdbot configure --section models` (interactive)
-- edit `agents.defaults.model` in `~/.clawdbot/clawdbot.json`
+- `poolbot models set ...` (updates just model config)
+- `poolbot configure --section models` (interactive)
+- edit `agents.defaults.model` in `~/.poolbot/poolbot.json`
 
 Avoid `config.apply` with a partial object unless you intend to replace the whole config.
-If you did overwrite config, restore from backup or re-run `clawdbot doctor` to repair.
+If you did overwrite config, restore from backup or re-run `poolbot doctor` to repair.
 
 Docs: [Models](/concepts/models), [Configure](/cli/configure), [Config](/cli/config), [Doctor](/gateway/doctor).
 
@@ -1941,8 +1936,8 @@ You can list available models with `/model`, `/model list`, or `/model status`.
 You can also force a specific auth profile for the provider (per session):
 
 ```
-/model opus@anthropic:claude-cli
 /model opus@anthropic:default
+/model opus@anthropic:work
 ```
 
 Tip: `/model status` shows which agent is active, which `auth-profiles.json` file is being used, and which auth profile will be tried next.
@@ -1995,7 +1990,7 @@ Fix checklist:
    `minimax/MiniMax-M2.1-lightning`.
 4) Run:
    ```bash
-   clawdbot models list
+   poolbot models list
    ```
    and pick from the list (or `/model list` in chat).
 
@@ -2036,7 +2031,7 @@ Docs: [Models](/concepts/models), [Multi-Agent Routing](/concepts/multi-agent),
 
 ### Are opus sonnet gpt builtin shortcuts
 
-Yes. Clawdbot ships a few default shorthands (only applied when the model exists in `agents.defaults.models`):
+Yes. Pool Bot ships a few default shorthands (only applied when the model exists in `agents.defaults.models`):
 
 - `opus` → `anthropic/claude-opus-4-5`
 - `sonnet` → `anthropic/claude-sonnet-4-5`
@@ -2106,11 +2101,11 @@ This usually means the **new agent** has an empty auth store. Auth is per-agent
 stored in:
 
 ```
-~/.clawdbot/agents/<agentId>/agent/auth-profiles.json
+~/.poolbot/agents/<agentId>/agent/auth-profiles.json
 ```
 
 Fix options:
-- Run `clawdbot agents add <id>` and configure auth during the wizard.
+- Run `poolbot agents add <id>` and configure auth during the wizard.
 - Or copy `auth-profiles.json` from the main agent’s `agentDir` into the new agent’s `agentDir`.
 
 Do **not** reuse `agentDir` across agents; it causes auth/session collisions.
@@ -2124,7 +2119,7 @@ Failover happens in two stages:
 1) **Auth profile rotation** within the same provider.
 2) **Model fallback** to the next model in `agents.defaults.model.fallbacks`.
 
-Cooldowns apply to failing profiles (exponential backoff), so Clawdbot can keep responding even when a provider is rate‑limited or temporarily failing.
+Cooldowns apply to failing profiles (exponential backoff), so Pool Bot can keep responding even when a provider is rate‑limited or temporarily failing.
 
 ### What does this error mean
 
@@ -2137,39 +2132,35 @@ It means the system attempted to use the auth profile ID `anthropic:default`, bu
 ### Fix checklist for No credentials found for profile anthropicdefault
 
 - **Confirm where auth profiles live** (new vs legacy paths)
-  - Current: `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json`
-  - Legacy: `~/.clawdbot/agent/*` (migrated by `clawdbot doctor`)
+  - Current: `~/.poolbot/agents/<agentId>/agent/auth-profiles.json`
+  - Legacy: `~/.poolbot/agent/*` (migrated by `poolbot doctor`)
 - **Confirm your env var is loaded by the Gateway**
-  - If you set `ANTHROPIC_API_KEY` in your shell but run the Gateway via systemd/launchd, it may not inherit it. Put it in `~/.clawdbot/.env` or enable `env.shellEnv`.
+  - If you set `ANTHROPIC_API_KEY` in your shell but run the Gateway via systemd/launchd, it may not inherit it. Put it in `~/.poolbot/.env` or enable `env.shellEnv`.
 - **Make sure you’re editing the correct agent**
   - Multi‑agent setups mean there can be multiple `auth-profiles.json` files.
 - **Sanity‑check model/auth status**
-  - Use `clawdbot models status` to see configured models and whether providers are authenticated.
+  - Use `poolbot models status` to see configured models and whether providers are authenticated.
 
-**Fix checklist for No credentials found for profile anthropic claude cli**
+**Fix checklist for No credentials found for profile anthropic**
 
-This means the run is pinned to the **Claude Code CLI** profile, but the Gateway
-can’t find that profile in its auth store.
+This means the run is pinned to an Anthropic auth profile, but the Gateway
+can’t find it in its auth store.
 
-- **Sync the Claude Code CLI token on the gateway host**
-  - Run `clawdbot models status` (it loads + syncs Claude Code CLI credentials).
-  - If it still says missing: run `claude setup-token` (or `clawdbot models auth setup-token --provider anthropic`) and retry.
-- **If the token was created on another machine**
-  - Paste it into the gateway host with `clawdbot models auth paste-token --provider anthropic`.
-- **Check the profile mode**
-  - `auth.profiles["anthropic:claude-cli"].mode` must be `"oauth"` (token mode rejects OAuth credentials).
+- **Use a setup-token**
+  - Run `claude setup-token`, then paste it with `poolbot models auth setup-token --provider anthropic`.
+  - If the token was created on another machine, use `poolbot models auth paste-token --provider anthropic`.
 - **If you want to use an API key instead**
-  - Put `ANTHROPIC_API_KEY` in `~/.clawdbot/.env` on the **gateway host**.
-  - Clear any pinned order that forces `anthropic:claude-cli`:
+  - Put `ANTHROPIC_API_KEY` in `~/.poolbot/.env` on the **gateway host**.
+  - Clear any pinned order that forces a missing profile:
     ```bash
-    clawdbot models auth order clear --provider anthropic
+    poolbot models auth order clear --provider anthropic
     ```
 - **Confirm you’re running commands on the gateway host**
   - In remote mode, auth profiles live on the gateway machine, not your laptop.
 
 ### Why did it also try Google Gemini and fail
 
-If your model config includes Google Gemini as a fallback (or you switched to a Gemini shorthand), Clawdbot will try it during model fallback. If you haven’t configured Google credentials, you’ll see `No API key found for provider "google"`.
+If your model config includes Google Gemini as a fallback (or you switched to a Gemini shorthand), Pool Bot will try it during model fallback. If you haven’t configured Google credentials, you’ll see `No API key found for provider "google"`.
 
 Fix: either provide Google auth, or remove/avoid Google models in `agents.defaults.model.fallbacks` / aliases so fallback doesn’t route there.
 
@@ -2178,23 +2169,23 @@ Fix: either provide Google auth, or remove/avoid Google models in `agents.defaul
 Cause: the session history contains **thinking blocks without signatures** (often from
 an aborted/partial stream). Google Antigravity requires signatures for thinking blocks.
 
-Fix: Clawdbot now strips unsigned thinking blocks for Google Antigravity Claude. If it still appears, start a **new session** or set `/thinking off` for that agent.
+Fix: Pool Bot now strips unsigned thinking blocks for Google Antigravity Claude. If it still appears, start a **new session** or set `/thinking off` for that agent.
 
 ## Auth profiles: what they are and how to manage them
 
-Related: [/concepts/oauth](/concepts/oauth) (OAuth flows, token storage, multi-account patterns, CLI sync)
+Related: [/concepts/oauth](/concepts/oauth) (OAuth flows, token storage, multi-account patterns)
 
 ### What is an auth profile
 
 An auth profile is a named credential record (OAuth or API key) tied to a provider. Profiles live in:
 
 ```
-~/.clawdbot/agents/<agentId>/agent/auth-profiles.json
+~/.poolbot/agents/<agentId>/agent/auth-profiles.json
 ```
 
 ### What are typical profile IDs
 
-Clawdbot uses provider‑prefixed IDs like:
+Pool Bot uses provider‑prefixed IDs like:
 
 - `anthropic:default` (common when no email identity exists)
 - `anthropic:<email>` for OAuth identities
@@ -2204,38 +2195,38 @@ Clawdbot uses provider‑prefixed IDs like:
 
 Yes. Config supports optional metadata for profiles and an ordering per provider (`auth.order.<provider>`). This does **not** store secrets; it maps IDs to provider/mode and sets rotation order.
 
-Clawdbot may temporarily skip a profile if it’s in a short **cooldown** (rate limits/timeouts/auth failures) or a longer **disabled** state (billing/insufficient credits). To inspect this, run `clawdbot models status --json` and check `auth.unusableProfiles`. Tuning: `auth.cooldowns.billingBackoffHours*`.
+Pool Bot may temporarily skip a profile if it’s in a short **cooldown** (rate limits/timeouts/auth failures) or a longer **disabled** state (billing/insufficient credits). To inspect this, run `poolbot models status --json` and check `auth.unusableProfiles`. Tuning: `auth.cooldowns.billingBackoffHours*`.
 
 You can also set a **per-agent** order override (stored in that agent’s `auth-profiles.json`) via the CLI:
 
 ```bash
 # Defaults to the configured default agent (omit --agent)
-clawdbot models auth order get --provider anthropic
+poolbot models auth order get --provider anthropic
 
 # Lock rotation to a single profile (only try this one)
-clawdbot models auth order set --provider anthropic anthropic:claude-cli
+poolbot models auth order set --provider anthropic anthropic:default
 
 # Or set an explicit order (fallback within provider)
-clawdbot models auth order set --provider anthropic anthropic:claude-cli anthropic:default
+poolbot models auth order set --provider anthropic anthropic:work anthropic:default
 
 # Clear override (fall back to config auth.order / round-robin)
-clawdbot models auth order clear --provider anthropic
+poolbot models auth order clear --provider anthropic
 ```
 
 To target a specific agent:
 
 ```bash
-clawdbot models auth order set --provider anthropic --agent main anthropic:claude-cli
+poolbot models auth order set --provider anthropic --agent main anthropic:default
 ```
 
 ### OAuth vs API key whats the difference
 
-Clawdbot supports both:
+Pool Bot supports both:
 
 - **OAuth** often leverages subscription access (where applicable).
 - **API keys** use pay‑per‑token billing.
 
-The wizard explicitly supports Anthropic OAuth and OpenAI Codex OAuth and can store API keys for you.
+The wizard explicitly supports Anthropic setup-token and OpenAI Codex OAuth and can store API keys for you.
 
 ## Gateway: ports, “already running”, and remote mode
 
@@ -2249,32 +2240,32 @@ Precedence:
 --port > CLAWDBOT_GATEWAY_PORT > gateway.port > default 18789
 ```
 
-### Why does clawdbot gateway status say Runtime running but RPC probe failed
+### Why does poolbot gateway status say Runtime running but RPC probe failed
 
 Because “running” is the **supervisor’s** view (launchd/systemd/schtasks). The RPC probe is the CLI actually connecting to the gateway WebSocket and calling `status`.
 
-Use `clawdbot gateway status` and trust these lines:
+Use `poolbot gateway status` and trust these lines:
 - `Probe target:` (the URL the probe actually used)
 - `Listening:` (what’s actually bound on the port)
 - `Last gateway error:` (common root cause when the process is alive but the port isn’t listening)
 
-### Why does clawdbot gateway status show Config cli and Config service different
+### Why does poolbot gateway status show Config cli and Config service different
 
 You’re editing one config file while the service is running another (often a `--profile` / `CLAWDBOT_STATE_DIR` mismatch).
 
 Fix:
 ```bash
-clawdbot gateway install --force
+poolbot gateway install --force
 ```
 Run that from the same `--profile` / environment you want the service to use.
 
 ### What does another gateway instance is already listening mean
 
-Clawdbot enforces a runtime lock by binding the WebSocket listener immediately on startup (default `ws://127.0.0.1:18789`). If the bind fails with `EADDRINUSE`, it throws `GatewayLockError` indicating another instance is already listening.
+Pool Bot enforces a runtime lock by binding the WebSocket listener immediately on startup (default `ws://127.0.0.1:18789`). If the bind fails with `EADDRINUSE`, it throws `GatewayLockError` indicating another instance is already listening.
 
-Fix: stop the other instance, free the port, or run with `clawdbot gateway --port <port>`.
+Fix: stop the other instance, free the port, or run with `poolbot gateway --port <port>`.
 
-### How do I run Clawdbot in remote mode client connects to a Gateway elsewhere
+### How do I run Pool Bot in remote mode client connects to a Gateway elsewhere
 
 Set `gateway.mode: "remote"` and point to a remote WebSocket URL, optionally with a token/password:
 
@@ -2292,7 +2283,7 @@ Set `gateway.mode: "remote"` and point to a remote WebSocket URL, optionally wit
 ```
 
 Notes:
-- `clawdbot gateway` only starts when `gateway.mode` is `local` (or you pass the override flag).
+- `poolbot gateway` only starts when `gateway.mode` is `local` (or you pass the override flag).
 - The macOS app watches the config file and switches modes live when these values change.
 
 ### The Control UI says unauthorized or keeps reconnecting What now
@@ -2300,16 +2291,16 @@ Notes:
 Your gateway is running with auth enabled (`gateway.auth.*`), but the UI is not sending the matching token/password.
 
 Facts (from code):
-- The Control UI stores the token in browser localStorage key `clawdbot.control.settings.v1`.
+- The Control UI stores the token in browser localStorage key `poolbot.control.settings.v1`.
 - The UI can import `?token=...` (and/or `?password=...`) once, then strips it from the URL.
 
 Fix:
-- Fastest: `clawdbot dashboard` (prints + copies tokenized link, tries to open; shows SSH hint if headless).
-- If you don’t have a token yet: `clawdbot doctor --generate-gateway-token`.
+- Fastest: `poolbot dashboard` (prints + copies tokenized link, tries to open; shows SSH hint if headless).
+- If you don’t have a token yet: `poolbot doctor --generate-gateway-token`.
 - If remote, tunnel first: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/?token=...`.
 - Set `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`) on the gateway host.
 - In the Control UI settings, paste the same token (or refresh with a one-time `?token=...` link).
-- Still stuck? Run `clawdbot status --all` and follow [Troubleshooting](/gateway/troubleshooting). See [Dashboard](/web/dashboard) for auth details.
+- Still stuck? Run `poolbot status --all` and follow [Troubleshooting](/gateway/troubleshooting). See [Dashboard](/web/dashboard) for auth details.
 
 ### I set gatewaybind tailnet but it cant bind nothing listens
 
@@ -2333,11 +2324,11 @@ Yes, but you must isolate:
 - `gateway.port` (unique ports)
 
 Quick setup (recommended):
-- Use `clawdbot --profile <name> …` per instance (auto-creates `~/.clawdbot-<name>`).
+- Use `poolbot --profile <name> …` per instance (auto-creates `~/.poolbot-<name>`).
 - Set a unique `gateway.port` in each profile config (or pass `--port` for manual runs).
-- Install a per-profile service: `clawdbot --profile <name> gateway install`.
+- Install a per-profile service: `poolbot --profile <name> gateway install`.
 
-Profiles also suffix service names (`com.clawdbot.<profile>`, `clawdbot-gateway-<profile>.service`, `Clawdbot Gateway (<profile>)`).
+Profiles also suffix service names (`com.poolbot.<profile>`, `poolbot-gateway-<profile>.service`, `Pool Bot Gateway (<profile>)`).
 Full guide: [Multiple gateways](/gateway/multiple-gateways).
 
 ### What does invalid handshake code 1008 mean
@@ -2358,7 +2349,7 @@ Quick fixes:
 
 If you’re using the CLI or TUI, the URL should look like:
 ```
-clawdbot tui --url ws://<host>:18789 --token <token>
+poolbot tui --url ws://<host>:18789 --token <token>
 ```
 
 Protocol details: [Gateway protocol](/gateway/protocol).
@@ -2370,7 +2361,7 @@ Protocol details: [Gateway protocol](/gateway/protocol).
 File logs (structured):
 
 ```
-/tmp/clawdbot/clawdbot-YYYY-MM-DD.log
+/tmp/poolbot/poolbot-YYYY-MM-DD.log
 ```
 
 You can set a stable path via `logging.file`. File log level is controlled by `logging.level`. Console verbosity is controlled by `--verbose` and `logging.consoleLevel`.
@@ -2378,13 +2369,13 @@ You can set a stable path via `logging.file`. File log level is controlled by `l
 Fastest log tail:
 
 ```bash
-clawdbot logs --follow
+poolbot logs --follow
 ```
 
 Service/supervisor logs (when the gateway runs via launchd/systemd):
-- macOS: `$CLAWDBOT_STATE_DIR/logs/gateway.log` and `gateway.err.log` (default: `~/.clawdbot/logs/...`; profiles use `~/.clawdbot-<profile>/logs/...`)
-- Linux: `journalctl --user -u clawdbot-gateway[-<profile>].service -n 200 --no-pager`
-- Windows: `schtasks /Query /TN "Clawdbot Gateway (<profile>)" /V /FO LIST`
+- macOS: `$CLAWDBOT_STATE_DIR/logs/gateway.log` and `gateway.err.log` (default: `~/.poolbot/logs/...`; profiles use `~/.poolbot-<profile>/logs/...`)
+- Linux: `journalctl --user -u poolbot-gateway[-<profile>].service -n 200 --no-pager`
+- Windows: `schtasks /Query /TN "Pool Bot Gateway (<profile>)" /V /FO LIST`
 
 See [Troubleshooting](/gateway/troubleshooting#log-locations) for more.
 
@@ -2393,13 +2384,13 @@ See [Troubleshooting](/gateway/troubleshooting#log-locations) for more.
 Use the gateway helpers:
 
 ```bash
-clawdbot gateway status
-clawdbot gateway restart
+poolbot gateway status
+poolbot gateway restart
 ```
 
-If you run the gateway manually, `clawdbot gateway --force` can reclaim the port. See [Gateway](/gateway).
+If you run the gateway manually, `poolbot gateway --force` can reclaim the port. See [Gateway](/gateway).
 
-### I closed my terminal on Windows how do I restart Clawdbot
+### I closed my terminal on Windows how do I restart Pool Bot
 
 There are **two Windows install modes**:
 
@@ -2409,14 +2400,14 @@ Open PowerShell, enter WSL, then restart:
 
 ```powershell
 wsl
-clawdbot gateway status
-clawdbot gateway restart
+poolbot gateway status
+poolbot gateway restart
 ```
 
 If you never installed the service, start it in the foreground:
 
 ```bash
-clawdbot gateway run
+poolbot gateway run
 ```
 
 **2) Native Windows (not recommended):** the Gateway runs directly in Windows.
@@ -2424,14 +2415,14 @@ clawdbot gateway run
 Open PowerShell and run:
 
 ```powershell
-clawdbot gateway status
-clawdbot gateway restart
+poolbot gateway status
+poolbot gateway restart
 ```
 
 If you run it manually (no service), use:
 
 ```powershell
-clawdbot gateway run
+poolbot gateway run
 ```
 
 Docs: [Windows (WSL2)](/platforms/windows), [Gateway service runbook](/gateway).
@@ -2441,10 +2432,10 @@ Docs: [Windows (WSL2)](/platforms/windows), [Gateway service runbook](/gateway).
 Start with a quick health sweep:
 
 ```bash
-clawdbot status
-clawdbot models status
-clawdbot channels status
-clawdbot logs --follow
+poolbot status
+poolbot models status
+poolbot channels status
+poolbot logs --follow
 ```
 
 Common causes:
@@ -2461,15 +2452,15 @@ Docs: [Channels](/channels), [Troubleshooting](/gateway/troubleshooting), [Remot
 
 This usually means the UI lost the WebSocket connection. Check:
 
-1) Is the Gateway running? `clawdbot gateway status`
-2) Is the Gateway healthy? `clawdbot status`
-3) Does the UI have the right token? `clawdbot dashboard`
+1) Is the Gateway running? `poolbot gateway status`
+2) Is the Gateway healthy? `poolbot status`
+3) Does the UI have the right token? `poolbot dashboard`
 4) If remote, is the tunnel/Tailscale link up?
 
 Then tail logs:
 
 ```bash
-clawdbot logs --follow
+poolbot logs --follow
 ```
 
 Docs: [Dashboard](/web/dashboard), [Remote access](/gateway/remote), [Troubleshooting](/gateway/troubleshooting).
@@ -2479,8 +2470,8 @@ Docs: [Dashboard](/web/dashboard), [Remote access](/gateway/remote), [Troublesho
 Start with logs and channel status:
 
 ```bash
-clawdbot channels status
-clawdbot channels logs --channel telegram
+poolbot channels status
+poolbot channels logs --channel telegram
 ```
 
 If you are on a VPS or behind a proxy, confirm outbound HTTPS is allowed and DNS works.
@@ -2493,9 +2484,9 @@ Docs: [Telegram](/channels/telegram), [Channel troubleshooting](/channels/troubl
 First confirm the Gateway is reachable and the agent can run:
 
 ```bash
-clawdbot status
-clawdbot models status
-clawdbot logs --follow
+poolbot status
+poolbot models status
+poolbot logs --follow
 ```
 
 In the TUI, use `/status` to see the current state. If you expect replies in a chat
@@ -2508,8 +2499,8 @@ Docs: [TUI](/tui), [Slash commands](/tools/slash-commands).
 If you installed the service:
 
 ```bash
-clawdbot gateway stop
-clawdbot gateway start
+poolbot gateway stop
+poolbot gateway start
 ```
 
 This stops/starts the **supervised service** (launchd on macOS, systemd on Linux).
@@ -2518,17 +2509,17 @@ Use this when the Gateway runs in the background as a daemon.
 If you’re running in the foreground, stop with Ctrl‑C, then:
 
 ```bash
-clawdbot gateway run
+poolbot gateway run
 ```
 
 Docs: [Gateway service runbook](/gateway).
 
-### ELI5 clawdbot gateway restart vs clawdbot gateway
+### ELI5 poolbot gateway restart vs poolbot gateway
 
-- `clawdbot gateway restart`: restarts the **background service** (launchd/systemd).
-- `clawdbot gateway`: runs the gateway **in the foreground** for this terminal session.
+- `poolbot gateway restart`: restarts the **background service** (launchd/systemd).
+- `poolbot gateway`: runs the gateway **in the foreground** for this terminal session.
 
-If you installed the service, use the gateway commands. Use `clawdbot gateway` when
+If you installed the service, use the gateway commands. Use `poolbot gateway` when
 you want a one-off, foreground run.
 
 ### Whats the fastest way to get more details when something fails
@@ -2539,12 +2530,12 @@ Start the Gateway with `--verbose` to get more console detail. Then inspect the
 
 ### My skill generated an imagePDF but nothing was sent
 
-Outbound attachments from the agent must include a `MEDIA:<path-or-url>` line (on its own line). See [Clawdbot assistant setup](/start/clawd) and [Agent send](/tools/agent-send).
+Outbound attachments from the agent must include a `MEDIA:<path-or-url>` line (on its own line). See [Pool Bot assistant setup](/start/clawd) and [Agent send](/tools/agent-send).
 
 CLI sending:
 
 ```bash
-clawdbot message send --target +15555550123 --message "Here you go" --media /path/to/file.png
+poolbot message send --target +15555550123 --message "Here you go" --media /path/to/file.png
 ```
 
 Also check:
@@ -2555,17 +2546,17 @@ See [Images](/nodes/images).
 
 ## Security and access control
 
-### Is it safe to expose Clawdbot to inbound DMs
+### Is it safe to expose Pool Bot to inbound DMs
 
 Treat inbound DMs as untrusted input. Defaults are designed to reduce risk:
 
 - Default behavior on DM‑capable channels is **pairing**:
   - Unknown senders receive a pairing code; the bot does not process their message.
-  - Approve with: `clawdbot pairing approve <channel> <code>`
-  - Pending requests are capped at **3 per channel**; check `clawdbot pairing list <channel>` if a code didn’t arrive.
+  - Approve with: `poolbot pairing approve <channel> <code>`
+  - Pending requests are capped at **3 per channel**; check `poolbot pairing list <channel>` if a code didn’t arrive.
 - Opening DMs publicly requires explicit opt‑in (`dmPolicy: "open"` and allowlist `"*"`).
 
-Run `clawdbot doctor` to surface risky DM policies.
+Run `poolbot doctor` to surface risky DM policies.
 
 ### Is prompt injection only a concern for public bots
 
@@ -2617,7 +2608,7 @@ Pairing codes are sent **only** when an unknown sender messages the bot and
 
 Check pending requests:
 ```bash
-clawdbot pairing list telegram
+poolbot pairing list telegram
 ```
 
 If you want immediate access, allowlist your sender id or set `dmPolicy: "open"`
@@ -2625,18 +2616,18 @@ for that account.
 
 ### WhatsApp will it message my contacts How does pairing work
 
-No. Default WhatsApp DM policy is **pairing**. Unknown senders only get a pairing code and their message is **not processed**. Clawdbot only replies to chats it receives or to explicit sends you trigger.
+No. Default WhatsApp DM policy is **pairing**. Unknown senders only get a pairing code and their message is **not processed**. Pool Bot only replies to chats it receives or to explicit sends you trigger.
 
 Approve pairing with:
 
 ```bash
-clawdbot pairing approve whatsapp <code>
+poolbot pairing approve whatsapp <code>
 ```
 
 List pending requests:
 
 ```bash
-clawdbot pairing list whatsapp
+poolbot pairing list whatsapp
 ```
 
 Wizard phone number prompt: it’s used to set your **allowlist/owner** so your own DMs are permitted. It’s not used for auto-sending. If you run on your personal WhatsApp number, use that number and enable `channels.whatsapp.selfChatMode`.
@@ -2687,7 +2678,7 @@ Most commands must be sent as a **standalone** message that starts with `/`, but
 
 ### How do I send a Discord message from Telegram Crosscontext messaging denied
 
-Clawdbot blocks **cross‑provider** messaging by default. If a tool call is bound
+Pool Bot blocks **cross‑provider** messaging by default. If a tool call is bound
 to Telegram, it won’t send to Discord unless you explicitly allow it.
 
 Enable cross‑provider messaging for the agent:
@@ -2728,8 +2719,8 @@ You can add options like `debounce:2s cap:25 drop:summarize` for followup modes.
 
 **Q: “What’s the default model for Anthropic with an API key?”**
 
-**A:** In Clawdbot, credentials and model selection are separate. Setting `ANTHROPIC_API_KEY` (or storing an Anthropic API key in auth profiles) enables authentication, but the actual default model is whatever you configure in `agents.defaults.model.primary` (for example, `anthropic/claude-sonnet-4-5` or `anthropic/claude-opus-4-5`). If you see `No credentials found for profile "anthropic:default"`, it means the Gateway couldn’t find Anthropic credentials in the expected `auth-profiles.json` for the agent that’s running.
+**A:** In Pool Bot, credentials and model selection are separate. Setting `ANTHROPIC_API_KEY` (or storing an Anthropic API key in auth profiles) enables authentication, but the actual default model is whatever you configure in `agents.defaults.model.primary` (for example, `anthropic/claude-sonnet-4-5` or `anthropic/claude-opus-4-5`). If you see `No credentials found for profile "anthropic:default"`, it means the Gateway couldn’t find Anthropic credentials in the expected `auth-profiles.json` for the agent that’s running.
 
 ---
 
-Still stuck? Ask in [Discord](https://discord.com/invite/clawd) or open a [GitHub discussion](https://github.com/clawdbot/clawdbot/discussions).
+Still stuck? Ask in [Discord](https://discord.com/discord.gg/poolbot) or open a [GitHub discussion](https://github.com/poolbot/poolbot/discussions).