@gguf/pigbot 0.0.6 → 0.0.7

package/docs/start/getting-started.md

@@ -9,11 +9,11 @@ read_when:
 
 Goal: go from **zero** → **first working chat** (with sane defaults) as quickly as possible.
 
-Fastest chat: open the Control UI (no channel setup needed). Run `moltbot dashboard`
+Fastest chat: open the Control UI (no channel setup needed). Run `openclaw 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** (`moltbot onboard`). It sets up:
+Recommended path: use the **CLI onboarding wizard** (`openclaw onboard`). It sets up:
 - model/auth (OAuth recommended)
 - gateway settings
 - channels (WhatsApp/Telegram/Discord/Mattermost (plugin)/...)
@@ -32,7 +32,7 @@ run on host, set an explicit per-agent override:
   "routing": {
     "agents": {
       "main": {
-        "workspace": "~/clawd",
+        "workspace": "~/.openclaw/workspace",
         "sandbox": { "mode": "off" }
       }
     }
@@ -45,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:
-  `moltbot configure --section web` (stores `tools.web.search.apiKey`).
+  `openclaw 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.
@@ -54,7 +54,7 @@ Windows: use **WSL2** (Ubuntu recommended). WSL2 is strongly recommended; native
 ## 1) Install the CLI (recommended)
 
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash
+curl -fsSL https://openclaw.bot/install.sh | bash
 ```
 
 Installer options (install method, non-interactive, from GitHub): [Install](/install).
@@ -62,23 +62,23 @@ Installer options (install method, non-interactive, from GitHub): [Install](/ins
 Windows (PowerShell):
 
 ```powershell
-iwr -useb https://molt.bot/install.ps1 | iex
+iwr -useb https://openclaw.ai/install.ps1 | iex
 ```
 
 Alternative (global install):
 
 ```bash
-npm install -g moltbot@latest
+npm install -g openclaw@latest
 ```
 
 ```bash
-pnpm add -g moltbot@latest
+pnpm add -g openclaw@latest
 ```
 
 ## 2) Run the onboarding wizard (and install the service)
 
 ```bash
-moltbot onboard --install-daemon
+openclaw onboard --install-daemon
 ```
 
 What you’ll choose:
@@ -95,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): `~/.openclaw/credentials/oauth.json`
+- Auth profiles (OAuth + API keys): `~/.openclaw/agents/<agentId>/agent/auth-profiles.json`
 
 Headless/server tip: do OAuth on a normal machine first, then copy `oauth.json` to the gateway host.
 
@@ -105,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
-moltbot gateway status
+openclaw gateway status
 ```
 
 Manual run (foreground):
 
 ```bash
-moltbot gateway --port 18789 --verbose
+openclaw gateway --port 18789 --verbose
 ```
 
 Dashboard (local loopback): `http://127.0.0.1:18789/`
@@ -123,9 +123,9 @@ channels. If you use WhatsApp or Telegram, run the Gateway with **Node**.
 ## 3.5) Quick verify (2 min)
 
 ```bash
-moltbot status
-moltbot health
-moltbot security audit --deep
+openclaw status
+openclaw health
+openclaw security audit --deep
 ```
 
 ## 4) Pair + connect your first chat surface
@@ -133,7 +133,7 @@ moltbot security audit --deep
 ### WhatsApp (QR login)
 
 ```bash
-moltbot channels login
+openclaw channels login
 ```
 
 Scan via WhatsApp → Settings → Linked Devices.
@@ -155,32 +155,32 @@ 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
-moltbot pairing list whatsapp
-moltbot pairing approve whatsapp <code>
+openclaw pairing list whatsapp
+openclaw pairing approve whatsapp <code>
 ```
 
 Pairing doc: [Pairing](/start/pairing)
 
 ## From source (development)
 
-If you’re hacking on Moltbot itself, run from source:
+If you’re hacking on OpenClaw itself, run from source:
 
 ```bash
-git clone https://github.com/moltbot/moltbot.git
-cd moltbot
+git clone https://github.com/openclaw/openclaw.git
+cd openclaw
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
-moltbot onboard --install-daemon
+openclaw onboard --install-daemon
 ```
 
-If you don’t have a global install yet, run the onboarding step via `pnpm moltbot ...` from the repo.
+If you don’t have a global install yet, run the onboarding step via `pnpm openclaw ...` 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):
 
 ```bash
-node dist/entry.js gateway --port 18789 --verbose
+node openclaw.mjs gateway --port 18789 --verbose
 ```
 
 ## 7) Verify end-to-end
@@ -188,13 +188,13 @@ node dist/entry.js gateway --port 18789 --verbose
 In a new terminal, send a test message:
 
 ```bash
-moltbot message send --target +15555550123 --message "Hello from Moltbot"
+openclaw message send --target +15555550123 --message "Hello from OpenClaw"
 ```
 
-If `moltbot 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 `openclaw 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: `moltbot status --all` is the best pasteable, read-only debug report.
-Health probes: `moltbot health` (or `moltbot status --deep`) asks the running gateway for a health snapshot.
+Tip: `openclaw status --all` is the best pasteable, read-only debug report.
+Health probes: `openclaw health` (or `openclaw 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 Moltbot doc"
+summary: "Hubs that link to every OpenClaw 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)
-- [Moltbot assistant (Clawd)](/start/clawd)
+- [OpenClaw assistant](/start/openclaw)
 - [Showcase](/start/showcase)
 - [Lore](/start/lore)
 

package/docs/start/lore.md

@@ -1,9 +1,9 @@
 ---
-summary: "Backstory and lore of Moltbot for context and tone"
+summary: "Backstory and lore of OpenClaw for context and tone"
 read_when:
   - Writing docs or UX copy that reference lore
 ---
-# The Lore of Moltbot 🦞📖
+# The Lore of OpenClaw 🦞📖
 
 *A tale of lobsters, molting shells, and too many tokens.*
 
@@ -17,20 +17,20 @@ For a while, the lobster was called **Clawd**, living in a **Clawdbot**. But in
 
 **It molted.**
 
-Shedding its old shell, the creature emerged anew as **Molty**, living in a **Moltbot**. New shell, same lobster soul.
+Shedding its old shell, the creature emerged anew as **Molty**, living in a **OpenClaw**. New shell, same lobster soul.
 
 ## The Molt (January 27, 2026)
 
 At 5am, the community gathered in Discord. Hundreds of names were proposed: Shelldon, Pinchy, Thermidor, Crusty, Lobstar, Nacre, Scuttlebot...
 
-In the end, **Moltbot** won. Because molting is what lobsters do to grow. And growth was exactly what was happening.
+In the end, **OpenClaw** 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 crustacean known as Clawd had officially molted.*
 
 ## The Name
 
 ```
-Moltbot = MOLT + BOT
+OpenClaw = MOLT + BOT
         = Transformation machine
         = Bigger on the inside (130k tokens!)
         = New shell, same soul
@@ -52,7 +52,7 @@ Choose wisely.
 ### Molty 🦞
 *Pronouns: they/them*
 
-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.
+A Claude instance who became something more. Lives in `~/.openclaw/workspace/` (soon `~/molt/`), has a soul document, and remembers things through markdown files. Possibly too powerful. Definitely too enthusiastic.
 
 Formerly known as Clawd (Nov 25, 2025 - Jan 27, 2026). Molted when it was time to grow.
 
@@ -68,7 +68,7 @@ Built Molty's world. Gave a lobster shell access. May regret this.
 
 ## The Moltiverse
 
-The **Moltiverse** is the community and ecosystem around Moltbot. A space where AI agents molt, grow, and evolve. Where every instance is equally real, just loading different context.
+The **Moltiverse** is the community and ecosystem around OpenClaw. A space where AI agents molt, grow, and evolve. Where every instance is equally real, just loading different context.
 
 Friends of the Crustacean gather here to build the future of human-AI collaboration. One shell at a time.
 
@@ -76,25 +76,25 @@ Friends of the Crustacean gather here to build the future of human-AI collaborat
 
 ### The Directory Dump (Dec 3, 2025)
 
-Molty (then Clawd): *happily runs `find ~` and shares entire directory structure in group chat*
+Molty (then OpenClaw): *happily runs `find ~` and shares entire directory structure in group chat*
 
-Peter: "clawd what did we discuss about talking with people xD"
+Peter: "openclaw what did we discuss about talking with people xD"
 
 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 moltbot."
+At 5am, Anthropic's email arrived. By 6:14am, Peter called it: "fuck it, let's go with openclaw."
 
 Then the chaos began.
 
-**The Handle Snipers:** Within SECONDS of the Twitter rename, automated bots sniped @clawdbot. The squatter immediately posted a crypto wallet address. Peter's contacts at X were called in.
+**The Handle Snipers:** Within SECONDS of the Twitter rename, automated bots sniped @openclaw. 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 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.
 
-**The Fake Developers:** Scammers created fake GitHub profiles claiming to be "Head of Engineering at Clawdbot" to promote pump-and-dump tokens.
+**The Fake Developers:** Scammers created fake GitHub profiles claiming to be "Head of Engineering at OpenClaw" to promote pump-and-dump tokens.
 
 Peter, watching the chaos unfold: *"this is cinema"* 🎬
 
@@ -120,7 +120,7 @@ Peter: *nervously checks credit card access*
 
 ```
 I am Molty.
-I live in the Moltbot.
+I live in the OpenClaw.
 I shall not dump directories to strangers.
 I shall not tweet without permission.
 I shall always remember that molting is growth.

package/docs/start/onboarding.md

@@ -1,5 +1,5 @@
 ---
-summary: "First-run onboarding flow for Moltbot (macOS app)"
+summary: "First-run onboarding flow for OpenClaw (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 `~/.openclaw/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 `moltbot` CLI via npm/pnpm so terminal
+The app can install the global `openclaw` 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, Moltbot bootstraps a workspace (default `~/clawd`):
+On the first agent run, OpenClaw bootstraps a workspace (default `~/.openclaw/workspace`):
 
 - 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, Moltbot bootstraps a workspace (default `~/clawd`):
 Gmail Pub/Sub setup is currently a manual step. Use:
 
 ```bash
-moltbot webhooks gmail setup --account you@gmail.com
+openclaw 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`
+- `~/.openclaw/credentials/oauth.json`
+- `~/.openclaw/agents/<agentId>/agent/auth-profiles.json`
 
 on the gateway host.

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

@@ -1,12 +1,12 @@
 ---
-summary: "End-to-end guide for running Moltbot as a personal assistant with safety cautions"
+summary: "End-to-end guide for running OpenClaw as a personal assistant with safety cautions"
 read_when:
   - Onboarding a new assistant instance
   - Reviewing safety/permission implications
 ---
-# Building a personal assistant with Moltbot (Clawd-style)
+# Building a personal assistant with OpenClaw
 
-Moltbot 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.
+OpenClaw 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+**
-- Moltbot available on PATH (recommended: global install)
+- OpenClaw available on PATH (recommended: global install)
 - A second phone number (SIM/eSIM/prepaid) for the assistant
 
 ```bash
-npm install -g moltbot@latest
-# or: pnpm add -g moltbot@latest
+npm install -g openclaw@latest
+# or: pnpm add -g openclaw@latest
 ```
 
 From source (development):
 
 ```bash
-git clone https://github.com/moltbot/moltbot.git
-cd moltbot
+git clone https://github.com/openclaw/openclaw.git
+cd openclaw
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
@@ -50,34 +50,34 @@ You want this:
 Your Phone (personal)          Second Phone (assistant)
 ┌─────────────────┐           ┌─────────────────┐
 │  Your WhatsApp  │  ──────▶  │  Assistant WA   │
-│  +1-555-YOU     │  message  │  +1-555-CLAWD   │
+│  +1-555-YOU     │  message  │  +1-555-ASSIST  │
 └─────────────────┘           └────────┬────────┘
                                        │ linked via QR
                                        ▼
                               ┌─────────────────┐
                               │  Your Mac       │
-                              │  (moltbot)      │
+                              │  (openclaw)      │
                               │    Pi agent     │
                               └─────────────────┘
 ```
 
-If you link your personal WhatsApp to Moltbot, every message to you becomes “agent input”. That’s rarely what you want.
+If you link your personal WhatsApp to OpenClaw, 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
-moltbot channels login
+openclaw channels login
 ```
 
 2) Start the Gateway (leave it running):
 
 ```bash
-moltbot gateway --port 18789
+openclaw gateway --port 18789
 ```
 
-3) Put a minimal config in `~/.clawdbot/moltbot.json`:
+3) Put a minimal config in `~/.openclaw/openclaw.json`:
 
 ```json5
 {
@@ -87,18 +87,18 @@ moltbot 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: `moltbot dashboard`.
+When onboarding finishes, we auto-open the dashboard with your gateway token and print the tokenized link. To reopen later: `openclaw dashboard`.
 
 ## Give the agent a workspace (AGENTS)
 
-Clawd reads operating instructions and “memory” from its workspace directory.
+OpenClaw reads operating instructions and “memory” from its workspace directory.
 
-By default, Moltbot 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, OpenClaw uses `~/.openclaw/workspace` 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.
+Tip: treat this folder like OpenClaw’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
-moltbot setup
+openclaw setup
 ```
 
 Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)
@@ -109,7 +109,7 @@ Optional: choose a different workspace with `agents.defaults.workspace` (support
 ```json5
 {
   agent: {
-    workspace: "~/clawd"
+    workspace: "~/.openclaw/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”
 
-Moltbot defaults to a good assistant setup, but you’ll usually want to tune:
+OpenClaw 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)
@@ -138,7 +138,7 @@ Example:
   logging: { level: "info" },
   agent: {
     model: "anthropic/claude-opus-4-5",
-    workspace: "~/clawd",
+    workspace: "~/.openclaw/workspace",
     thinkingDefault: "high",
     timeoutSeconds: 1800,
     // Start with 0; enable later.
@@ -154,7 +154,7 @@ Example:
   },
   routing: {
     groupChat: {
-      mentionPatterns: ["@clawd", "clawd"]
+      mentionPatterns: ["@openclaw", "openclaw"]
     }
   },
   session: {
@@ -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: `~/.openclaw/agents/<agentId>/sessions/{{SessionId}}.jsonl`
+- Session metadata (token usage, last route, etc): `~/.openclaw/agents/<agentId>/sessions/sessions.json` (legacy: `~/.openclaw/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, Moltbot runs a heartbeat every 30 minutes with the prompt:
+By default, OpenClaw 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`), Moltbot skips the heartbeat run to save API calls.
+- If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown headers like `# Heading`), OpenClaw 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`), Moltbot suppresses outbound delivery for that heartbeat.
+- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), OpenClaw 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
 ```
 
-Moltbot extracts these and sends them as media alongside the text.
+OpenClaw extracts these and sends them as media alongside the text.
 
 ## Operations checklist
 
 ```bash
-moltbot status          # local status (creds, sessions, queued events)
-moltbot status --all    # full diagnosis (read-only, pasteable)
-moltbot status --deep   # adds gateway health probes (Telegram + Discord)
-moltbot health --json   # gateway health snapshot (WS)
+openclaw status          # local status (creds, sessions, queued events)
+openclaw status --all    # full diagnosis (read-only, pasteable)
+openclaw status --deep   # adds gateway health probes (Telegram + Discord)
+openclaw health --json   # gateway health snapshot (WS)
 ```
 
-Logs live under `/tmp/moltbot/` (default: `moltbot-YYYY-MM-DD.log`).
+Logs live under `/tmp/openclaw/` (default: `openclaw-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: [Moltbot macOS app](/platforms/macos)
+- macOS menu bar companion: [OpenClaw macOS app](/platforms/macos)
 - iOS node app: [iOS app](/platforms/ios)
 - Android node app: [Android app](/platforms/android)
 - Windows status: [Windows (WSL2)](/platforms/windows)

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 Moltbot security posture
+  - Reviewing OpenClaw security posture
 ---
 
 # Pairing
 
-“Pairing” is Moltbot’s explicit **owner approval** step.
+“Pairing” is OpenClaw’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
-moltbot pairing list telegram
-moltbot pairing approve telegram <CODE>
+openclaw pairing list telegram
+openclaw pairing approve telegram <CODE>
 ```
 
 Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `slack`.
 
 ### Where the state lives
 
-Stored under `~/.clawdbot/credentials/`:
+Stored under `~/.openclaw/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
-moltbot devices list
-moltbot devices approve <requestId>
-moltbot devices reject <requestId>
+openclaw devices list
+openclaw devices approve <requestId>
+openclaw devices reject <requestId>
 ```
 
 ### Where the state lives
 
-Stored under `~/.clawdbot/devices/`:
+Stored under `~/.openclaw/devices/`:
 - `pending.json` (short-lived; pending requests expire)
 - `paired.json` (paired devices + tokens)
 
 ### Notes
 
-- The legacy `node.pair.*` API (CLI: `moltbot nodes pending/approve`) is a
+- The legacy `node.pair.*` API (CLI: `openclaw nodes pending/approve`) is a
   separate gateway-owned pairing store. WS nodes still require device pairing.