@poolzin/pool-bot 2026.1.26 → 2026.1.29

package/docs/concepts/session-tool.md

@@ -63,7 +63,7 @@ Parameters:
 Behavior:
 - `includeTools=false` filters `role: "toolResult"` messages.
 - Returns messages array in the raw transcript format.
-- When given a `sessionId`, Clawdbot resolves it to the corresponding session key (missing ids error).
+- When given a `sessionId`, Pool Bot resolves it to the corresponding session key (missing ids error).
 
 ## sessions_send
 Send a message into another session.
@@ -81,11 +81,11 @@ Behavior:
 - Announce delivery runs after the primary run completes and is best-effort; `status: "ok"` does not guarantee the announce was delivered.
 - Waits via gateway `agent.wait` (server-side) so reconnects don't drop the wait.
 - Agent-to-agent message context is injected for the primary run.
-- After the primary run completes, Clawdbot runs a **reply-back loop**:
+- After the primary run completes, Pool Bot runs a **reply-back loop**:
   - Round 2+ alternates between requester and target agents.
   - Reply exactly `REPLY_SKIP` to stop the ping‑pong.
   - Max turns is `session.agentToAgent.maxPingPongTurns` (0–5, default 5).
-- Once the loop ends, Clawdbot runs the **agent‑to‑agent announce step** (target agent only):
+- Once the loop ends, Pool Bot runs the **agent‑to‑agent announce step** (target agent only):
   - Reply exactly `ANNOUNCE_SKIP` to stay silent.
   - Any other reply is sent to the target channel.
   - Announce step includes the original request + round‑1 reply + latest ping‑pong reply.
@@ -145,7 +145,7 @@ Behavior:
 - Sub-agents default to the full tool set **minus session tools** (configurable via `tools.subagents.tools`).
 - Sub-agents are not allowed to call `sessions_spawn` (no sub-agent → sub-agent spawning).
 - Always non-blocking: returns `{ status: "accepted", runId, childSessionKey }` immediately.
-- After completion, Clawdbot runs a sub-agent **announce step** and posts the result to the requester chat channel.
+- After completion, Pool Bot runs a sub-agent **announce step** and posts the result to the requester chat channel.
 - Reply exactly `ANNOUNCE_SKIP` during the announce step to stay silent.
 - Announce replies are normalized to `Status`/`Result`/`Notes`; `Status` comes from runtime outcome (not model text).
 - Sub-agent sessions are auto-archived after `agents.defaults.subagents.archiveAfterMinutes` (default: 60).

package/docs/concepts/session.md

@@ -5,7 +5,7 @@ read_when:
 ---
 # Session Management
 
-Clawdbot treats **one direct-chat session per agent** as primary. Direct chats collapse to `agent:<agentId>:<mainKey>` (default `main`), while group/channel chats get their own keys. `session.mainKey` is honored.
+Pool Bot treats **one direct-chat session per agent** as primary. Direct chats collapse to `agent:<agentId>:<mainKey>` (default `main`), while group/channel chats get their own keys. `session.mainKey` is honored.
 
 Use `session.dmScope` to control how **direct messages** are grouped:
 - `main` (default): all DMs share the main session for continuity.
@@ -14,26 +14,26 @@ Use `session.dmScope` to control how **direct messages** are grouped:
 Use `session.identityLinks` to map provider-prefixed peer ids to a canonical identity so the same person shares a DM session across channels when using `per-peer` or `per-channel-peer`.
 
 ## Gateway is the source of truth
-All session state is **owned by the gateway** (the “master” Clawdbot). UI clients (macOS app, WebChat, etc.) must query the gateway for session lists and token counts instead of reading local files.
+All session state is **owned by the gateway** (the “master” Pool Bot). UI clients (macOS app, WebChat, etc.) must query the gateway for session lists and token counts instead of reading local files.
 
 - In **remote mode**, the session store you care about lives on the remote gateway host, not your Mac.
 - Token counts shown in UIs come from the gateway’s store fields (`inputTokens`, `outputTokens`, `totalTokens`, `contextTokens`). Clients do not parse JSONL transcripts to “fix up” totals.
 
 ## Where state lives
 - On the **gateway host**:
-  - Store file: `~/.clawdbot/agents/<agentId>/sessions/sessions.json` (per agent).
-- Transcripts: `~/.clawdbot/agents/<agentId>/sessions/<SessionId>.jsonl` (Telegram topic sessions use `.../<SessionId>-topic-<threadId>.jsonl`).
+  - Store file: `~/.poolbot/agents/<agentId>/sessions/sessions.json` (per agent).
+- Transcripts: `~/.poolbot/agents/<agentId>/sessions/<SessionId>.jsonl` (Telegram topic sessions use `.../<SessionId>-topic-<threadId>.jsonl`).
 - The store is a map `sessionKey -> { sessionId, updatedAt, ... }`. Deleting entries is safe; they are recreated on demand.
 - Group entries may include `displayName`, `channel`, `subject`, `room`, and `space` to label sessions in UIs.
 - Session entries include `origin` metadata (label + routing hints) so UIs can explain where a session came from.
-- Clawdbot does **not** read legacy Pi/Tau session folders.
+- Pool Bot does **not** read legacy Pi/Tau session folders.
 
 ## Session pruning
-Clawdbot trims **old tool results** from the in-memory context right before LLM calls by default.
+Pool Bot trims **old tool results** from the in-memory context right before LLM calls by default.
 This does **not** rewrite JSONL history. See [/concepts/session-pruning](/concepts/session-pruning).
 
 ## Pre-compaction memory flush
-When a session nears auto-compaction, Clawdbot can run a **silent memory flush**
+When a session nears auto-compaction, Pool Bot can run a **silent memory flush**
 turn that reminds the model to write durable notes to disk. This only runs when
 the workspace is writable. See [Memory](/concepts/memory) and
 [Compaction](/concepts/compaction).
@@ -58,10 +58,10 @@ the workspace is writable. See [Memory](/concepts/memory) and
 - Reset policy: sessions are reused until they expire, and expiry is evaluated on the next inbound message.
 - Daily reset: defaults to **4:00 AM local time on the gateway host**. A session is stale once its last update is earlier than the most recent daily reset time.
 - Idle reset (optional): `idleMinutes` adds a sliding idle window. When both daily and idle resets are configured, **whichever expires first** forces a new session.
-- Legacy idle-only: if you set `session.idleMinutes` without any `session.reset`/`resetByType` config, Clawdbot stays in idle-only mode for backward compatibility.
+- Legacy idle-only: if you set `session.idleMinutes` without any `session.reset`/`resetByType` config, Pool Bot stays in idle-only mode for backward compatibility.
 - Per-type overrides (optional): `resetByType` lets you override the policy for `dm`, `group`, and `thread` sessions (thread = Slack/Discord threads, Telegram topics, Matrix threads when provided by the connector).
 - Per-channel overrides (optional): `resetByChannel` overrides the reset policy for a channel (applies to all session types for that channel and takes precedence over `reset`/`resetByType`).
-- Reset triggers: exact `/new` or `/reset` (plus any extras in `resetTriggers`) start a fresh session id and pass the remainder of the message through. `/new <model>` accepts a model alias, `provider/model`, or provider name (fuzzy match) to set the new session model. If `/new` or `/reset` is sent alone, Clawdbot runs a short “hello” greeting turn to confirm the reset.
+- Reset triggers: exact `/new` or `/reset` (plus any extras in `resetTriggers`) start a fresh session id and pass the remainder of the message through. `/new <model>` accepts a model alias, `provider/model`, or provider name (fuzzy match) to set the new session model. If `/new` or `/reset` is sent alone, Pool Bot runs a short “hello” greeting turn to confirm the reset.
 - Manual reset: delete specific keys from the store or remove the JSONL transcript; the next message recreates them.
 - Isolated cron jobs always mint a fresh `sessionId` per run (no idle reuse).
 
@@ -90,7 +90,7 @@ Send these as standalone messages so they register.
 
 ## Configuration (optional rename example)
 ```json5
-// ~/.clawdbot/clawdbot.json
+// ~/.poolbot/poolbot.json
 {
   session: {
     scope: "per-sender",      // keep group keys separate
@@ -114,16 +114,16 @@ Send these as standalone messages so they register.
       discord: { mode: "idle", idleMinutes: 10080 }
     },
     resetTriggers: ["/new", "/reset"],
-    store: "~/.clawdbot/agents/{agentId}/sessions/sessions.json",
+    store: "~/.poolbot/agents/{agentId}/sessions/sessions.json",
     mainKey: "main",
   }
 }
 ```
 
 ## Inspecting
-- `clawdbot status` — shows store path and recent sessions.
-- `clawdbot sessions --json` — dumps every entry (filter with `--active <minutes>`).
-- `clawdbot gateway call sessions.list --params '{}'` — fetch sessions from the running gateway (use `--url`/`--token` for remote gateway access).
+- `poolbot status` — shows store path and recent sessions.
+- `poolbot sessions --json` — dumps every entry (filter with `--active <minutes>`).
+- `poolbot gateway call sessions.list --params '{}'` — fetch sessions from the running gateway (use `--url`/`--token` for remote gateway access).
 - Send `/status` as a standalone message in chat to see whether the agent is reachable, how much of the session context is used, current thinking/verbose toggles, and when your WhatsApp web creds were last refreshed (helps spot relink needs).
 - Send `/context list` or `/context detail` to see what’s in the system prompt and injected workspace files (and the biggest context contributors).
 - Send `/stop` as a standalone message to abort the current run, clear queued followups for that session, and stop any sub-agent runs spawned from it (the reply includes the stopped count).

package/docs/concepts/streaming.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Streaming + chunking
 
-Clawdbot has two separate “streaming” layers:
+Pool Bot has two separate “streaming” layers:
 - **Block streaming (channels):** emit completed **blocks** as the assistant writes. These are normal channel messages (not token deltas).
 - **Token-ish streaming (Telegram only):** update a **draft bubble** with partial text while generating; final message is sent at the end.
 
@@ -59,7 +59,7 @@ Block chunking is implemented by `EmbeddedBlockChunker`:
 
 ## Coalescing (merge streamed blocks)
 
-When block streaming is enabled, Clawdbot can **merge consecutive block chunks**
+When block streaming is enabled, Pool Bot can **merge consecutive block chunks**
 before sending them out. This reduces “single-line spam” while still providing
 progressive output.
 
@@ -109,7 +109,7 @@ Telegram is the only channel with draft streaming:
 - Final reply is still a normal message.
 - `/reasoning stream` writes reasoning into the draft bubble (Telegram only).
 
-When draft streaming is active, Clawdbot disables block streaming for that reply to avoid double-streaming.
+When draft streaming is active, Pool Bot disables block streaming for that reply to avoid double-streaming.
 
 ```
 Telegram (private + topics)

package/docs/concepts/system-prompt.md

@@ -1,14 +1,14 @@
 ---
-summary: "What the Clawdbot system prompt contains and how it is assembled"
+summary: "What the Pool Bot system prompt contains and how it is assembled"
 read_when:
   - Editing system prompt text, tools list, or time/heartbeat sections
   - Changing workspace bootstrap or skills injection behavior
 ---
 # System Prompt
 
-Clawdbot builds a custom system prompt for every agent run. The prompt is **Clawdbot-owned** and does not use the p-coding-agent default prompt.
+Pool Bot builds a custom system prompt for every agent run. The prompt is **Pool Bot-owned** and does not use the p-coding-agent default prompt.
 
-The prompt is assembled by Clawdbot and injected into each agent run.
+The prompt is assembled by Pool Bot and injected into each agent run.
 
 ## Structure
 
@@ -16,9 +16,9 @@ The prompt is intentionally compact and uses fixed sections:
 
 - **Tooling**: current tool list + short descriptions.
 - **Skills** (when available): tells the model how to load skill instructions on demand.
-- **Clawdbot Self-Update**: how to run `config.apply` and `update.run`.
+- **Pool Bot Self-Update**: how to run `config.apply` and `update.run`.
 - **Workspace**: working directory (`agents.defaults.workspace`).
-- **Documentation**: local path to Clawdbot docs (repo or npm package) and when to read them.
+- **Documentation**: local path to Pool Bot docs (repo or npm package) and when to read them.
 - **Workspace Files (injected)**: indicates bootstrap files are included below.
 - **Sandbox** (when enabled): indicates sandboxed runtime, sandbox paths, and whether elevated exec is available.
 - **Current Date & Time**: user-local time, timezone, and time format.
@@ -29,11 +29,11 @@ The prompt is intentionally compact and uses fixed sections:
 
 ## Prompt modes
 
-Clawdbot can render smaller system prompts for sub-agents. The runtime sets a
+Pool Bot can render smaller system prompts for sub-agents. The runtime sets a
 `promptMode` for each run (not a user-facing config):
 
 - `full` (default): includes all sections above.
-- `minimal`: used for sub-agents; omits **Skills**, **Memory Recall**, **Clawdbot
+- `minimal`: used for sub-agents; omits **Skills**, **Memory Recall**, **Pool Bot
   Self-Update**, **Model Aliases**, **User Identity**, **Reply Tags**,
   **Messaging**, **Silent Replies**, and **Heartbeats**. Tooling, Workspace,
   Sandbox, Current Date & Time (when known), Runtime, and injected context stay
@@ -82,7 +82,7 @@ See [Date & Time](/date-time) for full behavior details.
 
 ## Skills
 
-When eligible skills exist, Clawdbot injects a compact **available skills list**
+When eligible skills exist, Pool Bot injects a compact **available skills list**
 (`formatSkillsForPrompt`) that includes the **file path** for each skill. The
 prompt instructs the model to use `read` to load the SKILL.md at the listed
 location (workspace, managed, or bundled). If no skills are eligible, the
@@ -103,8 +103,8 @@ This keeps the base prompt small while still enabling targeted skill usage.
 ## Documentation
 
 When available, the system prompt includes a **Documentation** section that points to the
-local Clawdbot docs directory (either `docs/` in the repo workspace or the bundled npm
+local Pool Bot docs directory (either `docs/` in the repo workspace or the bundled npm
 package docs) and also notes the public mirror, source repo, community Discord, and
 ClawdHub (https://clawdhub.com) for skills discovery. The prompt instructs the model to consult local docs first
-for Clawdbot behavior, commands, configuration, or architecture, and to run
-`clawdbot status` itself when possible (asking the user only when it lacks access).
+for Pool Bot behavior, commands, configuration, or architecture, and to run
+`poolbot status` itself when possible (asking the user only when it lacks access).

package/docs/concepts/timezone.md

@@ -7,7 +7,7 @@ read_when:
 
 # Timezones
 
-Clawdbot standardizes timestamps so the model sees a **single reference time**.
+Pool Bot standardizes timestamps so the model sees a **single reference time**.
 
 ## Message envelopes (local by default)
 
@@ -72,7 +72,7 @@ Raw provider fields are preserved.
 ## User timezone for the system prompt
 
 Set `agents.defaults.userTimezone` to tell the model the user's local time zone. If it is
-unset, Clawdbot resolves the **host timezone at runtime** (no config write).
+unset, Pool Bot resolves the **host timezone at runtime** (no config write).
 
 ```json5
 {

package/docs/concepts/typebox.md

@@ -91,7 +91,7 @@ Connect (first message):
     "minProtocol": 2,
     "maxProtocol": 2,
     "client": {
-      "id": "clawdbot-macos",
+      "id": "poolbot-macos",
       "displayName": "macos",
       "version": "1.0.0",
       "platform": "macos 15.1",
@@ -272,7 +272,7 @@ Unknown frame types are preserved as raw payloads for forward compatibility.
 Generated JSON Schema is in the repo at `dist/protocol.schema.json`. The
 published raw file is typically available at:
 
-- https://raw.githubusercontent.com/clawdbot/clawdbot/main/dist/protocol.schema.json
+- https://raw.githubusercontent.com/poolbot/poolbot/main/dist/protocol.schema.json
 
 ## When you change schemas
 

package/docs/concepts/typing-indicators.md

@@ -1,5 +1,5 @@
 ---
-summary: "When Clawdbot shows typing indicators and how to tune them"
+summary: "When Pool Bot shows typing indicators and how to tune them"
 read_when:
   - Changing typing indicator behavior or defaults
 ---
@@ -10,7 +10,7 @@ Typing indicators are sent to the chat channel while a run is active. Use
 to control **how often** it refreshes.
 
 ## Defaults
-When `agents.defaults.typingMode` is **unset**, Clawdbot keeps the legacy behavior:
+When `agents.defaults.typingMode` is **unset**, Pool Bot keeps the legacy behavior:
 - **Direct chats**: typing starts immediately once the model loop begins.
 - **Group chats with a mention**: typing starts immediately.
 - **Group chats without a mention**: typing starts only when message text begins streaming.

package/docs/concepts/usage-tracking.md

@@ -13,9 +13,9 @@ read_when:
 ## Where it shows up
 - `/status` in chats: emoji‑rich status card with session tokens + estimated cost (API key only). Provider usage shows for the **current model provider** when available.
 - `/usage off|tokens|full` in chats: per-response usage footer (OAuth shows tokens only).
-- `/usage cost` in chats: local cost summary aggregated from Clawdbot session logs.
-- CLI: `clawdbot status --usage` prints a full per-provider breakdown.
-- CLI: `clawdbot channels list` prints the same usage snapshot alongside provider config (use `--no-usage` to skip).
+- `/usage cost` in chats: local cost summary aggregated from Pool Bot session logs.
+- CLI: `poolbot status --usage` prints a full per-provider breakdown.
+- CLI: `poolbot channels list` prints the same usage snapshot alongside provider config (use `--no-usage` to skip).
 - macOS menu bar: “Usage” section under Context (only if available).
 
 ## Providers + credentials

package/docs/date-time.md

@@ -7,7 +7,7 @@ read_when:
 
 # Date & Time
 
-Clawdbot defaults to **host-local time for transport timestamps** and **user timezone only in the system prompt**.
+Pool Bot defaults to **host-local time for transport timestamps** and **user timezone only in the system prompt**.
 Provider timestamps are preserved so tools keep their native semantics (current time is available via `session_status`).
 
 ## Message envelopes (local by default)
@@ -101,7 +101,7 @@ System: [2026-01-12 12:19:17 PST] Model switched.
 
 ## Time format detection (auto)
 
-When `timeFormat: "auto"`, Clawdbot inspects the OS preference (macOS/Windows)
+When `timeFormat: "auto"`, Pool Bot inspects the OS preference (macOS/Windows)
 and falls back to locale formatting. The detected value is **cached per process**
 to avoid repeated system calls.
 

package/docs/debug/node-issue.md

@@ -2,16 +2,16 @@
 summary: Node + tsx "__name is not a function" crash notes and workarounds
 read_when:
   - Debugging Node-only dev scripts or watch mode failures
-  - Investigating tsx/esbuild loader crashes in Clawdbot
+  - Investigating tsx/esbuild loader crashes in Pool Bot
 ---
 
 # Node + tsx "__name is not a function" crash
 
 ## Summary
-Running Clawdbot via Node with `tsx` fails at startup with:
+Running Pool Bot via Node with `tsx` fails at startup with:
 
 ```
-[clawdbot] Failed to start CLI: TypeError: __name is not a function
+[poolbot] Failed to start CLI: TypeError: __name is not a function
     at createSubsystemLogger (.../src/logging/subsystem.ts:203:25)
     at .../src/agents/auth-profiles/constants.ts:25:20
 ```
@@ -48,7 +48,7 @@ node --import tsx scripts/repro/tsx-name-repro.ts
 
 ## Regression history
 - `2871657e` (2026-01-06): scripts changed from Bun to tsx to make Bun optional.
-- Before that (Bun path), `clawdbot status` and `gateway:watch` worked.
+- Before that (Bun path), `poolbot status` and `gateway:watch` worked.
 
 ## Workarounds
 - Use Bun for dev scripts (current temporary revert).

package/docs/debugging.md

@@ -15,13 +15,13 @@ provider mixes reasoning into normal text.
 
 Use `/debug` in chat to set **runtime-only** config overrides (memory, not disk).
 `/debug` is disabled by default; enable with `commands.debug: true`.
-This is handy when you need to toggle obscure settings without editing `clawdbot.json`.
+This is handy when you need to toggle obscure settings without editing `poolbot.json`.
 
 Examples:
 
 ```
 /debug show
-/debug set messages.responsePrefix="[clawdbot]"
+/debug set messages.responsePrefix="[poolbot]"
 /debug unset messages.responsePrefix
 /debug reset
 ```
@@ -50,7 +50,7 @@ on each restart.
 Use the dev profile to isolate state and spin up a safe, disposable setup for
 debugging. There are **two** `--dev` flags:
 
-- **Global `--dev` (profile):** isolates state under `~/.clawdbot-dev` and
+- **Global `--dev` (profile):** isolates state under `~/.poolbot-dev` and
   defaults the gateway port to `19001` (derived ports shift with it).
 - **`gateway --dev`: tells the Gateway to auto-create a default config +
   workspace** when missing (and skip BOOTSTRAP.md).
@@ -59,17 +59,17 @@ Recommended flow (dev profile + dev bootstrap):
 
 ```bash
 pnpm gateway:dev
-CLAWDBOT_PROFILE=dev clawdbot tui
+CLAWDBOT_PROFILE=dev poolbot tui
 ```
 
-If you don’t have a global install yet, run the CLI via `pnpm clawdbot ...`.
+If you don’t have a global install yet, run the CLI via `pnpm poolbot ...`.
 
 What this does:
 
 1) **Profile isolation** (global `--dev`)
    - `CLAWDBOT_PROFILE=dev`
-   - `CLAWDBOT_STATE_DIR=~/.clawdbot-dev`
-   - `CLAWDBOT_CONFIG_PATH=~/.clawdbot-dev/clawdbot.json`
+   - `CLAWDBOT_STATE_DIR=~/.poolbot-dev`
+   - `CLAWDBOT_CONFIG_PATH=~/.poolbot-dev/poolbot.json`
    - `CLAWDBOT_GATEWAY_PORT=19001` (browser/canvas shift accordingly)
 
 2) **Dev bootstrap** (`gateway --dev`)
@@ -91,7 +91,7 @@ Note: `--dev` is a **global** profile flag and gets eaten by some runners.
 If you need to spell it out, use the env var form:
 
 ```bash
-CLAWDBOT_PROFILE=dev clawdbot gateway --dev --reset
+CLAWDBOT_PROFILE=dev poolbot gateway --dev --reset
 ```
 
 `--reset` wipes config, credentials, sessions, and the dev workspace (using
@@ -100,12 +100,12 @@ CLAWDBOT_PROFILE=dev clawdbot gateway --dev --reset
 Tip: if a non‑dev gateway is already running (launchd/systemd), stop it first:
 
 ```bash
-clawdbot gateway stop
+poolbot gateway stop
 ```
 
-## Raw stream logging (Clawdbot)
+## Raw stream logging (Pool Bot)
 
-Clawdbot can log the **raw assistant stream** before any filtering/formatting.
+Pool Bot can log the **raw assistant stream** before any filtering/formatting.
 This is the best way to see whether reasoning is arriving as plain text deltas
 (or as separate thinking blocks).
 
@@ -118,19 +118,19 @@ pnpm gateway:watch --force --raw-stream
 Optional path override:
 
 ```bash
-pnpm gateway:watch --force --raw-stream --raw-stream-path ~/.clawdbot/logs/raw-stream.jsonl
+pnpm gateway:watch --force --raw-stream --raw-stream-path ~/.poolbot/logs/raw-stream.jsonl
 ```
 
 Equivalent env vars:
 
 ```bash
 CLAWDBOT_RAW_STREAM=1
-CLAWDBOT_RAW_STREAM_PATH=~/.clawdbot/logs/raw-stream.jsonl
+CLAWDBOT_RAW_STREAM_PATH=~/.poolbot/logs/raw-stream.jsonl
 ```
 
 Default file:
 
-`~/.clawdbot/logs/raw-stream.jsonl`
+`~/.poolbot/logs/raw-stream.jsonl`
 
 ## Raw chunk logging (pi-mono)
 

package/docs/diagnostics/flags.md

@@ -55,7 +55,7 @@ CLAWDBOT_DIAGNOSTICS=0
 Flags emit logs into the standard diagnostics log file. By default:
 
 ```
-/tmp/clawdbot/clawdbot-YYYY-MM-DD.log
+/tmp/poolbot/poolbot-YYYY-MM-DD.log
 ```
 
 If you set `logging.file`, use that path instead. Logs are JSONL (one JSON object per line). Redaction still applies based on `logging.redactSensitive`.
@@ -65,22 +65,22 @@ If you set `logging.file`, use that path instead. Logs are JSONL (one JSON objec
 Pick the latest log file:
 
 ```bash
-ls -t /tmp/clawdbot/clawdbot-*.log | head -n 1
+ls -t /tmp/poolbot/poolbot-*.log | head -n 1
 ```
 
 Filter for Telegram HTTP diagnostics:
 
 ```bash
-rg "telegram http error" /tmp/clawdbot/clawdbot-*.log
+rg "telegram http error" /tmp/poolbot/poolbot-*.log
 ```
 
 Or tail while reproducing:
 
 ```bash
-tail -f /tmp/clawdbot/clawdbot-$(date +%F).log | rg "telegram http error"
+tail -f /tmp/poolbot/poolbot-$(date +%F).log | rg "telegram http error"
 ```
 
-For remote gateways, you can also use `clawdbot logs --follow` (see [/cli/logs](/cli/logs)).
+For remote gateways, you can also use `poolbot logs --follow` (see [/cli/logs](/cli/logs)).
 
 ## Notes
 

package/docs/docs.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://mintlify.com/docs.json",
-  "name": "Clawdbot",
+  "name": "Moltbot",
   "theme": "mint",
   "logo": {
     "light": "/assets/pixel-lobster.svg",
@@ -13,11 +13,11 @@
   "topbarLinks": [
     {
       "name": "GitHub",
-      "url": "https://github.com/clawdbot/clawdbot"
+      "url": "https://github.com/poolbot/poolbot"
     },
     {
       "name": "Releases",
-      "url": "https://github.com/clawdbot/clawdbot/releases"
+      "url": "https://github.com/poolbot/poolbot/releases"
     }
   ],
   "redirects": [
@@ -117,6 +117,14 @@
       "source": "/mattermost/",
       "destination": "/channels/mattermost"
     },
+    {
+      "source": "/line",
+      "destination": "/channels/line"
+    },
+    {
+      "source": "/line/",
+      "destination": "/channels/line"
+    },
     {
       "source": "/glm",
       "destination": "/providers/glm"
@@ -197,6 +205,14 @@
       "source": "/providers/msteams/",
       "destination": "/channels/msteams"
     },
+    {
+      "source": "/providers/line",
+      "destination": "/channels/line"
+    },
+    {
+      "source": "/providers/line/",
+      "destination": "/channels/line"
+    },
     {
       "source": "/providers/signal",
       "destination": "/channels/signal"
@@ -329,10 +345,6 @@
       "source": "/auth-monitoring",
       "destination": "/automation/auth-monitoring"
     },
-    {
-      "source": "/scripts",
-      "destination": "/scripts"
-    },
     {
       "source": "/camera",
       "destination": "/nodes/camera"
@@ -788,6 +800,18 @@
     {
       "source": "/install/railway/",
       "destination": "/railway"
+    },
+    {
+      "source": "/install/northflank/",
+      "destination": "/northflank"
+    },
+    {
+      "source": "/gcp",
+      "destination": "/platforms/gcp"
+    },
+    {
+      "source": "/gcp/",
+      "destination": "/platforms/gcp"
     }
   ],
   "navigation": {
@@ -827,6 +851,8 @@
           "install/nix",
           "install/docker",
           "railway",
+          "render",
+          "northflank",
           "install/bun"
         ]
       },
@@ -930,6 +956,7 @@
           "gateway/doctor",
           "gateway/logging",
           "gateway/security",
+          "security/formal-verification",
           "gateway/sandbox-vs-tool-policy-vs-elevated",
           "gateway/sandboxing",
           "gateway/troubleshooting",
@@ -965,6 +992,7 @@
           "channels/signal",
           "channels/imessage",
           "channels/msteams",
+          "channels/line",
           "channels/matrix",
           "channels/zalo",
           "channels/zalouser",
@@ -983,6 +1011,7 @@
           "bedrock",
           "providers/moonshot",
           "providers/minimax",
+          "providers/vercel-ai-gateway",
           "providers/openrouter",
           "providers/synthetic",
           "providers/opencode",
@@ -1055,6 +1084,7 @@
           "platforms/linux",
           "platforms/fly",
           "platforms/hetzner",
+          "platforms/gcp",
           "platforms/exe-dev"
         ]
       },

package/docs/environment.md

@@ -1,5 +1,5 @@
 ---
-summary: "Where Clawdbot loads environment variables and the precedence order"
+summary: "Where Pool Bot loads environment variables and the precedence order"
 read_when:
   - You need to know which env vars are loaded, and in what order
   - You are debugging missing API keys in the Gateway
@@ -7,14 +7,14 @@ read_when:
 ---
 # Environment variables
 
-Clawdbot pulls environment variables from multiple sources. The rule is **never override existing values**.
+Pool Bot pulls environment variables from multiple sources. The rule is **never override existing values**.
 
 ## Precedence (highest → lowest)
 
 1) **Process environment** (what the Gateway process already has from the parent shell/daemon).
 2) **`.env` in the current working directory** (dotenv default; does not override).
-3) **Global `.env`** at `~/.clawdbot/.env` (aka `$CLAWDBOT_STATE_DIR/.env`; does not override).
-4) **Config `env` block** in `~/.clawdbot/clawdbot.json` (applied only if missing).
+3) **Global `.env`** at `~/.poolbot/.env` (aka `$CLAWDBOT_STATE_DIR/.env`; does not override).
+4) **Config `env` block** in `~/.poolbot/poolbot.json` (applied only if missing).
 5) **Optional login-shell import** (`env.shellEnv.enabled` or `CLAWDBOT_LOAD_SHELL_ENV=1`), applied only for missing expected keys.
 
 If the config file is missing entirely, step 4 is skipped; shell import still runs if enabled.

package/docs/experiments/plans/cron-add-hardening.md

@@ -1,6 +1,6 @@
 ---
 summary: "Harden cron.add input handling, align schemas, and improve cron UI/agent tooling"
-owner: "clawdbot"
+owner: "poolbot"
 status: "complete"
 last_updated: "2026-01-05"
 ---

package/docs/experiments/plans/openresponses-gateway.md

@@ -1,6 +1,6 @@
 ---
 summary: "Plan: Add OpenResponses /v1/responses endpoint and deprecate chat completions cleanly"
-owner: "clawdbot"
+owner: "poolbot"
 status: "draft"
 last_updated: "2026-01-19"
 ---
@@ -9,7 +9,7 @@ last_updated: "2026-01-19"
 
 ## Context
 
-Clawdbot Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
+Pool Bot Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
 `/v1/chat/completions` (see [OpenAI Chat Completions](/gateway/openai-http-api)).
 
 Open Responses is an open inference standard based on the OpenAI Responses API. It is designed