@poolzin/pool-bot 1.28.0 → 2026.1.26

package/docs/concepts/agent-workspace.md

@@ -24,7 +24,7 @@ inside a sandbox workspace under `~/.clawdbot/sandboxes`, not your host workspac
 - Default: `~/clawd`
 - If `CLAWDBOT_PROFILE` is set and not `"default"`, the default becomes
   `~/clawd-<profile>`.
-- Override in `~/.clawdbot/moltbot.json`:
+- Override in `~/.clawdbot/clawdbot.json`:
 
 ```json5
 {
@@ -34,7 +34,7 @@ inside a sandbox workspace under `~/.clawdbot/sandboxes`, not your host workspac
 }
 ```
 
-`moltbot onboard`, `moltbot configure`, or `moltbot setup` will create the
+`clawdbot onboard`, `clawdbot configure`, or `clawdbot setup` will create the
 workspace and seed the bootstrap files if they are missing.
 
 If you already manage the workspace files yourself, you can disable bootstrap
@@ -46,20 +46,20 @@ file creation:
 
 ## Extra workspace folders
 
-Older installs may have created `~/moltbot`. Keeping multiple workspace
+Older installs may have created `~/clawdbot`. Keeping multiple workspace
 directories around can cause confusing auth or state drift, because only one
 workspace is active at a time.
 
 **Recommendation:** keep a single active workspace. If you no longer use the
-extra folders, archive or move them to Trash (for example `trash ~/moltbot`).
+extra folders, archive or move them to Trash (for example `trash ~/clawdbot`).
 If you intentionally keep multiple workspaces, make sure
 `agents.defaults.workspace` points to the active one.
 
-`moltbot doctor` warns when it detects extra workspace directories.
+`clawdbot doctor` warns when it detects extra workspace directories.
 
 ## Workspace file map (what each file means)
 
-These are the standard files Pool Bot expects inside the workspace:
+These are the standard files Clawdbot expects inside the workspace:
 
 - `AGENTS.md`
   - Operating instructions for the agent and how it should use memory.
@@ -112,17 +112,17 @@ See [Memory](/concepts/memory) for the workflow and automatic memory flush.
 - `canvas/` (optional)
   - Canvas UI files for node displays (for example `canvas/index.html`).
 
-If any bootstrap file is missing, Pool Bot injects a "missing file" marker into
+If any bootstrap file is missing, Clawdbot injects a "missing file" marker into
 the session and continues. Large bootstrap files are truncated when injected;
 adjust the limit with `agents.defaults.bootstrapMaxChars` (default: 20000).
-`moltbot setup` can recreate missing defaults without overwriting existing
+`clawdbot setup` can recreate missing defaults without overwriting existing
 files.
 
 ## What is NOT in the workspace
 
 These live under `~/.clawdbot/` and should NOT be committed to the workspace repo:
 
-- `~/.clawdbot/moltbot.json` (config)
+- `~/.clawdbot/clawdbot.json` (config)
 - `~/.clawdbot/credentials/` (OAuth tokens, API keys)
 - `~/.clawdbot/agents/<agentId>/sessions/` (session transcripts + metadata)
 - `~/.clawdbot/skills/` (managed skills)
@@ -218,8 +218,8 @@ Suggested `.gitignore` starter:
 ## Moving the workspace to a new machine
 
 1. Clone the repo to the desired path (default `~/clawd`).
-2. Set `agents.defaults.workspace` to that path in `~/.clawdbot/moltbot.json`.
-3. Run `moltbot setup --workspace <path>` to seed any missing files.
+2. Set `agents.defaults.workspace` to that path in `~/.clawdbot/clawdbot.json`.
+3. Run `clawdbot setup --workspace <path>` to seed any missing files.
 4. If you need sessions, copy `~/.clawdbot/agents/<agentId>/sessions/` from the
    old machine separately.
 

package/docs/concepts/agent.md

@@ -5,13 +5,13 @@ read_when:
 ---
 # Agent Runtime 🤖
 
-Pool Bot runs a single embedded agent runtime derived from **p-mono**.
+Clawdbot runs a single embedded agent runtime derived from **p-mono**.
 
 ## Workspace (required)
 
-Pool Bot uses a single agent workspace directory (`agents.defaults.workspace`) as the agent’s **only** working directory (`cwd`) for tools and context.
+Clawdbot uses a single agent workspace directory (`agents.defaults.workspace`) as the agent’s **only** working directory (`cwd`) for tools and context.
 
-Recommended: use `moltbot setup` to create `~/.clawdbot/moltbot.json` if missing and initialize the workspace files.
+Recommended: use `clawdbot setup` to create `~/.clawdbot/clawdbot.json` if missing and initialize the workspace files.
 
 Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)
 
@@ -21,7 +21,7 @@ per-session workspaces under `agents.defaults.sandbox.workspaceRoot` (see
 
 ## Bootstrap files (injected)
 
-Inside `agents.defaults.workspace`, Pool Bot expects these user-editable files:
+Inside `agents.defaults.workspace`, Clawdbot expects these user-editable files:
 - `AGENTS.md` — operating instructions + “memory”
 - `SOUL.md` — persona, boundaries, tone
 - `TOOLS.md` — user-maintained tool notes (e.g. `imsg`, `sag`, conventions)
@@ -29,11 +29,11 @@ Inside `agents.defaults.workspace`, Pool Bot expects these user-editable files:
 - `IDENTITY.md` — agent name/vibe/emoji
 - `USER.md` — user profile + preferred address
 
-On the first turn of a new session, Pool Bot injects the contents of these files directly into the agent context.
+On the first turn of a new session, Clawdbot injects the contents of these files directly into the agent context.
 
 Blank files are skipped. Large files are trimmed and truncated with a marker so prompts stay lean (read the file for full content).
 
-If a file is missing, Pool Bot injects a single “missing file” marker line (and `moltbot setup` will create a safe default template).
+If a file is missing, Clawdbot injects a single “missing file” marker line (and `clawdbot setup` will create a safe default template).
 
 `BOOTSTRAP.md` is only created for a **brand new workspace** (no other bootstrap files present). If you delete it after completing the ritual, it should not be recreated on later restarts.
 
@@ -52,7 +52,7 @@ guidance for how *you* want them used.
 
 ## Skills
 
-Pool Bot loads skills from three locations (workspace wins on name conflict):
+Clawdbot loads skills from three locations (workspace wins on name conflict):
 - Bundled (shipped with the install)
 - Managed/local: `~/.clawdbot/skills`
 - Workspace: `<workspace>/skills`
@@ -61,7 +61,7 @@ Skills can be gated by config/env (see `skills` in [Gateway configuration](/gate
 
 ## p-mono integration
 
-Pool Bot reuses pieces of the p-mono codebase (models/tools), but **session management, discovery, and tool wiring are Pool Bot-owned**.
+Clawdbot reuses pieces of the p-mono codebase (models/tools), but **session management, discovery, and tool wiring are Clawdbot-owned**.
 
 - No p-coding agent runtime.
 - No `~/.pi/agent` or `<workspace>/.pi` settings are consulted.
@@ -71,7 +71,7 @@ Pool Bot reuses pieces of the p-mono codebase (models/tools), but **session mana
 Session transcripts are stored as JSONL at:
 - `~/.clawdbot/agents/<agentId>/sessions/<SessionId>.jsonl`
 
-The session ID is stable and chosen by Pool Bot.
+The session ID is stable and chosen by Clawdbot.
 Legacy Pi/Tau session folders are **not** read.
 
 ## Steering while streaming
@@ -104,7 +104,7 @@ Model refs in config (for example `agents.defaults.model` and `agents.defaults.m
 
 - Use `provider/model` when configuring models.
 - If the model ID itself contains `/` (OpenRouter-style), include the provider prefix (example: `openrouter/moonshotai/kimi-k2`).
-- If you omit the provider, Pool Bot treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
+- If you omit the provider, Clawdbot treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
 
 ## Configuration (minimal)
 

package/docs/concepts/architecture.md

@@ -111,7 +111,7 @@ Details: [Gateway protocol](/gateway/protocol), [Pairing](/start/pairing),
 
 ## Operations snapshot
 
-- Start: `moltbot gateway` (foreground, logs to stdout).
+- Start: `clawdbot gateway` (foreground, logs to stdout).
 - Health: `health` over WS (also included in `hello-ok`).
 - Supervision: launchd/systemd for auto‑restart.
 

package/docs/concepts/channel-routing.md

@@ -6,7 +6,7 @@ read_when:
 # Channels & routing
 
 
-Pool Bot routes replies **back to the channel where a message came from**. The
+Clawdbot routes replies **back to the channel where a message came from**. The
 model does not choose a channel; routing is deterministic and controlled by the
 host configuration.
 
@@ -53,7 +53,7 @@ The matched agent determines which workspace and session store are used.
 
 ## Broadcast groups (run multiple agents)
 
-Broadcast groups let you run **multiple agents** for the same peer **when Pool Bot would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
+Broadcast groups let you run **multiple agents** for the same peer **when Clawdbot would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
 
 Config:
 

package/docs/concepts/compaction.md

@@ -1,12 +1,12 @@
 ---
-summary: "Context window + compaction: how Pool Bot keeps sessions under model limits"
+summary: "Context window + compaction: how Clawdbot keeps sessions under model limits"
 read_when:
   - You want to understand auto-compaction and /compact
   - You are debugging long sessions hitting context limits
 ---
 # Context Window & Compaction
 
-Every model has a **context window** (max tokens it can see). Long-running chats accumulate messages and tool results; once the window is tight, Pool Bot **compacts** older history to stay within limits.
+Every model has a **context window** (max tokens it can see). Long-running chats accumulate messages and tool results; once the window is tight, Clawdbot **compacts** older history to stay within limits.
 
 ## What compaction is
 Compaction **summarizes older conversation** into a compact summary entry and keeps recent messages intact. The summary is stored in the session history, so future requests use:
@@ -19,13 +19,13 @@ Compaction **persists** in the session’s JSONL history.
 See [Compaction config & modes](/concepts/compaction) for the `agents.defaults.compaction` settings.
 
 ## Auto-compaction (default on)
-When a session nears or exceeds the model’s context window, Pool Bot triggers auto-compaction and may retry the original request using the compacted context.
+When a session nears or exceeds the model’s context window, Clawdbot triggers auto-compaction and may retry the original request using the compacted context.
 
 You’ll see:
 - `🧹 Auto-compaction complete` in verbose mode
 - `/status` showing `🧹 Compactions: <count>`
 
-Before compaction, Pool Bot can run a **silent memory flush** turn to store
+Before compaction, Clawdbot can run a **silent memory flush** turn to store
 durable notes to disk. See [Memory](/concepts/memory) for details and config.
 
 ## Manual compaction
@@ -35,7 +35,7 @@ Use `/compact` (optionally with instructions) to force a compaction pass:
 ```
 
 ## Context window source
-Context window is model-specific. Pool Bot uses the model definition from the configured provider catalog to determine limits.
+Context window is model-specific. Clawdbot uses the model definition from the configured provider catalog to determine limits.
 
 ## Compaction vs pruning
 - **Compaction**: summarises and **persists** in JSONL.

package/docs/concepts/context.md

@@ -1,16 +1,16 @@
 ---
 summary: "Context: what the model sees, how it is built, and how to inspect it"
 read_when:
-  - You want to understand what “context” means in Pool Bot
+  - You want to understand what “context” means in Clawdbot
   - You are debugging why the model “knows” something (or forgot it)
   - You want to reduce context overhead (/context, /status, /compact)
 ---
 # Context
 
-“Context” is **everything Pool Bot sends to the model for a run**. It is bounded by the model’s **context window** (token limit).
+“Context” is **everything Clawdbot sends to the model for a run**. It is bounded by the model’s **context window** (token limit).
 
 Beginner mental model:
-- **System prompt** (Pool Bot-built): rules, tools, skills list, time/runtime, and injected workspace files.
+- **System prompt** (Clawdbot-built): rules, tools, skills list, time/runtime, and injected workspace files.
 - **Conversation history**: your messages + the assistant’s messages for this session.
 - **Tool calls/results + attachments**: command output, file reads, images/audio, etc.
 
@@ -83,9 +83,9 @@ Everything the model receives counts, including:
 - Compaction summaries and pruning artifacts.
 - Provider “wrappers” or hidden headers (not visible, still counted).
 
-## How Pool Bot builds the system prompt
+## How Clawdbot builds the system prompt
 
-The system prompt is **Pool Bot-owned** and rebuilt each run. It includes:
+The system prompt is **Clawdbot-owned** and rebuilt each run. It includes:
 - Tool list + short descriptions.
 - Skills list (metadata only; see below).
 - Workspace location.
@@ -97,7 +97,7 @@ Full breakdown: [System Prompt](/concepts/system-prompt).
 
 ## Injected workspace files (Project Context)
 
-By default, Pool Bot injects a fixed set of workspace files (if present):
+By default, Clawdbot injects a fixed set of workspace files (if present):
 - `AGENTS.md`
 - `SOUL.md`
 - `TOOLS.md`

package/docs/concepts/group-messages.md

@@ -19,7 +19,7 @@ Note: `agents.list[].groupChat.mentionPatterns` is now used by Telegram/Discord/
 - Group system prompt: on the first turn of a group session (and whenever `/activation` changes the mode) we inject a short blurb into the system prompt like `You are replying inside the WhatsApp group "<subject>". Group members: Alice (+44...), Bob (+43...), … Activation: trigger-only … Address the specific sender noted in the message context.` If metadata isn’t available we still tell the agent it’s a group chat.
 
 ## Config example (WhatsApp)
-Add a `groupChat` block to `~/.clawdbot/moltbot.json` so display-name pings work even when WhatsApp strips the visual `@` in the text body:
+Add a `groupChat` block to `~/.clawdbot/clawdbot.json` so display-name pings work even when WhatsApp strips the visual `@` in the text body:
 
 ```json5
 {
@@ -37,7 +37,7 @@ Add a `groupChat` block to `~/.clawdbot/moltbot.json` so display-name pings work
         groupChat: {
           historyLimit: 50,
           mentionPatterns: [
-            "@?moltbot",
+            "@?clawdbot",
             "\\+?15555550123"
           ]
         }
@@ -48,7 +48,7 @@ Add a `groupChat` block to `~/.clawdbot/moltbot.json` so display-name pings work
 ```
 
 Notes:
-- The regexes are case-insensitive; they cover a display-name ping like `@moltbot` and the raw number with or without `+`/spaces.
+- The regexes are case-insensitive; they cover a display-name ping like `@clawdbot` and the raw number with or without `+`/spaces.
 - WhatsApp still sends canonical mentions via `mentionedJids` when someone taps the contact, so the number fallback is rarely needed but is a useful safety net.
 
 ### Activation command (owner-only)
@@ -60,8 +60,8 @@ Use the group chat command:
 Only the owner number (from `channels.whatsapp.allowFrom`, or the bot’s own E.164 when unset) can change this. Send `/status` as a standalone message in the group to see the current activation mode.
 
 ## How to use
-1) Add your WhatsApp account (the one running Pool Bot) to the group.
-2) Say `@moltbot …` (or include the number). Only allowlisted senders can trigger it unless you set `groupPolicy: "open"`.
+1) Add your WhatsApp account (the one running Clawdbot) to the group.
+2) Say `@clawdbot …` (or include the number). Only allowlisted senders can trigger it unless you set `groupPolicy: "open"`.
 3) The agent prompt will include recent group context plus the trailing `[from: …]` marker so it can address the right person.
 4) Session-level directives (`/verbose on`, `/think high`, `/new` or `/reset`, `/compact`) apply only to that group’s session; send them as standalone messages so they register. Your personal DM session remains independent.
 

package/docs/concepts/groups.md

@@ -5,17 +5,17 @@ read_when:
 ---
 # Groups
 
-Pool Bot treats group chats consistently across surfaces: WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Microsoft Teams.
+Clawdbot treats group chats consistently across surfaces: WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Microsoft Teams.
 
 ## Beginner intro (2 minutes)
-Pool Bot “lives” on your own messaging accounts. There is no separate WhatsApp bot user.
-If **you** are in a group, Pool Bot can see that group and respond there.
+Clawdbot “lives” on your own messaging accounts. There is no separate WhatsApp bot user.
+If **you** are in a group, Clawdbot can see that group and respond there.
 
 Default behavior:
 - Groups are restricted (`groupPolicy: "allowlist"`).
 - Replies require a mention unless you explicitly disable mention gating.
 
-Translation: allowlisted senders can trigger Pool Bot by mentioning it.
+Translation: allowlisted senders can trigger Clawdbot by mentioning it.
 
 > TL;DR
 > - **DM access** is controlled by `*.allowFrom`.
@@ -215,7 +215,7 @@ Replying to a bot message counts as an implicit mention (when the channel suppor
       {
         id: "main",
         groupChat: {
-          mentionPatterns: ["@clawd", "moltbot", "\\+15555550123"],
+          mentionPatterns: ["@clawd", "clawdbot", "\\+15555550123"],
           historyLimit: 50
         }
       }
@@ -232,42 +232,6 @@ Notes:
 - Discord defaults live in `channels.discord.guilds."*"` (overridable per guild/channel).
 - Group history context is wrapped uniformly across channels and is **pending-only** (messages skipped due to mention gating); use `messages.groupChat.historyLimit` for the global default and `channels.<channel>.historyLimit` (or `channels.<channel>.accounts.*.historyLimit`) for overrides. Set `0` to disable.
 
-## Group/channel tool restrictions (optional)
-Some channel configs support restricting which tools are available **inside a specific group/room/channel**.
-
-- `tools`: allow/deny tools for the whole group.
-- `toolsBySender`: per-sender overrides within the group (keys are sender IDs/usernames/emails/phone numbers depending on the channel). Use `"*"` as a wildcard.
-
-Resolution order (most specific wins):
-1) group/channel `toolsBySender` match
-2) group/channel `tools`
-3) default (`"*"`) `toolsBySender` match
-4) default (`"*"`) `tools`
-
-Example (Telegram):
-
-```json5
-{
-  channels: {
-    telegram: {
-      groups: {
-        "*": { tools: { deny: ["exec"] } },
-        "-1001234567890": {
-          tools: { deny: ["exec", "read", "write"] },
-          toolsBySender: {
-            "123456789": { alsoAllow: ["exec"] }
-          }
-        }
-      }
-    }
-  }
-}
-```
-
-Notes:
-- Group/channel tool restrictions are applied in addition to global/agent tool policy (deny still wins).
-- Some channels use different nesting for rooms/channels (e.g., Discord `guilds.*.channels.*`, Slack `channels.*`, MS Teams `teams.*.channels.*`).
-
 ## Group allowlists
 When `channels.whatsapp.groups`, `channels.telegram.groups`, or `channels.imessage.groups` is configured, the keys act as a group allowlist. Use `"*"` to allow all groups while still setting default mention behavior.
 

package/docs/concepts/markdown-formatting.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Markdown formatting
 
-Pool Bot formats outbound Markdown by converting it into a shared intermediate
+Clawdbot formats outbound Markdown by converting it into a shared intermediate
 representation (IR) before rendering channel-specific output. The IR keeps the
 source text intact while carrying style/link spans so chunking and rendering can
 stay consistent across channels.
@@ -39,7 +39,7 @@ stay consistent across channels.
 Input Markdown:
 
 ```markdown
-Hello **world** — see [docs](https://docs.molt.bot).
+Hello **world** — see [docs](https://docs.clawd.bot).
 ```
 
 IR (schematic):
@@ -51,7 +51,7 @@ IR (schematic):
     { "start": 6, "end": 11, "style": "bold" }
   ],
   "links": [
-    { "start": 19, "end": 23, "href": "https://docs.molt.bot" }
+    { "start": 19, "end": 23, "href": "https://docs.clawd.bot" }
   ]
 }
 ```

package/docs/concepts/memory.md

@@ -1,12 +1,12 @@
 ---
-summary: "How Pool Bot memory works (workspace files + automatic memory flush)"
+summary: "How Clawdbot memory works (workspace files + automatic memory flush)"
 read_when:
   - You want the memory file layout and workflow
   - You want to tune the automatic pre-compaction memory flush
 ---
 # Memory
 
-Pool Bot memory is **plain Markdown in the agent workspace**. The files are the
+Clawdbot memory is **plain Markdown in the agent workspace**. The files are the
 source of truth; the model only "remembers" what gets written to disk.
 
 Memory search tools are provided by the active memory plugin (default:
@@ -36,7 +36,7 @@ These files live under the workspace (`agents.defaults.workspace`, default
 
 ## Automatic memory flush (pre-compaction ping)
 
-When a session is **close to auto-compaction**, Pool Bot triggers a **silent,
+When a session is **close to auto-compaction**, Clawdbot triggers a **silent,
 agentic turn** that reminds the model to write durable memory **before** the
 context is compacted. The default prompts explicitly say the model *may reply*,
 but usually `NO_REPLY` is the correct response so the user never sees this turn.
@@ -75,13 +75,13 @@ For the full compaction lifecycle, see
 
 ## Vector memory search
 
-Pool Bot can build a small vector index over `MEMORY.md` and `memory/*.md` so
+Clawdbot can build a small vector index over `MEMORY.md` and `memory/*.md` so
 semantic queries can find related notes even when wording differs.
 
 Defaults:
 - Enabled by default.
 - Watches memory files for changes (debounced).
-- Uses remote embeddings by default. If `memorySearch.provider` is not set, Pool Bot auto-selects:
+- Uses remote embeddings by default. If `memorySearch.provider` is not set, Clawdbot auto-selects:
   1. `local` if a `memorySearch.local.modelPath` is configured and the file exists.
   2. `openai` if an OpenAI key can be resolved.
   3. `gemini` if a Gemini key can be resolved.
@@ -89,7 +89,7 @@ Defaults:
 - Local mode uses node-llama-cpp and may require `pnpm approve-builds`.
 - Uses sqlite-vec (when available) to accelerate vector search inside SQLite.
 
-Remote embeddings **require** an API key for the embedding provider. Pool Bot
+Remote embeddings **require** an API key for the embedding provider. Clawdbot
 resolves keys from auth profiles, `models.providers.*.apiKey`, or environment
 variables. Codex OAuth only covers chat/completions and does **not** satisfy
 embeddings for memory search. For Gemini, use `GEMINI_API_KEY` or
@@ -197,15 +197,15 @@ Local mode:
 - File type: Markdown only (`MEMORY.md`, `memory/**/*.md`).
 - Index storage: per-agent SQLite at `~/.clawdbot/memory/<agentId>.sqlite` (configurable via `agents.defaults.memorySearch.store.path`, supports `{agentId}` token).
 - Freshness: watcher on `MEMORY.md` + `memory/` marks the index dirty (debounce 1.5s). Sync is scheduled on session start, on search, or on an interval and runs asynchronously. Session transcripts use delta thresholds to trigger background sync.
-- Reindex triggers: the index stores the embedding **provider/model + endpoint fingerprint + chunking params**. If any of those change, Pool Bot automatically resets and reindexes the entire store.
+- Reindex triggers: the index stores the embedding **provider/model + endpoint fingerprint + chunking params**. If any of those change, Clawdbot automatically resets and reindexes the entire store.
 
 ### Hybrid search (BM25 + vector)
 
-When enabled, Pool Bot combines:
+When enabled, Clawdbot combines:
 - **Vector similarity** (semantic match, wording can differ)
 - **BM25 keyword relevance** (exact tokens like IDs, env vars, code symbols)
 
-If full-text search is unavailable on your platform, Pool Bot falls back to vector-only search.
+If full-text search is unavailable on your platform, Clawdbot falls back to vector-only search.
 
 #### Why hybrid?
 
@@ -266,7 +266,7 @@ agents: {
 
 ### Embedding cache
 
-Pool Bot can cache **chunk embeddings** in SQLite so reindexing and frequent updates (especially session transcripts) don't re-embed unchanged text.
+Clawdbot can cache **chunk embeddings** in SQLite so reindexing and frequent updates (especially session transcripts) don't re-embed unchanged text.
 
 Config:
 
@@ -326,7 +326,7 @@ agents: {
 
 ### SQLite vector acceleration (sqlite-vec)
 
-When the sqlite-vec extension is available, Pool Bot stores embeddings in a
+When the sqlite-vec extension is available, Clawdbot stores embeddings in a
 SQLite virtual table (`vec0`) and performs vector distance queries in the
 database. This keeps search fast without loading every embedding into JS.
 
@@ -350,7 +350,7 @@ agents: {
 Notes:
 - `enabled` defaults to true; when disabled, search falls back to in-process
   cosine similarity over stored embeddings.
-- If the sqlite-vec extension is missing or fails to load, Pool Bot logs the
+- If the sqlite-vec extension is missing or fails to load, Clawdbot logs the
   error and continues with the JS fallback (no vector table).
 - `extensionPath` overrides the bundled sqlite-vec path (useful for custom builds
   or non-standard install locations).

package/docs/concepts/messages.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Messages
 
-This page ties together how Pool Bot handles inbound messages, sessions, queueing,
+This page ties together how Clawdbot handles inbound messages, sessions, queueing,
 streaming, and reasoning visibility.
 
 ## Message flow (high level)
@@ -29,7 +29,7 @@ See [Configuration](/gateway/configuration) for full schema.
 
 ## Inbound dedupe
 
-Channels can redeliver the same message after reconnects. Pool Bot keeps a
+Channels can redeliver the same message after reconnects. Clawdbot keeps a
 short-lived cache keyed by channel/account/peer/session/message id so duplicate
 deliveries do not trigger another agent run.
 
@@ -75,7 +75,7 @@ Details: [Session management](/concepts/session).
 
 ## Inbound bodies and history context
 
-Pool Bot separates the **prompt body** from the **command body**:
+Clawdbot separates the **prompt body** from the **command body**:
 - `Body`: prompt text sent to the agent. This may include channel envelopes and
   optional history wrappers.
 - `CommandBody`: raw user text for directive/command parsing.
@@ -127,7 +127,7 @@ Details: [Streaming + chunking](/concepts/streaming).
 
 ## Reasoning visibility and tokens
 
-Pool Bot can expose or hide model reasoning:
+Clawdbot can expose or hide model reasoning:
 - `/reasoning on|off|stream` controls visibility.
 - Reasoning content still counts toward token usage when produced by the model.
 - Telegram supports reasoning stream into the draft bubble.

package/docs/concepts/model-failover.md

@@ -1,5 +1,5 @@
 ---
-summary: "How Pool Bot rotates auth profiles and falls back across models"
+summary: "How Clawdbot rotates auth profiles and falls back across models"
 read_when:
   - Diagnosing auth profile rotation, cooldowns, or model fallback behavior
   - Updating failover rules for auth profiles or models
@@ -7,7 +7,7 @@ read_when:
 
 # Model failover
 
-Pool Bot handles failures in two stages:
+Clawdbot handles failures in two stages:
 1) **Auth profile rotation** within the current provider.
 2) **Model fallback** to the next model in `agents.defaults.model.fallbacks`.
 
@@ -15,7 +15,7 @@ This doc explains the runtime rules and the data that backs them.
 
 ## Auth storage (keys + OAuth)
 
-Pool Bot uses **auth profiles** for both API keys and OAuth tokens.
+Clawdbot uses **auth profiles** for both API keys and OAuth tokens.
 
 - Secrets live in `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json` (legacy: `~/.clawdbot/agent/auth-profiles.json`).
 - Config `auth.profiles` / `auth.order` are **metadata + routing only** (no secrets).
@@ -37,20 +37,20 @@ Profiles live in `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json` under `
 
 ## Rotation order
 
-When a provider has multiple profiles, Pool Bot chooses an order like this:
+When a provider has multiple profiles, Clawdbot chooses an order like this:
 
 1) **Explicit config**: `auth.order[provider]` (if set).
 2) **Configured profiles**: `auth.profiles` filtered by provider.
 3) **Stored profiles**: entries in `auth-profiles.json` for the provider.
 
-If no explicit order is configured, Pool Bot uses a round‑robin order:
+If no explicit order is configured, Clawdbot uses a round‑robin order:
 - **Primary key:** profile type (**OAuth before API keys**).
 - **Secondary key:** `usageStats.lastUsed` (oldest first, within each type).
 - **Cooldown/disabled profiles** are moved to the end, ordered by soonest expiry.
 
 ### Session stickiness (cache-friendly)
 
-Pool Bot **pins the chosen auth profile per session** to keep provider caches warm.
+Clawdbot **pins the chosen auth profile per session** to keep provider caches warm.
 It does **not** rotate on every request. The pinned profile is reused until:
 - the session is reset (`/new` / `/reset`)
 - a compaction completes (compaction count increments)
@@ -60,9 +60,9 @@ Manual selection via `/model …@<profileId>` sets a **user override** for that
 and is not auto‑rotated until a new session starts.
 
 Auto‑pinned profiles (selected by the session router) are treated as a **preference**:
-they are tried first, but Pool Bot may rotate to another profile on rate limits/timeouts.
+they are tried first, but Clawdbot may rotate to another profile on rate limits/timeouts.
 User‑pinned profiles stay locked to that profile; if it fails and model fallbacks
-are configured, Pool Bot moves to the next model instead of switching profiles.
+are configured, Clawdbot moves to the next model instead of switching profiles.
 
 ### Why OAuth can “look lost”
 
@@ -73,7 +73,7 @@ If you have both an OAuth profile and an API key profile for the same provider,
 ## Cooldowns
 
 When a profile fails due to auth/rate‑limit errors (or a timeout that looks
-like rate limiting), Pool Bot marks it in cooldown and moves to the next profile.
+like rate limiting), Clawdbot marks it in cooldown and moves to the next profile.
 Format/invalid‑request errors (for example Cloud Code Assist tool call ID
 validation failures) are treated as failover‑worthy and use the same cooldowns.
 
@@ -99,7 +99,7 @@ State is stored in `auth-profiles.json` under `usageStats`:
 
 ## Billing disables
 
-Billing/credit failures (for example “insufficient credits” / “credit balance too low”) are treated as failover‑worthy, but they’re usually not transient. Instead of a short cooldown, Pool Bot marks the profile as **disabled** (with a longer backoff) and rotates to the next profile/provider.
+Billing/credit failures (for example “insufficient credits” / “credit balance too low”) are treated as failover‑worthy, but they’re usually not transient. Instead of a short cooldown, Clawdbot marks the profile as **disabled** (with a longer backoff) and rotates to the next profile/provider.
 
 State is stored in `auth-profiles.json`:
 
@@ -120,7 +120,7 @@ Defaults:
 
 ## Model fallback
 
-If all profiles for a provider fail, Pool Bot moves to the next model in
+If all profiles for a provider fail, Clawdbot moves to the next model in
 `agents.defaults.model.fallbacks`. This applies to auth failures, rate limits, and
 timeouts that exhausted profile rotation (other errors do not advance fallback).