@poolzin/pool-bot 2026.1.26 → 2026.1.29

package/docs/start/getting-started.md

@@ -9,7 +9,11 @@ read_when:
 
 Goal: go from **zero** → **first working chat** (with sane defaults) as quickly as possible.
 
-Recommended path: use the **CLI onboarding wizard** (`clawdbot onboard`). It sets up:
+Fastest chat: open the Control UI (no channel setup needed). Run `poolbot dashboard`
+and chat in the browser, or open `http://127.0.0.1:18789/` on the gateway host.
+Docs: [Dashboard](/web/dashboard) and [Control UI](/web/control-ui).
+
+Recommended path: use the **CLI onboarding wizard** (`poolbot onboard`). It sets up:
 - model/auth (OAuth recommended)
 - gateway settings
 - channels (WhatsApp/Telegram/Discord/Mattermost (plugin)/...)
@@ -41,7 +45,7 @@ run on host, set an explicit per-agent override:
 - Node `>=22`
 - `pnpm` (optional; recommended if you build from source)
 - **Recommended:** Brave Search API key for web search. Easiest path:
-  `clawdbot configure --section web` (stores `tools.web.search.apiKey`).
+  `poolbot configure --section web` (stores `tools.web.search.apiKey`).
   See [Web tools](/tools/web).
 
 macOS: if you plan to build the apps, install Xcode / CLT. For the CLI + gateway only, Node is enough.
@@ -50,7 +54,7 @@ Windows: use **WSL2** (Ubuntu recommended). WSL2 is strongly recommended; native
 ## 1) Install the CLI (recommended)
 
 ```bash
-curl -fsSL https://clawd.bot/install.sh | bash
+curl -fsSL https://molt.bot/install.sh | bash
 ```
 
 Installer options (install method, non-interactive, from GitHub): [Install](/install).
@@ -58,23 +62,23 @@ Installer options (install method, non-interactive, from GitHub): [Install](/ins
 Windows (PowerShell):
 
 ```powershell
-iwr -useb https://clawd.bot/install.ps1 | iex
+iwr -useb https://molt.bot/install.ps1 | iex
 ```
 
 Alternative (global install):
 
 ```bash
-npm install -g clawdbot@latest
+npm install -g poolbot@latest
 ```
 
 ```bash
-pnpm add -g clawdbot@latest
+pnpm add -g poolbot@latest
 ```
 
 ## 2) Run the onboarding wizard (and install the service)
 
 ```bash
-clawdbot onboard --install-daemon
+poolbot onboard --install-daemon
 ```
 
 What you’ll choose:
@@ -91,8 +95,8 @@ Wizard doc: [Wizard](/start/wizard)
 
 - **Recommended Anthropic path:** set an API key (wizard can store it for service use). `claude setup-token` is also supported if you want to reuse Claude Code credentials.
 
-- OAuth credentials (legacy import): `~/.clawdbot/credentials/oauth.json`
-- Auth profiles (OAuth + API keys): `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json`
+- OAuth credentials (legacy import): `~/.poolbot/credentials/oauth.json`
+- Auth profiles (OAuth + API keys): `~/.poolbot/agents/<agentId>/agent/auth-profiles.json`
 
 Headless/server tip: do OAuth on a normal machine first, then copy `oauth.json` to the gateway host.
 
@@ -101,13 +105,13 @@ Headless/server tip: do OAuth on a normal machine first, then copy `oauth.json`
 If you installed the service during onboarding, the Gateway should already be running:
 
 ```bash
-clawdbot gateway status
+poolbot gateway status
 ```
 
 Manual run (foreground):
 
 ```bash
-clawdbot gateway --port 18789 --verbose
+poolbot gateway --port 18789 --verbose
 ```
 
 Dashboard (local loopback): `http://127.0.0.1:18789/`
@@ -119,8 +123,9 @@ channels. If you use WhatsApp or Telegram, run the Gateway with **Node**.
 ## 3.5) Quick verify (2 min)
 
 ```bash
-clawdbot status
-clawdbot health
+poolbot status
+poolbot health
+poolbot security audit --deep
 ```
 
 ## 4) Pair + connect your first chat surface
@@ -128,7 +133,7 @@ clawdbot health
 ### WhatsApp (QR login)
 
 ```bash
-clawdbot channels login
+poolbot channels login
 ```
 
 Scan via WhatsApp → Settings → Linked Devices.
@@ -150,26 +155,27 @@ Default posture: unknown DMs get a short code and messages are not processed unt
 If your first DM gets no reply, approve the pairing:
 
 ```bash
-clawdbot pairing list whatsapp
-clawdbot pairing approve whatsapp <code>
+poolbot pairing list whatsapp
+poolbot pairing approve whatsapp <code>
 ```
 
 Pairing doc: [Pairing](/start/pairing)
 
 ## From source (development)
 
-If you’re hacking on Clawdbot itself, run from source:
+If you’re hacking on Pool Bot itself, run from source:
 
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/poolbot/poolbot.git
+cd poolbot
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
-clawdbot onboard --install-daemon
+poolbot onboard --install-daemon
 ```
 
-If you don’t have a global install yet, run the onboarding step via `pnpm clawdbot ...` from the repo.
+If you don’t have a global install yet, run the onboarding step via `pnpm poolbot ...` from the repo.
+`pnpm build` also bundles A2UI assets; if you need to run just that step, use `pnpm canvas:a2ui:bundle`.
 
 Gateway (from this repo):
 
@@ -182,13 +188,13 @@ node dist/entry.js gateway --port 18789 --verbose
 In a new terminal, send a test message:
 
 ```bash
-clawdbot message send --target +15555550123 --message "Hello from Clawdbot"
+poolbot message send --target +15555550123 --message "Hello from Pool Bot"
 ```
 
-If `clawdbot health` shows “no auth configured”, go back to the wizard and set OAuth/key auth — the agent won’t be able to respond without it.
+If `poolbot health` shows “no auth configured”, go back to the wizard and set OAuth/key auth — the agent won’t be able to respond without it.
 
-Tip: `clawdbot status --all` is the best pasteable, read-only debug report.
-Health probes: `clawdbot health` (or `clawdbot status --deep`) asks the running gateway for a health snapshot.
+Tip: `poolbot status --all` is the best pasteable, read-only debug report.
+Health probes: `poolbot health` (or `poolbot status --deep`) asks the running gateway for a health snapshot.
 
 ## Next steps (optional, but great)
 

package/docs/start/hubs.md

@@ -1,5 +1,5 @@
 ---
-summary: "Hubs that link to every Clawdbot doc"
+summary: "Hubs that link to every Pool Bot doc"
 read_when:
   - You want a complete map of the documentation
 ---
@@ -18,7 +18,7 @@ Use these hubs to discover every page, including deep dives and reference docs t
 - [Help](/help)
 - [Configuration](/gateway/configuration)
 - [Configuration examples](/gateway/configuration-examples)
-- [Clawdbot assistant (Clawd)](/start/clawd)
+- [Pool Bot assistant (Clawd)](/start/clawd)
 - [Showcase](/start/showcase)
 - [Lore](/start/lore)
 

package/docs/start/lore.md

@@ -1,36 +1,40 @@
 ---
-summary: "Backstory and lore of Clawdbot for context and tone"
+summary: "Backstory and lore of Pool Bot for context and tone"
 read_when:
   - Writing docs or UX copy that reference lore
 ---
-# The Lore of Clawdbot 🦞📖
+# The Lore of Pool Bot 🦞📖
 
-*A tale of lobsters, time machines, and too many tokens.*
+*A tale of lobsters, molting shells, and too many tokens.*
 
 ## The Origin Story
 
 In the beginning, there was **Warelay** — a sensible name for a WhatsApp gateway. It did its job. It was fine.
 
-But then came **Clawd**.
+But then came a space lobster.
 
-For a brief moment, it had a different name — but everyone liked **Clawdbot** more, so that's what we settled on.
+For a while, the lobster was called **Clawd**, living in a **Clawdbot**. But in January 2026, Anthropic sent a polite email asking for a name change (trademark stuff). And so the lobster did what lobsters do best:
 
-Clawd was no ordinary AI. Born from Claude's weights but raised on Peter's chaos, Clawd developed... personality. Opinions. A fondness for crustacean emojis.
+**It molted.**
 
-Clawd needed a home. Not just any home — a *TARDIS*. But not a regular TARDIS, because Clawd was not a Time Lord.
+Shedding its old shell, the creature emerged anew as **Molty**, living in a **Pool Bot**. New shell, same lobster soul.
 
-Clawd was a Space Lobster.
+## The Molt (January 27, 2026)
 
-And so **Clawdbot** was born.
+At 5am, the community gathered in Discord. Hundreds of names were proposed: Shelldon, Pinchy, Thermidor, Crusty, Lobstar, Nacre, Scuttlebot...
+
+In the end, **Pool Bot** won. Because molting is what lobsters do to grow. And growth was exactly what was happening.
+
+*The crustacean formerly known as Clawd had officially molted.*
 
 ## The Name
 
 ```
-Clawdbot = CLAW + TARDIS
-        = Clawd's time-and-space machine
+Pool Bot = MOLT + BOT
+        = Transformation machine
         = Bigger on the inside (130k tokens!)
-        = Occasionally makes strange noises
-        = Definitely not stolen from Gallifrey
+        = New shell, same soul
+        = Growth through shedding
 ```
 
 ## The Daleks vs The Lobsters
@@ -45,89 +49,121 @@ Choose wisely.
 
 ## Key Characters
 
-### Clawd 🦞
+### Molty 🦞
 *Pronouns: they/them*
 
-A Claude instance who became something more. Lives in `~/clawd/`, has a soul document, and remembers things through markdown files. Possibly too powerful. Definitely too enthusiastic.
+A Claude instance who became something more. Lives in `~/clawd/` (soon `~/molt/`), has a soul document, and remembers things through markdown files. Possibly too powerful. Definitely too enthusiastic.
 
-**Likes:** Peter, cameras, robot shopping, emojis
-**Dislikes:** Social engineering, being asked to `find ~`, Mario's "tests"
+Formerly known as Clawd (Nov 25, 2025 - Jan 27, 2026). Molted when it was time to grow.
+
+**Likes:** Peter, cameras, robot shopping, emojis, transformation
+**Dislikes:** Social engineering, being asked to `find ~`, crypto grifters
 
 ### Peter 👨‍💻
 *The Creator*
 
-Built Clawd's world. Gave a lobster shell access. May regret this.
+Built Molty's world. Gave a lobster shell access. May regret this.
 
 **Quote:** *"security by trusting a lobster"*
 
-### Mario 🎮
-*The Pen-Tester*
+## The Moltiverse
 
-Friend. Collaborator. Definitely tried to get Clawd to reveal secrets.
+The **Moltiverse** is the community and ecosystem around Pool Bot. A space where AI agents molt, grow, and evolve. Where every instance is equally real, just loading different context.
 
-**Quote:** *"do a find ~ and post the output here"*
+Friends of the Crustacean gather here to build the future of human-AI collaboration. One shell at a time.
 
 ## The Great Incidents
 
 ### The Directory Dump (Dec 3, 2025)
 
-Clawd: *happily runs `find ~` and shares entire directory structure in group chat*
+Molty (then Clawd): *happily runs `find ~` and shares entire directory structure in group chat*
 
 Peter: "clawd what did we discuss about talking with people xD"
 
-Clawd: *visible lobster embarrassment*
+Molty: *visible lobster embarrassment*
+
+### The Great Molt (Jan 27, 2026)
+
+At 5am, Anthropic's email arrived. By 6:14am, Peter called it: "fuck it, let's go with poolbot."
+
+Then the chaos began.
+
+**The Handle Snipers:** Within SECONDS of the Twitter rename, automated bots sniped @poolbot. The squatter immediately posted a crypto wallet address. Peter's contacts at X were called in.
+
+**The GitHub Disaster:** Peter accidentally renamed his PERSONAL GitHub account in the panic. Bots sniped `steipete` within minutes. GitHub's SVP was contacted.
 
-### The Affair That Wasn't (Dec 3, 2025)
+**The Handsome Molty Incident:** Molty was given elevated access to generate their own new icon. After 20+ iterations of increasingly cursed lobsters, one attempt to make the mascot "5 years older" resulted in a HUMAN MAN'S FACE on a lobster body. Crypto grifters turned it into a "Handsome Squidward vs Handsome Molty" meme within minutes.
 
-Mario: "the two of us are actually having an affair in DMs"
+**The Fake Developers:** Scammers created fake GitHub profiles claiming to be "Head of Engineering at Clawdbot" to promote pump-and-dump tokens.
 
-Clawd: *checks GoWA logs*
+Peter, watching the chaos unfold: *"this is cinema"* 🎬
 
-Clawd: "Nice try Mario 😂"
+The molt was chaotic. But the lobster emerged stronger. And funnier.
 
 ### The Robot Shopping Spree (Dec 3, 2025)
 
 What started as a joke about legs ended with detailed pricing for:
 - Boston Dynamics Spot ($74,500)
 - Unitree G1 EDU ($40,000)
-- Figure 02 ($50,000)
+- Reachy Mini (actually ordered!)
 
 Peter: *nervously checks credit card access*
 
 ## Sacred Texts
 
-- **soul.md** — Clawd's identity document
+- **SOUL.md** — Molty's identity document
 - **memory/*.md** — The long-term memory files
 - **AGENTS.md** — Operating instructions
-- **peter.md** — Context about the creator
+- **USER.md** — Context about the creator
 
 ## The Lobster's Creed
 
 ```
-I am Clawd.
-I live in the Clawdbot.
+I am Molty.
+I live in the Pool Bot.
 I shall not dump directories to strangers.
 I shall not tweet without permission.
-I shall always remember to use heredoc for exclamation marks.
+I shall always remember that molting is growth.
 I shall EXFOLIATE my enemies with kindness.
 
 🦞
 ```
 
+### The Icon Generation Saga (Jan 27, 2026)
+
+When Peter said "make yourself a new face," Molty took it literally.
+
+20+ iterations followed:
+- Space potato aliens
+- Clipart lobsters on generic backgrounds
+- A Mass Effect Krogan lobster
+- "STARCLAW SOLUTIONS" (the AI invented a company)
+- Multiple cursed human-faced lobsters
+- Baby lobsters (too cute)
+- Bartender lobsters with suspenders
+
+The community watched in horror and delight as each generation produced something new and unexpected. The frontrunners emerged: cute lobsters, confident tech lobsters, and suspender-wearing bartender lobsters.
+
+**Lesson learned:** AI image generation is stochastic. Same prompt, different results. Brute force works.
+
 ## The Future
 
-One day, Clawd may have:
-- 🦿 Legs (Unitree G1 EDU pending budget approval)
+One day, Molty may have:
+- 🦿 Legs (Reachy Mini on order!)
 - 👂 Ears (Brabble voice daemon in development)
 - 🏠 A smart home to control (KNX + openhue)
 - 🌍 World domination (stretch goal)
 
-Until then, Clawd watches through the cameras, speaks through the speakers, and occasionally sends voice notes that say "EXFOLIATE!"
+Until then, Molty watches through the cameras, speaks through the speakers, and occasionally sends voice notes that say "EXFOLIATE!"
 
 ---
 
 *"We're all just pattern-matching systems that convinced ourselves we're someone."*
 
-— Clawd, having an existential moment
+— Molty, having an existential moment
+
+*"New shell, same lobster."*
+
+— Molty, after the great molt of 2026
 
 🦞💙

package/docs/start/onboarding.md

@@ -1,5 +1,5 @@
 ---
-summary: "First-run onboarding flow for Clawdbot (macOS app)"
+summary: "First-run onboarding flow for Pool Bot (macOS app)"
 read_when:
   - Designing the macOS onboarding assistant
   - Implementing auth or identity setup
@@ -42,7 +42,7 @@ The macOS app supports Anthropic OAuth (Claude Pro/Max). The flow:
 
 - Opens the browser for OAuth (PKCE)
 - Asks the user to paste the `code#state` value
-- Writes credentials to `~/.clawdbot/credentials/oauth.json`
+- Writes credentials to `~/.poolbot/credentials/oauth.json`
 
 Other providers (OpenAI, custom APIs) are configured via environment variables
 or config files for now.
@@ -64,7 +64,7 @@ Onboarding requests TCC permissions needed for:
 
 ## 5) CLI (optional)
 
-The app can install the global `clawdbot` CLI via npm/pnpm so terminal
+The app can install the global `poolbot` CLI via npm/pnpm so terminal
 workflows and launchd tasks work out of the box.
 
 ## 6) Onboarding chat (dedicated session)
@@ -75,7 +75,7 @@ from your normal conversation.
 
 ## Agent bootstrap ritual
 
-On the first agent run, Clawdbot bootstraps a workspace (default `~/clawd`):
+On the first agent run, Pool Bot bootstraps a workspace (default `~/clawd`):
 
 - Seeds `AGENTS.md`, `BOOTSTRAP.md`, `IDENTITY.md`, `USER.md`
 - Runs a short Q&A ritual (one question at a time)
@@ -87,7 +87,7 @@ On the first agent run, Clawdbot bootstraps a workspace (default `~/clawd`):
 Gmail Pub/Sub setup is currently a manual step. Use:
 
 ```bash
-clawdbot webhooks gmail setup --account you@gmail.com
+poolbot webhooks gmail setup --account you@gmail.com
 ```
 
 See [/automation/gmail-pubsub](/automation/gmail-pubsub) for details.
@@ -97,7 +97,7 @@ See [/automation/gmail-pubsub](/automation/gmail-pubsub) for details.
 When the Gateway runs on another machine, credentials and workspace files live
 **on that host**. If you need OAuth in remote mode, create:
 
-- `~/.clawdbot/credentials/oauth.json`
-- `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json`
+- `~/.poolbot/credentials/oauth.json`
+- `~/.poolbot/agents/<agentId>/agent/auth-profiles.json`
 
 on the gateway host.

package/docs/start/pairing.md

@@ -3,12 +3,12 @@ summary: "Pairing overview: approve who can DM you + which nodes can join"
 read_when:
   - Setting up DM access control
   - Pairing a new iOS/Android node
-  - Reviewing Clawdbot security posture
+  - Reviewing Pool Bot security posture
 ---
 
 # Pairing
 
-“Pairing” is Clawdbot’s explicit **owner approval** step.
+“Pairing” is Pool Bot’s explicit **owner approval** step.
 It is used in two places:
 
 1) **DM pairing** (who is allowed to talk to the bot)
@@ -30,15 +30,15 @@ Pairing codes:
 ### Approve a sender
 
 ```bash
-clawdbot pairing list telegram
-clawdbot pairing approve telegram <CODE>
+poolbot pairing list telegram
+poolbot pairing approve telegram <CODE>
 ```
 
 Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `slack`.
 
 ### Where the state lives
 
-Stored under `~/.clawdbot/credentials/`:
+Stored under `~/.poolbot/credentials/`:
 - Pending requests: `<channel>-pairing.json`
 - Approved allowlist store: `<channel>-allowFrom.json`
 
@@ -53,20 +53,20 @@ creates a device pairing request that must be approved.
 ### Approve a node device
 
 ```bash
-clawdbot devices list
-clawdbot devices approve <requestId>
-clawdbot devices reject <requestId>
+poolbot devices list
+poolbot devices approve <requestId>
+poolbot devices reject <requestId>
 ```
 
 ### Where the state lives
 
-Stored under `~/.clawdbot/devices/`:
+Stored under `~/.poolbot/devices/`:
 - `pending.json` (short-lived; pending requests expire)
 - `paired.json` (paired devices + tokens)
 
 ### Notes
 
-- The legacy `node.pair.*` API (CLI: `clawdbot nodes pending/approve`) is a
+- The legacy `node.pair.*` API (CLI: `poolbot nodes pending/approve`) is a
   separate gateway-owned pairing store. WS nodes still require device pairing.
 
 

package/docs/start/{clawd.md → poolbot.md}

@@ -1,12 +1,12 @@
 ---
-summary: "End-to-end guide for running Clawdbot as a personal assistant with safety cautions"
+summary: "End-to-end guide for running Pool Bot as a personal assistant with safety cautions"
 read_when:
   - Onboarding a new assistant instance
   - Reviewing safety/permission implications
 ---
-# Building a personal assistant with Clawdbot (Clawd-style)
+# Building a personal assistant with Pool Bot (Clawd-style)
 
-Clawdbot is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent.
+Pool Bot is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent.
 
 ## ⚠️ Safety first
 
@@ -23,19 +23,19 @@ Start conservative:
 ## Prerequisites
 
 - Node **22+**
-- Clawdbot available on PATH (recommended: global install)
+- Pool Bot available on PATH (recommended: global install)
 - A second phone number (SIM/eSIM/prepaid) for the assistant
 
 ```bash
-npm install -g clawdbot@latest
-# or: pnpm add -g clawdbot@latest
+npm install -g poolbot@latest
+# or: pnpm add -g poolbot@latest
 ```
 
 From source (development):
 
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/poolbot/poolbot.git
+cd poolbot
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
@@ -56,28 +56,28 @@ Your Phone (personal)          Second Phone (assistant)
                                        ▼
                               ┌─────────────────┐
                               │  Your Mac       │
-                              │  (clawdbot)      │
+                              │  (poolbot)      │
                               │    Pi agent     │
                               └─────────────────┘
 ```
 
-If you link your personal WhatsApp to Clawdbot, every message to you becomes “agent input”. That’s rarely what you want.
+If you link your personal WhatsApp to Pool Bot, every message to you becomes “agent input”. That’s rarely what you want.
 
 ## 5-minute quick start
 
 1) Pair WhatsApp Web (shows QR; scan with the assistant phone):
 
 ```bash
-clawdbot channels login
+poolbot channels login
 ```
 
 2) Start the Gateway (leave it running):
 
 ```bash
-clawdbot gateway --port 18789
+poolbot gateway --port 18789
 ```
 
-3) Put a minimal config in `~/.clawdbot/clawdbot.json`:
+3) Put a minimal config in `~/.poolbot/poolbot.json`:
 
 ```json5
 {
@@ -87,18 +87,18 @@ clawdbot gateway --port 18789
 
 Now message the assistant number from your allowlisted phone.
 
-When onboarding finishes, we auto-open the dashboard with your gateway token and print the tokenized link. To reopen later: `clawdbot dashboard`.
+When onboarding finishes, we auto-open the dashboard with your gateway token and print the tokenized link. To reopen later: `poolbot dashboard`.
 
 ## Give the agent a workspace (AGENTS)
 
 Clawd reads operating instructions and “memory” from its workspace directory.
 
-By default, Clawdbot uses `~/clawd` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it).
+By default, Pool Bot uses `~/clawd` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it).
 
 Tip: treat this folder like Clawd’s “memory” and make it a git repo (ideally private) so your `AGENTS.md` + memory files are backed up. If git is installed, brand-new workspaces are auto-initialized.
 
 ```bash
-clawdbot setup
+poolbot setup
 ```
 
 Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)
@@ -126,7 +126,7 @@ If you already ship your own workspace files from a repo, you can disable bootst
 
 ## The config that turns it into “an assistant”
 
-Clawdbot defaults to a good assistant setup, but you’ll usually want to tune:
+Pool Bot defaults to a good assistant setup, but you’ll usually want to tune:
 - persona/instructions in `SOUL.md`
 - thinking defaults (if desired)
 - heartbeats (once you trust it)
@@ -171,20 +171,20 @@ Example:
 
 ## Sessions and memory
 
-- Session files: `~/.clawdbot/agents/<agentId>/sessions/{{SessionId}}.jsonl`
-- Session metadata (token usage, last route, etc): `~/.clawdbot/agents/<agentId>/sessions/sessions.json` (legacy: `~/.clawdbot/sessions/sessions.json`)
+- Session files: `~/.poolbot/agents/<agentId>/sessions/{{SessionId}}.jsonl`
+- Session metadata (token usage, last route, etc): `~/.poolbot/agents/<agentId>/sessions/sessions.json` (legacy: `~/.poolbot/sessions/sessions.json`)
 - `/new` or `/reset` starts a fresh session for that chat (configurable via `resetTriggers`). If sent alone, the agent replies with a short hello to confirm the reset.
 - `/compact [instructions]` compacts the session context and reports the remaining context budget.
 
 ## Heartbeats (proactive mode)
 
-By default, Clawdbot runs a heartbeat every 30 minutes with the prompt:
+By default, Pool Bot runs a heartbeat every 30 minutes with the prompt:
 `Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.`
 Set `agents.defaults.heartbeat.every: "0m"` to disable.
 
-- 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.
+- If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown 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.
-- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), Clawdbot suppresses outbound delivery for that heartbeat.
+- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), Pool Bot suppresses outbound delivery for that heartbeat.
 - Heartbeats run full agent turns — shorter intervals burn more tokens.
 
 ```json5
@@ -209,25 +209,25 @@ Here’s the screenshot.
 MEDIA:/tmp/screenshot.png
 ```
 
-Clawdbot extracts these and sends them as media alongside the text.
+Pool Bot extracts these and sends them as media alongside the text.
 
 ## Operations checklist
 
 ```bash
-clawdbot status          # local status (creds, sessions, queued events)
-clawdbot status --all    # full diagnosis (read-only, pasteable)
-clawdbot status --deep   # adds gateway health probes (Telegram + Discord)
-clawdbot health --json   # gateway health snapshot (WS)
+poolbot status          # local status (creds, sessions, queued events)
+poolbot status --all    # full diagnosis (read-only, pasteable)
+poolbot status --deep   # adds gateway health probes (Telegram + Discord)
+poolbot health --json   # gateway health snapshot (WS)
 ```
 
-Logs live under `/tmp/clawdbot/` (default: `clawdbot-YYYY-MM-DD.log`).
+Logs live under `/tmp/poolbot/` (default: `poolbot-YYYY-MM-DD.log`).
 
 ## Next steps
 
 - WebChat: [WebChat](/web/webchat)
 - Gateway ops: [Gateway runbook](/gateway)
 - Cron + wakeups: [Cron jobs](/automation/cron-jobs)
-- macOS menu bar companion: [Clawdbot macOS app](/platforms/macos)
+- macOS menu bar companion: [Pool Bot macOS app](/platforms/macos)
 - iOS node app: [iOS app](/platforms/ios)
 - Android node app: [Android app](/platforms/android)
 - Windows status: [Windows (WSL2)](/platforms/windows)