@poolzin/pool-bot 2026.1.26 → 2026.1.29

package/docs/plugin.md

@@ -1,5 +1,5 @@
 ---
-summary: "Clawdbot plugins/extensions: discovery, config, and safety"
+summary: "Pool Bot plugins/extensions: discovery, config, and safety"
 read_when:
   - Adding or modifying plugins/extensions
   - Documenting plugin install or load rules
@@ -8,11 +8,11 @@ read_when:
 
 ## Quick start (new to plugins?)
 
-A plugin is just a **small code module** that extends Clawdbot with extra
+A plugin is just a **small code module** that extends Pool Bot with extra
 features (commands, tools, and Gateway RPC).
 
 Most of the time, you’ll use plugins when you want a feature that’s not built
-into core Clawdbot yet (or you want to keep optional features out of your main
+into core Pool Bot yet (or you want to keep optional features out of your main
 install).
 
 Fast path:
@@ -20,13 +20,13 @@ Fast path:
 1) See what’s already loaded:
 
 ```bash
-clawdbot plugins list
+poolbot plugins list
 ```
 
 2) Install an official plugin (example: Voice Call):
 
 ```bash
-clawdbot plugins install @clawdbot/voice-call
+poolbot plugins install @poolbot/voice-call
 ```
 
 3) Restart the Gateway, then configure under `plugins.entries.<id>.config`.
@@ -35,21 +35,21 @@ See [Voice Call](/plugins/voice-call) for a concrete example plugin.
 
 ## Available plugins (official)
 
-- Microsoft Teams is plugin-only as of 2026.1.15; install `@clawdbot/msteams` if you use Teams.
+- Microsoft Teams is plugin-only as of 2026.1.15; install `@poolbot/msteams` if you use Teams.
 - Memory (Core) — bundled memory search plugin (enabled by default via `plugins.slots.memory`)
 - Memory (LanceDB) — bundled long-term memory plugin (auto-recall/capture; set `plugins.slots.memory = "memory-lancedb"`)
-- [Voice Call](/plugins/voice-call) — `@clawdbot/voice-call`
-- [Zalo Personal](/plugins/zalouser) — `@clawdbot/zalouser`
-- [Matrix](/channels/matrix) — `@clawdbot/matrix`
-- [Nostr](/channels/nostr) — `@clawdbot/nostr`
-- [Zalo](/channels/zalo) — `@clawdbot/zalo`
-- [Microsoft Teams](/channels/msteams) — `@clawdbot/msteams`
+- [Voice Call](/plugins/voice-call) — `@poolbot/voice-call`
+- [Zalo Personal](/plugins/zalouser) — `@poolbot/zalouser`
+- [Matrix](/channels/matrix) — `@poolbot/matrix`
+- [Nostr](/channels/nostr) — `@poolbot/nostr`
+- [Zalo](/channels/zalo) — `@poolbot/zalo`
+- [Microsoft Teams](/channels/msteams) — `@poolbot/msteams`
 - Google Antigravity OAuth (provider auth) — bundled as `google-antigravity-auth` (disabled by default)
 - Gemini CLI OAuth (provider auth) — bundled as `google-gemini-cli-auth` (disabled by default)
 - Qwen OAuth (provider auth) — bundled as `qwen-portal-auth` (disabled by default)
 - Copilot Proxy (provider auth) — local VS Code Copilot Proxy bridge; distinct from built-in `github-copilot` device login (bundled, disabled by default)
 
-Clawdbot plugins are **TypeScript modules** loaded at runtime via jiti. **Config
+Pool Bot plugins are **TypeScript modules** loaded at runtime via jiti. **Config
 validation does not execute plugin code**; it uses the plugin manifest and JSON
 Schema instead. See [Plugin manifest](/plugins/manifest).
 
@@ -73,7 +73,7 @@ Plugins can access selected core helpers via `api.runtime`. For telephony TTS:
 
 ```ts
 const result = await api.runtime.tts.textToSpeechTelephony({
-  text: "Hello from Clawdbot",
+  text: "Hello from Pool Bot",
   cfg: api.config,
 });
 ```
@@ -85,27 +85,27 @@ Notes:
 
 ## Discovery & precedence
 
-Clawdbot scans, in order:
+Pool Bot scans, in order:
 
 1) Config paths
 - `plugins.load.paths` (file or directory)
 
 2) Workspace extensions
-- `<workspace>/.clawdbot/extensions/*.ts`
-- `<workspace>/.clawdbot/extensions/*/index.ts`
+- `<workspace>/.poolbot/extensions/*.ts`
+- `<workspace>/.poolbot/extensions/*/index.ts`
 
 3) Global extensions
-- `~/.clawdbot/extensions/*.ts`
-- `~/.clawdbot/extensions/*/index.ts`
+- `~/.poolbot/extensions/*.ts`
+- `~/.poolbot/extensions/*/index.ts`
 
-4) Bundled extensions (shipped with Clawdbot, **disabled by default**)
-- `<clawdbot>/extensions/*`
+4) Bundled extensions (shipped with Pool Bot, **disabled by default**)
+- `<poolbot>/extensions/*`
 
 Bundled plugins must be enabled explicitly via `plugins.entries.<id>.enabled`
-or `clawdbot plugins enable <id>`. Installed plugins are enabled by default,
+or `poolbot plugins enable <id>`. Installed plugins are enabled by default,
 but can be disabled the same way.
 
-Each plugin must include a `clawdbot.plugin.json` file in its root. If a path
+Each plugin must include a `poolbot.plugin.json` file in its root. If a path
 points at a file, the plugin root is the file's directory and must contain the
 manifest.
 
@@ -114,12 +114,12 @@ wins and lower-precedence copies are ignored.
 
 ### Package packs
 
-A plugin directory may include a `package.json` with `clawdbot.extensions`:
+A plugin directory may include a `package.json` with `poolbot.extensions`:
 
 ```json
 {
   "name": "my-pack",
-  "clawdbot": {
+  "poolbot": {
     "extensions": ["./src/safety.ts", "./src/tools.ts"]
   }
 }
@@ -133,15 +133,15 @@ If your plugin imports npm deps, install them in that directory so
 
 ### Channel catalog metadata
 
-Channel plugins can advertise onboarding metadata via `clawdbot.channel` and
-install hints via `clawdbot.install`. This keeps the core catalog data-free.
+Channel plugins can advertise onboarding metadata via `poolbot.channel` and
+install hints via `poolbot.install`. This keeps the core catalog data-free.
 
 Example:
 
 ```json
 {
-  "name": "@clawdbot/nextcloud-talk",
-  "clawdbot": {
+  "name": "@poolbot/nextcloud-talk",
+  "poolbot": {
     "extensions": ["./index.ts"],
     "channel": {
       "id": "nextcloud-talk",
@@ -154,7 +154,7 @@ Example:
       "aliases": ["nc-talk", "nc"]
     },
     "install": {
-      "npmSpec": "@clawdbot/nextcloud-talk",
+      "npmSpec": "@poolbot/nextcloud-talk",
       "localPath": "extensions/nextcloud-talk",
       "defaultChoice": "npm"
     }
@@ -162,15 +162,15 @@ Example:
 }
 ```
 
-Clawdbot can also merge **external channel catalogs** (for example, an MPM
+Pool Bot can also merge **external channel catalogs** (for example, an MPM
 registry export). Drop a JSON file at one of:
-- `~/.clawdbot/mpm/plugins.json`
-- `~/.clawdbot/mpm/catalog.json`
-- `~/.clawdbot/plugins/catalog.json`
+- `~/.poolbot/mpm/plugins.json`
+- `~/.poolbot/mpm/catalog.json`
+- `~/.poolbot/plugins/catalog.json`
 
 Or point `CLAWDBOT_PLUGIN_CATALOG_PATHS` (or `CLAWDBOT_MPM_CATALOG_PATHS`) at
 one or more JSON files (comma/semicolon/`PATH`-delimited). Each file should
-contain `{ "entries": [ { "name": "@scope/pkg", "clawdbot": { "channel": {...}, "install": {...} } } ] }`.
+contain `{ "entries": [ { "name": "@scope/pkg", "poolbot": { "channel": {...}, "install": {...} } } ] }`.
 
 ## Plugin IDs
 
@@ -179,7 +179,7 @@ Default plugin ids:
 - Package packs: `package.json` `name`
 - Standalone file: file base name (`~/.../voice-call.ts` → `voice-call`)
 
-If a plugin exports `id`, Clawdbot uses it but warns when it doesn’t match the
+If a plugin exports `id`, Pool Bot uses it but warns when it doesn’t match the
 configured id.
 
 ## Config
@@ -212,7 +212,7 @@ Validation rules (strict):
 - Unknown `channels.<id>` keys are **errors** unless a plugin manifest declares
   the channel id.
 - Plugin config is validated using the JSON Schema embedded in
-  `clawdbot.plugin.json` (`configSchema`).
+  `poolbot.plugin.json` (`configSchema`).
 - If a plugin is disabled, its config is preserved and a **warning** is emitted.
 
 ## Plugin slots (exclusive categories)
@@ -237,7 +237,7 @@ are disabled with diagnostics.
 
 The Control UI uses `config.schema` (JSON Schema + `uiHints`) to render better forms.
 
-Clawdbot augments `uiHints` at runtime based on discovered plugins:
+Pool Bot augments `uiHints` at runtime based on discovered plugins:
 
 - Adds per-plugin labels for `plugins.entries.<id>` / `.enabled` / `.config`
 - Merges optional plugin-provided config field hints under:
@@ -269,24 +269,24 @@ Example:
 ## CLI
 
 ```bash
-clawdbot plugins list
-clawdbot plugins info <id>
-clawdbot plugins install <path>                 # copy a local file/dir into ~/.clawdbot/extensions/<id>
-clawdbot plugins install ./extensions/voice-call # relative path ok
-clawdbot plugins install ./plugin.tgz           # install from a local tarball
-clawdbot plugins install ./plugin.zip           # install from a local zip
-clawdbot plugins install -l ./extensions/voice-call # link (no copy) for dev
-clawdbot plugins install @clawdbot/voice-call # install from npm
-clawdbot plugins update <id>
-clawdbot plugins update --all
-clawdbot plugins enable <id>
-clawdbot plugins disable <id>
-clawdbot plugins doctor
+poolbot plugins list
+poolbot plugins info <id>
+poolbot plugins install <path>                 # copy a local file/dir into ~/.poolbot/extensions/<id>
+poolbot plugins install ./extensions/voice-call # relative path ok
+poolbot plugins install ./plugin.tgz           # install from a local tarball
+poolbot plugins install ./plugin.zip           # install from a local zip
+poolbot plugins install -l ./extensions/voice-call # link (no copy) for dev
+poolbot plugins install @poolbot/voice-call # install from npm
+poolbot plugins update <id>
+poolbot plugins update --all
+poolbot plugins enable <id>
+poolbot plugins disable <id>
+poolbot plugins doctor
 ```
 
 `plugins update` only works for npm installs tracked under `plugins.installs`.
 
-Plugins may also register their own top‑level commands (example: `clawdbot voicecall`).
+Plugins may also register their own top‑level commands (example: `poolbot voicecall`).
 
 ## Plugin API (overview)
 
@@ -303,7 +303,7 @@ event-driven automation without a separate hook pack install.
 ### Example
 
 ```
-import { registerPluginHooksFromDir } from "clawdbot/plugin-sdk";
+import { registerPluginHooksFromDir } from "poolbot/plugin-sdk";
 
 export default function register(api) {
   registerPluginHooksFromDir(api, "./hooks");
@@ -313,18 +313,18 @@ export default function register(api) {
 Notes:
 - Hook directories follow the normal hook structure (`HOOK.md` + `handler.ts`).
 - Hook eligibility rules still apply (OS/bins/env/config requirements).
-- Plugin-managed hooks show up in `clawdbot hooks list` with `plugin:<id>`.
-- You cannot enable/disable plugin-managed hooks via `clawdbot hooks`; enable/disable the plugin instead.
+- Plugin-managed hooks show up in `poolbot hooks list` with `plugin:<id>`.
+- You cannot enable/disable plugin-managed hooks via `poolbot hooks`; enable/disable the plugin instead.
 
 ## Provider plugins (model auth)
 
 Plugins can register **model provider auth** flows so users can run OAuth or
-API-key setup inside Clawdbot (no external scripts needed).
+API-key setup inside Pool Bot (no external scripts needed).
 
 Register a provider via `api.registerProvider(...)`. Each provider exposes one
 or more auth methods (OAuth, API key, device code, etc.). These methods power:
 
-- `clawdbot models auth login --provider <id> [--method <id>]`
+- `poolbot models auth login --provider <id> [--method <id>]`
 
 Example:
 
@@ -536,7 +536,7 @@ Command handler context:
 - `isAuthorizedSender`: Whether the sender is an authorized user
 - `args`: Arguments passed after the command (if `acceptsArgs: true`)
 - `commandBody`: The full command text
-- `config`: The current Clawdbot config
+- `config`: The current Pool Bot config
 
 Command options:
 
@@ -598,14 +598,14 @@ it’s present in your workspace/managed skills locations.
 
 Recommended packaging:
 
-- Main package: `clawdbot` (this repo)
-- Plugins: separate npm packages under `@clawdbot/*` (example: `@clawdbot/voice-call`)
+- Main package: `poolbot` (this repo)
+- Plugins: separate npm packages under `@poolbot/*` (example: `@poolbot/voice-call`)
 
 Publishing contract:
 
-- Plugin `package.json` must include `clawdbot.extensions` with one or more entry files.
+- Plugin `package.json` must include `poolbot.extensions` with one or more entry files.
 - Entry files can be `.js` or `.ts` (jiti loads TS at runtime).
-- `clawdbot plugins install <npm-spec>` uses `npm pack`, extracts into `~/.clawdbot/extensions/<id>/`, and enables it in config.
+- `poolbot plugins install <npm-spec>` uses `npm pack`, extracts into `~/.poolbot/extensions/<id>/`, and enables it in config.
 - Config key stability: scoped packages are normalized to the **unscoped** id for `plugins.entries.*`.
 
 ## Example plugin: Voice Call
@@ -614,7 +614,7 @@ This repo includes a voice‑call plugin (Twilio or log fallback):
 
 - Source: `extensions/voice-call`
 - Skill: `skills/voice-call`
-- CLI: `clawdbot voicecall start|status`
+- CLI: `poolbot voicecall start|status`
 - Tool: `voice_call`
 - RPC: `voicecall.start`, `voicecall.status`
 - Config (twilio): `provider: "twilio"` + `twilio.accountSid/authToken/from` (optional `statusCallbackUrl`, `twimlUrl`)
@@ -635,4 +635,4 @@ Plugins run in-process with the Gateway. Treat them as trusted code:
 Plugins can (and should) ship tests:
 
 - In-repo plugins can keep Vitest tests under `src/**` (example: `src/plugins/voice-call.plugin.test.ts`).
-- Separately published plugins should run their own CI (lint/build/test) and validate `clawdbot.extensions` points at the built entrypoint (`dist/index.js`).
+- Separately published plugins should run their own CI (lint/build/test) and validate `poolbot.extensions` points at the built entrypoint (`dist/index.js`).

package/docs/plugins/agent-tools.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Plugin agent tools
 
-Clawdbot plugins can register **agent tools** (JSON‑schema functions) that are exposed
+Pool Bot plugins can register **agent tools** (JSON‑schema functions) that are exposed
 to the LLM during agent runs. Tools can be **required** (always available) or
 **optional** (opt‑in).
 

package/docs/plugins/manifest.md

@@ -1,13 +1,13 @@
 ---
 summary: "Plugin manifest + JSON schema requirements (strict config validation)"
 read_when:
-  - You are building a Clawdbot plugin
+  - You are building a Pool Bot plugin
   - You need to ship a plugin config schema or debug plugin validation errors
 ---
-# Plugin manifest (clawdbot.plugin.json)
+# Plugin manifest (poolbot.plugin.json)
 
-Every plugin **must** ship a `clawdbot.plugin.json` file in the **plugin root**.
-Clawdbot uses this manifest to validate configuration **without executing plugin
+Every plugin **must** ship a `poolbot.plugin.json` file in the **plugin root**.
+Pool Bot uses this manifest to validate configuration **without executing plugin
 code**. Missing or invalid manifests are treated as plugin errors and block
 config validation.
 

package/docs/plugins/voice-call.md

@@ -1,13 +1,13 @@
 ---
 summary: "Voice Call plugin: outbound + inbound calls via Twilio/Telnyx/Plivo (plugin install + config + CLI)"
 read_when:
-  - You want to place an outbound voice call from Clawdbot
+  - You want to place an outbound voice call from Pool Bot
   - You are configuring or developing the voice-call plugin
 ---
 
 # Voice Call (plugin)
 
-Voice calls for Clawdbot via a plugin. Supports outbound notifications and
+Voice calls for Pool Bot via a plugin. Supports outbound notifications and
 multi-turn conversations with inbound policies.
 
 Current providers:
@@ -20,7 +20,7 @@ Quick mental model:
 - Install plugin
 - Restart Gateway
 - Configure under `plugins.entries.voice-call.config`
-- Use `clawdbot voicecall ...` or the `voice_call` tool
+- Use `poolbot voicecall ...` or the `voice_call` tool
 
 ## Where it runs (local vs remote)
 
@@ -33,7 +33,7 @@ If you use a remote Gateway, install/configure the plugin on the **machine runni
 ### Option A: install from npm (recommended)
 
 ```bash
-clawdbot plugins install @clawdbot/voice-call
+poolbot plugins install @poolbot/voice-call
 ```
 
 Restart the Gateway afterwards.
@@ -41,7 +41,7 @@ Restart the Gateway afterwards.
 ### Option B: install from a local folder (dev, no copying)
 
 ```bash
-clawdbot plugins install ./extensions/voice-call
+poolbot plugins install ./extensions/voice-call
 cd ./extensions/voice-call && pnpm install
 ```
 
@@ -103,6 +103,9 @@ Notes:
 - Plivo requires a **publicly reachable** webhook URL.
 - `mock` is a local dev provider (no network calls).
 - `skipSignatureVerification` is for local testing only.
+- If you use ngrok free tier, set `publicUrl` to the exact ngrok URL; signature verification is always enforced.
+- `tunnel.allowNgrokFreeTierLoopbackBypass: true` allows Twilio webhooks with invalid signatures **only** when `tunnel.provider="ngrok"` and `serve.bind` is loopback (ngrok local agent). Use for local dev only.
+- Ngrok free tier URLs can change or add interstitial behavior; if `publicUrl` drifts, Twilio signatures will fail. For production, prefer a stable domain or Tailscale funnel.
 
 ## TTS for calls
 
@@ -205,13 +208,13 @@ Auto-responses use the agent system. Tune with:
 ## CLI
 
 ```bash
-clawdbot voicecall call --to "+15555550123" --message "Hello from Clawdbot"
-clawdbot voicecall continue --call-id <id> --message "Any questions?"
-clawdbot voicecall speak --call-id <id> --message "One moment"
-clawdbot voicecall end --call-id <id>
-clawdbot voicecall status --call-id <id>
-clawdbot voicecall tail
-clawdbot voicecall expose --mode funnel
+poolbot voicecall call --to "+15555550123" --message "Hello from Pool Bot"
+poolbot voicecall continue --call-id <id> --message "Any questions?"
+poolbot voicecall speak --call-id <id> --message "One moment"
+poolbot voicecall end --call-id <id>
+poolbot voicecall status --call-id <id>
+poolbot voicecall tail
+poolbot voicecall expose --mode funnel
 ```
 
 ## Agent tool

package/docs/plugins/zalouser.md

@@ -1,13 +1,13 @@
 ---
 summary: "Zalo Personal plugin: QR login + messaging via zca-cli (plugin install + channel config + CLI + tool)"
 read_when:
-  - You want Zalo Personal (unofficial) support in Clawdbot
+  - You want Zalo Personal (unofficial) support in Pool Bot
   - You are configuring or developing the zalouser plugin
 ---
 
 # Zalo Personal (plugin)
 
-Zalo Personal support for Clawdbot via a plugin, using `zca-cli` to automate a normal Zalo user account.
+Zalo Personal support for Pool Bot via a plugin, using `zca-cli` to automate a normal Zalo user account.
 
 > **Warning:** Unofficial automation may lead to account suspension/ban. Use at your own risk.
 
@@ -24,7 +24,7 @@ If you use a remote Gateway, install/configure it on the **machine running the G
 ### Option A: install from npm
 
 ```bash
-clawdbot plugins install @clawdbot/zalouser
+poolbot plugins install @poolbot/zalouser
 ```
 
 Restart the Gateway afterwards.
@@ -32,7 +32,7 @@ Restart the Gateway afterwards.
 ### Option B: install from a local folder (dev)
 
 ```bash
-clawdbot plugins install ./extensions/zalouser
+poolbot plugins install ./extensions/zalouser
 cd ./extensions/zalouser && pnpm install
 ```
 
@@ -62,11 +62,11 @@ Channel config lives under `channels.zalouser` (not `plugins.entries.*`):
 ## CLI
 
 ```bash
-clawdbot channels login --channel zalouser
-clawdbot channels logout --channel zalouser
-clawdbot channels status --probe
-clawdbot message send --channel zalouser --target <threadId> --message "Hello from Clawdbot"
-clawdbot directory peers list --channel zalouser --query "name"
+poolbot channels login --channel zalouser
+poolbot channels logout --channel zalouser
+poolbot channels status --probe
+poolbot message send --channel zalouser --target <threadId> --message "Hello from Pool Bot"
+poolbot directory peers list --channel zalouser --query "name"
 ```
 
 ## Agent tool

package/docs/prose.md

@@ -1,5 +1,5 @@
 ---
-summary: "OpenProse: .prose workflows, slash commands, and state in Clawdbot"
+summary: "OpenProse: .prose workflows, slash commands, and state in Pool Bot"
 read_when:
   - You want to run or write .prose workflows
   - You want to enable the OpenProse plugin
@@ -7,7 +7,7 @@ read_when:
 ---
 # OpenProse
 
-OpenProse is a portable, markdown-first workflow format for orchestrating AI sessions. In Clawdbot it ships as a plugin that installs an OpenProse skill pack plus a `/prose` slash command. Programs live in `.prose` files and can spawn multiple sub-agents with explicit control flow.
+OpenProse is a portable, markdown-first workflow format for orchestrating AI sessions. In Pool Bot it ships as a plugin that installs an OpenProse skill pack plus a `/prose` slash command. Programs live in `.prose` files and can spawn multiple sub-agents with explicit control flow.
 
 Official site: https://www.prose.md
 
@@ -22,18 +22,18 @@ Official site: https://www.prose.md
 Bundled plugins are disabled by default. Enable OpenProse:
 
 ```bash
-clawdbot plugins enable open-prose
+poolbot plugins enable open-prose
 ```
 
 Restart the Gateway after enabling the plugin.
 
-Dev/local checkout: `clawdbot plugins install ./extensions/open-prose`
+Dev/local checkout: `poolbot plugins install ./extensions/open-prose`
 
 Related docs: [Plugins](/plugin), [Plugin manifest](/plugins/manifest), [Skills](/tools/skills).
 
 ## Slash command
 
-OpenProse registers `/prose` as a user-invocable skill command. It routes to the OpenProse VM instructions and uses Clawdbot tools under the hood.
+OpenProse registers `/prose` as a user-invocable skill command. It routes to the OpenProse VM instructions and uses Pool Bot tools under the hood.
 
 Common commands:
 
@@ -112,11 +112,11 @@ Notes:
 `/prose run <handle/slug>` resolves to `https://p.prose.md/<handle>/<slug>`.
 Direct URLs are fetched as-is. This uses the `web_fetch` tool (or `exec` for POST).
 
-## Clawdbot runtime mapping
+## Pool Bot runtime mapping
 
-OpenProse programs map to Clawdbot primitives:
+OpenProse programs map to Pool Bot primitives:
 
-| OpenProse concept | Clawdbot tool |
+| OpenProse concept | Pool Bot tool |
 | --- | --- |
 | Spawn session / Task tool | `sessions_spawn` |
 | File read/write | `read` / `write` |
@@ -126,6 +126,6 @@ If your tool allowlist blocks these tools, OpenProse programs will fail. See [Sk
 
 ## Security + approvals
 
-Treat `.prose` files like code. Review before running. Use Clawdbot tool allowlists and approval gates to control side effects.
+Treat `.prose` files like code. Review before running. Use Pool Bot tool allowlists and approval gates to control side effects.
 
 For deterministic, approval-gated workflows, compare with [Lobster](/tools/lobster).

package/docs/providers/anthropic.md

@@ -1,14 +1,13 @@
 ---
-summary: "Use Anthropic Claude via API keys or Claude Code CLI auth in Clawdbot"
+summary: "Use Anthropic Claude via API keys or setup-token in Pool Bot"
 read_when:
-  - You want to use Anthropic models in Clawdbot
-  - You want setup-token or Claude Code CLI auth instead of API keys
+  - You want to use Anthropic models in Pool Bot
+  - You want setup-token instead of API keys
 ---
 # Anthropic (Claude)
 
 Anthropic builds the **Claude** model family and provides access via an API.
-In Clawdbot you can authenticate with an API key or reuse **Claude Code CLI** credentials
-(setup-token or OAuth).
+In Pool Bot you can authenticate with an API key or a **setup-token**.
 
 ## Option A: Anthropic API key
 
@@ -18,11 +17,11 @@ Create your API key in the Anthropic Console.
 ### CLI setup
 
 ```bash
-clawdbot onboard
+poolbot onboard
 # choose: Anthropic API key
 
 # or non-interactive
-clawdbot onboard --anthropic-api-key "$ANTHROPIC_API_KEY"
+poolbot onboard --anthropic-api-key "$ANTHROPIC_API_KEY"
 ```
 
 ### Config snippet
@@ -36,8 +35,8 @@ clawdbot onboard --anthropic-api-key "$ANTHROPIC_API_KEY"
 
 ## Prompt caching (Anthropic API)
 
-Clawdbot does **not** override Anthropic’s default cache TTL unless you set it.
-This is **API-only**; Claude Code CLI OAuth ignores TTL settings.
+Pool Bot does **not** override Anthropic’s default cache TTL unless you set it.
+This is **API-only**; subscription auth does not honor TTL settings.
 
 To set the TTL per model, use `cacheControlTtl` in the model `params`:
 
@@ -55,12 +54,12 @@ To set the TTL per model, use `cacheControlTtl` in the model `params`:
 }
 ```
 
-Clawdbot includes the `extended-cache-ttl-2025-04-11` beta flag for Anthropic API
+Pool Bot includes the `extended-cache-ttl-2025-04-11` beta flag for Anthropic API
 requests; keep it if you override provider headers (see [/gateway/configuration](/gateway/configuration)).
 
-## Option B: Claude Code CLI (setup-token or OAuth)
+## Option B: Claude setup-token
 
-**Best for:** using your Claude subscription or existing Claude Code CLI login.
+**Best for:** using your Claude subscription.
 
 ### Where to get a setup-token
 
@@ -70,23 +69,23 @@ Setup-tokens are created by the **Claude Code CLI**, not the Anthropic Console.
 claude setup-token
 ```
 
-Paste the token into Clawdbot (wizard: **Anthropic token (paste setup-token)**), or run it on the gateway host:
+Paste the token into Pool Bot (wizard: **Anthropic token (paste setup-token)**), or run it on the gateway host:
 
 ```bash
-clawdbot models auth setup-token --provider anthropic
+poolbot models auth setup-token --provider anthropic
 ```
 
 If you generated the token on a different machine, paste it:
 
 ```bash
-clawdbot models auth paste-token --provider anthropic
+poolbot models auth paste-token --provider anthropic
 ```
 
 ### CLI setup
 
 ```bash
-# Reuse Claude Code CLI OAuth credentials if already logged in
-clawdbot onboard --auth-choice claude-cli
+# Paste a setup-token during onboarding
+poolbot onboard --auth-choice setup-token
 ```
 
 ### Config snippet
@@ -99,11 +98,8 @@ clawdbot onboard --auth-choice claude-cli
 
 ## Notes
 
-- Generate the setup-token with `claude setup-token` and paste it, or run `clawdbot models auth setup-token` on the gateway host.
-- If you see “OAuth token refresh failed …” on a Claude subscription, re-auth with a setup-token or resync Claude Code CLI OAuth on the gateway host. See [/gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription](/gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription).
-- Clawdbot writes `auth.profiles["anthropic:claude-cli"].mode` as `"oauth"` so the profile
-  accepts both OAuth and setup-token credentials. Older configs using `"token"` are
-  auto-migrated on load.
+- Generate the setup-token with `claude setup-token` and paste it, or run `poolbot models auth setup-token` on the gateway host.
+- If you see “OAuth token refresh failed …” on a Claude subscription, re-auth with a setup-token. See [/gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription](/gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription).
 - Auth details + reuse rules are in [/concepts/oauth](/concepts/oauth).
 
 ## Troubleshooting
@@ -112,19 +108,19 @@ clawdbot onboard --auth-choice claude-cli
 - Claude subscription auth can expire or be revoked. Re-run `claude setup-token`
   and paste it into the **gateway host**.
 - If the Claude CLI login lives on a different machine, use
-  `clawdbot models auth paste-token --provider anthropic` on the gateway host.
+  `poolbot models auth paste-token --provider anthropic` on the gateway host.
 
 **No API key found for provider "anthropic"**
 - Auth is **per agent**. New agents don’t inherit the main agent’s keys.
 - Re-run onboarding for that agent, or paste a setup-token / API key on the
-  gateway host, then verify with `clawdbot models status`.
+  gateway host, then verify with `poolbot models status`.
 
-**No credentials found for profile `anthropic:default` or `anthropic:claude-cli`**
-- Run `clawdbot models status` to see which auth profile is active.
+**No credentials found for profile `anthropic:default`**
+- Run `poolbot models status` to see which auth profile is active.
 - Re-run onboarding, or paste a setup-token / API key for that profile.
 
 **No available auth profile (all in cooldown/unavailable)**
-- Check `clawdbot models status --json` for `auth.unusableProfiles`.
+- Check `poolbot models status --json` for `auth.unusableProfiles`.
 - Add another Anthropic profile or wait for cooldown.
 
 More: [/gateway/troubleshooting](/gateway/troubleshooting) and [/help/faq](/help/faq).