refactor: rename clawdbot to moltbot with legacy compat

docs/platforms/android.md

@@ -31,12 +31,12 @@ Android connects directly to the Gateway WebSocket (default `ws://<host>:18789`)
   - Same LAN with mDNS/NSD, **or**
   - Same Tailscale tailnet using Wide-Area Bonjour / unicast DNS-SD (see below), **or**
   - Manual gateway host/port (fallback)
-- You can run the CLI (`clawdbot`) on the gateway machine (or via SSH).
+- You can run the CLI (`moltbot`) on the gateway machine (or via SSH).
 
 ### 1) Start the Gateway
 
 ```bash
-clawdbot gateway --port 18789 --verbose
+moltbot gateway --port 18789 --verbose
 ```
 
 Confirm in logs you see something like:
@@ -44,7 +44,7 @@ Confirm in logs you see something like:
 
 For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to the tailnet IP:
 
-- Set `gateway.bind: "tailnet"` in `~/.clawdbot/clawdbot.json` on the gateway host.
+- Set `gateway.bind: "tailnet"` in `~/.clawdbot/moltbot.json` on the gateway host.
 - Restart the Gateway / macOS menubar app.
 
 ### 2) Verify discovery (optional)
@@ -52,7 +52,7 @@ For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to
 From the gateway machine:
 
 ```bash
-dns-sd -B _clawdbot-gw._tcp local.
+dns-sd -B _moltbot-gw._tcp local.
 ```
 
 More debugging notes: [Bonjour](/gateway/bonjour).
@@ -61,8 +61,8 @@ More debugging notes: [Bonjour](/gateway/bonjour).
 
 Android NSD/mDNS discovery won’t cross networks. If your Android node and the gateway are on different networks but connected via Tailscale, use Wide-Area Bonjour / unicast DNS-SD instead:
 
-1) Set up a DNS-SD zone (example `clawdbot.internal.`) on the gateway host and publish `_clawdbot-gw._tcp` records.
-2) Configure Tailscale split DNS for `clawdbot.internal` pointing at that DNS server.
+1) Set up a DNS-SD zone (example `moltbot.internal.`) on the gateway host and publish `_moltbot-gw._tcp` records.
+2) Configure Tailscale split DNS for `moltbot.internal` pointing at that DNS server.
 
 Details and example CoreDNS config: [Bonjour](/gateway/bonjour).
 
@@ -84,8 +84,8 @@ After the first successful pairing, Android auto-reconnects on launch:
 On the gateway machine:
 
 ```bash
-clawdbot nodes pending
-clawdbot nodes approve <requestId>
+moltbot nodes pending
+moltbot nodes approve <requestId>
 ```
 
 Pairing details: [Gateway pairing](/gateway/pairing).
@@ -94,11 +94,11 @@ Pairing details: [Gateway pairing](/gateway/pairing).
 
 - Via nodes status:
   ```bash
-  clawdbot nodes status
+  moltbot nodes status
   ```
 - Via Gateway:
   ```bash
-  clawdbot gateway call node.list --params "{}"
+  moltbot gateway call node.list --params "{}"
   ```
 
 ### 6) Chat + history
@@ -122,13 +122,13 @@ Note: nodes use the standalone canvas host on `canvasHost.port` (default `18793`
 2) Navigate the node to it (LAN):
 
 ```bash
-clawdbot nodes invoke --node "<Android Node>" --command canvas.navigate --params '{"url":"http://<gateway-hostname>.local:18793/__clawdbot__/canvas/"}'
+moltbot nodes invoke --node "<Android Node>" --command canvas.navigate --params '{"url":"http://<gateway-hostname>.local:18793/__moltbot__/canvas/"}'
 ```
 
-Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://<gateway-magicdns>:18793/__clawdbot__/canvas/`.
+Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://<gateway-magicdns>:18793/__moltbot__/canvas/`.
 
 This server injects a live-reload client into HTML and reloads on file changes.
-The A2UI host lives at `http://<gateway-host>:18793/__clawdbot__/a2ui/`.
+The A2UI host lives at `http://<gateway-host>:18793/__moltbot__/a2ui/`.
 
 Canvas commands (foreground only):
 - `canvas.eval`, `canvas.snapshot`, `canvas.navigate` (use `{"url":""}` or `{"url":"/"}` to return to the default scaffold). `canvas.snapshot` returns `{ format, base64 }` (default `format="jpeg"`).

docs/platforms/digitalocean.md

@@ -1,15 +1,15 @@
 ---
-summary: "Clawdbot on DigitalOcean (simple paid VPS option)"
+summary: "Moltbot on DigitalOcean (simple paid VPS option)"
 read_when:
-  - Setting up Clawdbot on DigitalOcean
-  - Looking for cheap VPS hosting for Clawdbot
+  - Setting up Moltbot on DigitalOcean
+  - Looking for cheap VPS hosting for Moltbot
 ---
 
-# Clawdbot on DigitalOcean
+# Moltbot on DigitalOcean
 
 ## Goal
 
-Run a persistent Clawdbot Gateway on DigitalOcean for **$6/month** (or $4/mo with reserved pricing).
+Run a persistent Moltbot Gateway on DigitalOcean for **$6/month** (or $4/mo with reserved pricing).
 
 If you want a $0/month option and don’t mind ARM + provider-specific setup, see the [Oracle Cloud guide](/platforms/oracle).
 
@@ -54,7 +54,7 @@ If you want a $0/month option and don’t mind ARM + provider-specific setup, se
 ssh root@YOUR_DROPLET_IP
 ```
 
-## 3) Install Clawdbot
+## 3) Install Moltbot
 
 ```bash
 # Update system
@@ -64,17 +64,17 @@ apt update && apt upgrade -y
 curl -fsSL https://deb.nodesource.com/setup_22.x | bash -
 apt install -y nodejs
 
-# Install Clawdbot
+# Install Moltbot
 curl -fsSL https://molt.bot/install.sh | bash
 
 # Verify
-clawdbot --version
+moltbot --version
 ```
 
 ## 4) Run Onboarding
 
 ```bash
-clawdbot onboard --install-daemon
+moltbot onboard --install-daemon
 ```
 
 The wizard will walk you through:
@@ -87,13 +87,13 @@ The wizard will walk you through:
 
 ```bash
 # Check status
-clawdbot status
+moltbot status
 
 # Check service
-systemctl --user status clawdbot-gateway.service
+systemctl --user status moltbot-gateway.service
 
 # View logs
-journalctl --user -u clawdbot-gateway.service -f
+journalctl --user -u moltbot-gateway.service -f
 ```
 
 ## 6) Access the Dashboard
@@ -115,8 +115,8 @@ curl -fsSL https://tailscale.com/install.sh | sh
 tailscale up
 
 # Configure Gateway to use Tailscale Serve
-clawdbot config set gateway.tailscale.mode serve
-clawdbot gateway restart
+moltbot config set gateway.tailscale.mode serve
+moltbot gateway restart
 ```
 
 Open: `https://<magicdns>/`
@@ -127,8 +127,8 @@ Notes:
 
 **Option C: Tailnet bind (no Serve)**
 ```bash
-clawdbot config set gateway.bind tailnet
-clawdbot gateway restart
+moltbot config set gateway.bind tailnet
+moltbot gateway restart
 ```
 
 Open: `http://<tailscale-ip>:18789` (token required).
@@ -137,13 +137,13 @@ Open: `http://<tailscale-ip>:18789` (token required).
 
 ### Telegram
 ```bash
-clawdbot pairing list telegram
-clawdbot pairing approve telegram <CODE>
+moltbot pairing list telegram
+moltbot pairing approve telegram <CODE>
 ```
 
 ### WhatsApp
 ```bash
-clawdbot channels login whatsapp
+moltbot channels login whatsapp
 # Scan QR code
 ```
 
@@ -185,7 +185,7 @@ All state lives in:
 
 These survive reboots. Back them up periodically:
 ```bash
-tar -czvf clawdbot-backup.tar.gz ~/.clawdbot ~/clawd
+tar -czvf moltbot-backup.tar.gz ~/.clawdbot ~/clawd
 ```
 
 ---
@@ -213,9 +213,9 @@ For the full setup guide, see [Oracle Cloud](/platforms/oracle). For signup tips
 
 ### Gateway won't start
 ```bash
-clawdbot gateway status
-clawdbot doctor --non-interactive
-journalctl -u clawdbot --no-pager -n 50
+moltbot gateway status
+moltbot doctor --non-interactive
+journalctl -u moltbot --no-pager -n 50
 ```
 
 ### Port already in use

docs/platforms/exe-dev.md

@@ -1,5 +1,5 @@
 ---
-summary: "Run Clawdbot Gateway on exe.dev (VM + HTTPS proxy) for remote access"
+summary: "Run Moltbot Gateway on exe.dev (VM + HTTPS proxy) for remote access"
 read_when:
   - You want a cheap always-on Linux host for the Gateway
   - You want remote Control UI access without running your own VPS
@@ -7,7 +7,7 @@ read_when:
 
 # exe.dev
 
-Goal: Clawdbot Gateway running on an exe.dev VM, reachable from your laptop via:
+Goal: Moltbot Gateway running on an exe.dev VM, reachable from your laptop via:
 - **exe.dev HTTPS proxy** (easy, no tunnel) or
 - **SSH tunnel** (most secure; loopback-only Gateway)
 
@@ -17,8 +17,8 @@ If you’re on any other Linux VPS, the same steps apply — you just won’t us
 
 ## Beginner quick path
 
-1) Create VM → install Node 22 → install Clawdbot  
-2) Run `clawdbot onboard --install-daemon`  
+1) Create VM → install Node 22 → install Moltbot  
+2) Run `moltbot onboard --install-daemon`  
 3) Tunnel from laptop (`ssh -N -L 18789:127.0.0.1:18789 …`)  
 4) Open `http://127.0.0.1:18789/` and paste your token
 
@@ -34,16 +34,16 @@ If you’re on any other Linux VPS, the same steps apply — you just won’t us
 From your laptop:
 
 ```bash
-ssh exe.dev new --name=clawdbot
+ssh exe.dev new --name=moltbot
 ```
 
 Then connect:
 
 ```bash
-ssh clawdbot.exe.xyz
+ssh moltbot.exe.xyz
 ```
 
-Tip: keep this VM **stateful**. Clawdbot stores state under `~/.clawdbot/` and `~/clawd/`.
+Tip: keep this VM **stateful**. Moltbot stores state under `~/.clawdbot/` and `~/clawd/`.
 
 ## 2) Install prerequisites (on the VM)
 
@@ -69,13 +69,13 @@ curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
 sudo apt-get install -y nodejs
 ```
 
-## 3) Install Clawdbot
+## 3) Install Moltbot
 
 Recommended on servers: npm global install.
 
 ```bash
-npm i -g clawdbot@latest
-clawdbot --version
+npm i -g moltbot@latest
+moltbot --version
 ```
 
 If native deps fail to install (rare; usually `sharp`), add build tools:
@@ -89,12 +89,12 @@ sudo apt-get install -y build-essential python3
 Run the onboarding wizard on the VM:
 
 ```bash
-clawdbot onboard --install-daemon
+moltbot onboard --install-daemon
 ```
 
 It can set up:
 - `~/clawd` workspace bootstrap
-- `~/.clawdbot/clawdbot.json` config
+- `~/.clawdbot/moltbot.json` config
 - model auth profiles
 - model provider config/login
 - Linux systemd **user** service (service)
@@ -108,7 +108,7 @@ If you’re doing OAuth on a headless VM: do OAuth on a normal machine first, th
 Keep Gateway on loopback (default) and tunnel it from your laptop:
 
 ```bash
-ssh -N -L 18789:127.0.0.1:18789 clawdbot.exe.xyz
+ssh -N -L 18789:127.0.0.1:18789 moltbot.exe.xyz
 ```
 
 Open locally:
@@ -122,10 +122,10 @@ To let exe.dev proxy traffic to the VM, bind the Gateway to the LAN interface an
 
 ```bash
 export CLAWDBOT_GATEWAY_TOKEN="$(openssl rand -hex 32)"
-clawdbot gateway --bind lan --port 8080 --token "$CLAWDBOT_GATEWAY_TOKEN"
+moltbot gateway --bind lan --port 8080 --token "$CLAWDBOT_GATEWAY_TOKEN"
 ```
 
-For service runs, persist it in `~/.clawdbot/clawdbot.json`:
+For service runs, persist it in `~/.clawdbot/moltbot.json`:
 
 ```json5
 {
@@ -145,11 +145,11 @@ Notes:
 Then point exe.dev’s proxy at `8080` (or whatever port you chose) and open your VM’s HTTPS URL:
 
 ```bash
-ssh exe.dev share port clawdbot 8080
+ssh exe.dev share port moltbot 8080
 ```
 
 Open:
-- `https://clawdbot.exe.xyz/`
+- `https://moltbot.exe.xyz/`
 
 In the Control UI, paste the token (UI → Settings → token). The UI sends it as `connect.params.auth.token`.
 
@@ -161,10 +161,10 @@ Control UI details: [Control UI](/web/control-ui)
 
 ## 6) Keep it running (service)
 
-On Linux, Clawdbot uses a systemd **user** service. After `--install-daemon`, verify:
+On Linux, Moltbot uses a systemd **user** service. After `--install-daemon`, verify:
 
 ```bash
-systemctl --user status clawdbot-gateway[-<profile>].service
+systemctl --user status moltbot-gateway[-<profile>].service
 ```
 
 If the service dies after logout, enable lingering:
@@ -178,10 +178,10 @@ More: [Linux](/platforms/linux)
 ## 7) Updates
 
 ```bash
-npm i -g clawdbot@latest
-clawdbot doctor
-clawdbot gateway restart
-clawdbot health
+npm i -g moltbot@latest
+moltbot doctor
+moltbot gateway restart
+moltbot health
 ```
 
 Guide: [Updating](/install/updating)

docs/platforms/fly.md

@@ -1,11 +1,11 @@
 ---
 title: Fly.io
-description: Deploy Clawdbot on Fly.io
+description: Deploy Moltbot on Fly.io
 ---
 
 # Fly.io Deployment
 
-**Goal:** Clawdbot Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access.
+**Goal:** Moltbot Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access.
 
 ## What you need
 
@@ -25,14 +25,14 @@ description: Deploy Clawdbot on Fly.io
 
 ```bash
 # Clone the repo
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/moltbot/moltbot.git
+cd moltbot
 
 # Create a new Fly app (pick your own name)
-fly apps create my-clawdbot
+fly apps create my-moltbot
 
 # Create a persistent volume (1GB is usually enough)
-fly volumes create clawdbot_data --size 1 --region iad
+fly volumes create moltbot_data --size 1 --region iad
 ```
 
 **Tip:** Choose a region close to you. Common options: `lhr` (London), `iad` (Virginia), `sjc` (San Jose).
@@ -44,7 +44,7 @@ Edit `fly.toml` to match your app name and requirements.
 **Security note:** The default config exposes a public URL. For a hardened deployment with no public IP, see [Private Deployment](#private-deployment-hardened) or use `fly.private.toml`.
 
 ```toml
-app = "my-clawdbot"  # Your app name
+app = "my-moltbot"  # Your app name
 primary_region = "iad"
 
 [build]
@@ -72,7 +72,7 @@ primary_region = "iad"
   memory = "2048mb"
 
 [mounts]
-  source = "clawdbot_data"
+  source = "moltbot_data"
   destination = "/data"
 ```
 
@@ -106,7 +106,7 @@ fly secrets set DISCORD_BOT_TOKEN=MTQ...
 **Notes:**
 - Non-loopback binds (`--bind lan`) require `CLAWDBOT_GATEWAY_TOKEN` for security.
 - Treat these tokens like passwords.
-- **Prefer env vars over config file** for all API keys and tokens. This keeps secrets out of `clawdbot.json` where they could be accidentally exposed or logged.
+- **Prefer env vars over config file** for all API keys and tokens. This keeps secrets out of `moltbot.json` where they could be accidentally exposed or logged.
 
 ## 4) Deploy
 
@@ -139,7 +139,7 @@ fly ssh console
 Create the config directory and file:
 ```bash
 mkdir -p /data
-cat > /data/clawdbot.json << 'EOF'
+cat > /data/moltbot.json << 'EOF'
 {
   "agents": {
     "defaults": {
@@ -191,7 +191,7 @@ cat > /data/clawdbot.json << 'EOF'
 EOF
 ```
 
-**Note:** With `CLAWDBOT_STATE_DIR=/data`, the config path is `/data/clawdbot.json`.
+**Note:** With `CLAWDBOT_STATE_DIR=/data`, the config path is `/data/moltbot.json`.
 
 **Note:** The Discord token can come from either:
 - Environment variable: `DISCORD_BOT_TOKEN` (recommended for secrets)
@@ -214,7 +214,7 @@ Open in browser:
 fly open
 ```
 
-Or visit `https://my-clawdbot.fly.dev/`
+Or visit `https://my-moltbot.fly.dev/`
 
 Paste your gateway token (the one from `CLAWDBOT_GATEWAY_TOKEN`) to authenticate.
 
@@ -278,11 +278,11 @@ The lock file is at `/data/gateway.*.lock` (not in a subdirectory).
 
 ### Config Not Being Read
 
-If using `--allow-unconfigured`, the gateway creates a minimal config. Your custom config at `/data/clawdbot.json` should be read on restart.
+If using `--allow-unconfigured`, the gateway creates a minimal config. Your custom config at `/data/moltbot.json` should be read on restart.
 
 Verify the config exists:
 ```bash
-fly ssh console --command "cat /data/clawdbot.json"
+fly ssh console --command "cat /data/moltbot.json"
 ```
 
 ### Writing Config via SSH
@@ -291,16 +291,16 @@ The `fly ssh console -C` command doesn't support shell redirection. To write a c
 
 ```bash
 # Use echo + tee (pipe from local to remote)
-echo '{"your":"config"}' | fly ssh console -C "tee /data/clawdbot.json"
+echo '{"your":"config"}' | fly ssh console -C "tee /data/moltbot.json"
 
 # Or use sftp
 fly sftp shell
-> put /local/path/config.json /data/clawdbot.json
+> put /local/path/config.json /data/moltbot.json
 ```
 
 **Note:** `fly sftp` may fail if the file already exists. Delete first:
 ```bash
-fly ssh console --command "rm /data/clawdbot.json"
+fly ssh console --command "rm /data/moltbot.json"
 ```
 
 ### State Not Persisting
@@ -366,18 +366,18 @@ Or convert an existing deployment:
 
 ```bash
 # List current IPs
-fly ips list -a my-clawdbot
+fly ips list -a my-moltbot
 
 # Release public IPs
-fly ips release <public-ipv4> -a my-clawdbot
-fly ips release <public-ipv6> -a my-clawdbot
+fly ips release <public-ipv4> -a my-moltbot
+fly ips release <public-ipv6> -a my-moltbot
 
 # Switch to private config so future deploys don't re-allocate public IPs
 # (remove [http_service] or deploy with the private template)
 fly deploy -c fly.private.toml
 
 # Allocate private-only IPv6
-fly ips allocate-v6 --private -a my-clawdbot
+fly ips allocate-v6 --private -a my-moltbot
 ```
 
 After this, `fly ips list` should show only a `private` type IP:
@@ -393,7 +393,7 @@ Since there's no public URL, use one of these methods:
 **Option 1: Local proxy (simplest)**
 ```bash
 # Forward local port 3000 to the app
-fly proxy 3000:3000 -a my-clawdbot
+fly proxy 3000:3000 -a my-moltbot
 
 # Then open http://localhost:3000 in browser
 ```
@@ -409,7 +409,7 @@ fly wireguard create
 
 **Option 3: SSH only**
 ```bash
-fly ssh console -a my-clawdbot
+fly ssh console -a my-moltbot
 ```
 
 ### Webhooks with private deployment

docs/platforms/gcp.md

@@ -1,18 +1,18 @@
 ---
-summary: "Run Clawdbot Gateway 24/7 on a GCP Compute Engine VM (Docker) with durable state"
+summary: "Run Moltbot Gateway 24/7 on a GCP Compute Engine VM (Docker) with durable state"
 read_when:
-  - You want Clawdbot running 24/7 on GCP
+  - You want Moltbot running 24/7 on GCP
   - You want a production-grade, always-on Gateway on your own VM
   - You want full control over persistence, binaries, and restart behavior
 ---
 
-# Clawdbot on GCP Compute Engine (Docker, Production VPS Guide)
+# Moltbot on GCP Compute Engine (Docker, Production VPS Guide)
 
 ## Goal
 
-Run a persistent Clawdbot Gateway on a GCP Compute Engine VM using Docker, with durable state, baked-in binaries, and safe restart behavior.
+Run a persistent Moltbot Gateway on a GCP Compute Engine VM using Docker, with durable state, baked-in binaries, and safe restart behavior.
 
-If you want "Clawdbot 24/7 for ~$5-12/mo", this is a reliable setup on Google Cloud.
+If you want "Moltbot 24/7 for ~$5-12/mo", this is a reliable setup on Google Cloud.
 Pricing varies by machine type and region; pick the smallest VM that fits your workload and scale up if you hit OOMs.
 
 ## What are we doing (simple terms)?
@@ -20,7 +20,7 @@ Pricing varies by machine type and region; pick the smallest VM that fits your w
 - Create a GCP project and enable billing
 - Create a Compute Engine VM
 - Install Docker (isolated app runtime)
-- Start the Clawdbot Gateway in Docker
+- Start the Moltbot Gateway in Docker
 - Persist `~/.clawdbot` + `~/clawd` on the host (survives restarts/rebuilds)
 - Access the Control UI from your laptop via an SSH tunnel
 
@@ -40,7 +40,7 @@ For the generic Docker flow, see [Docker](/install/docker).
 2) Create Compute Engine VM (e2-small, Debian 12, 20GB)
 3) SSH into the VM
 4) Install Docker
-5) Clone Clawdbot repository
+5) Clone Moltbot repository
 6) Create persistent host directories
 7) Configure `.env` and `docker-compose.yml`
 8) Bake required binaries, build, and launch
@@ -87,8 +87,8 @@ All steps can be done via the web UI at https://console.cloud.google.com
 **CLI:**
 
 ```bash
-gcloud projects create my-clawdbot-project --name="Clawdbot Gateway"
-gcloud config set project my-clawdbot-project
+gcloud projects create my-moltbot-project --name="Moltbot Gateway"
+gcloud config set project my-moltbot-project
 ```
 
 Enable billing at https://console.cloud.google.com/billing (required for Compute Engine).
@@ -120,7 +120,7 @@ gcloud services enable compute.googleapis.com
 **CLI:**
 
 ```bash
-gcloud compute instances create clawdbot-gateway \
+gcloud compute instances create moltbot-gateway \
   --zone=us-central1-a \
   --machine-type=e2-small \
   --boot-disk-size=20GB \
@@ -131,7 +131,7 @@ gcloud compute instances create clawdbot-gateway \
 **Console:**
 
 1. Go to Compute Engine > VM instances > Create instance
-2. Name: `clawdbot-gateway`
+2. Name: `moltbot-gateway`
 3. Region: `us-central1`, Zone: `us-central1-a`
 4. Machine type: `e2-small`
 5. Boot disk: Debian 12, 20GB
@@ -144,7 +144,7 @@ gcloud compute instances create clawdbot-gateway \
 **CLI:**
 
 ```bash
-gcloud compute ssh clawdbot-gateway --zone=us-central1-a
+gcloud compute ssh moltbot-gateway --zone=us-central1-a
 ```
 
 **Console:**
@@ -173,7 +173,7 @@ exit
 Then SSH back in:
 
 ```bash
-gcloud compute ssh clawdbot-gateway --zone=us-central1-a
+gcloud compute ssh moltbot-gateway --zone=us-central1-a
 ```
 
 Verify:
@@ -185,11 +185,11 @@ docker compose version
 
 ---
 
-## 6) Clone the Clawdbot repository
+## 6) Clone the Moltbot repository
 
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/moltbot/moltbot.git
+cd moltbot
 ```
 
 This guide assumes you will build a custom image to guarantee binary persistence.
@@ -213,7 +213,7 @@ mkdir -p ~/clawd
 Create `.env` in the repository root.
 
 ```bash
-CLAWDBOT_IMAGE=clawdbot:latest
+CLAWDBOT_IMAGE=moltbot:latest
 CLAWDBOT_GATEWAY_TOKEN=change-me-now
 CLAWDBOT_GATEWAY_BIND=lan
 CLAWDBOT_GATEWAY_PORT=18789
@@ -241,7 +241,7 @@ Create or update `docker-compose.yml`.
 
 ```yaml
 services:
-  clawdbot-gateway:
+  moltbot-gateway:
     image: ${CLAWDBOT_IMAGE}
     build: .
     restart: unless-stopped
@@ -347,15 +347,15 @@ CMD ["node","dist/index.js"]
 
 ```bash
 docker compose build
-docker compose up -d clawdbot-gateway
+docker compose up -d moltbot-gateway
 ```
 
 Verify binaries:
 
 ```bash
-docker compose exec clawdbot-gateway which gog
-docker compose exec clawdbot-gateway which goplaces
-docker compose exec clawdbot-gateway which wacli
+docker compose exec moltbot-gateway which gog
+docker compose exec moltbot-gateway which goplaces
+docker compose exec moltbot-gateway which wacli
 ```
 
 Expected output:
@@ -371,7 +371,7 @@ Expected output:
 ## 12) Verify Gateway
 
 ```bash
-docker compose logs -f clawdbot-gateway
+docker compose logs -f moltbot-gateway
 ```
 
 Success:
@@ -387,7 +387,7 @@ Success:
 Create an SSH tunnel to forward the Gateway port:
 
 ```bash
-gcloud compute ssh clawdbot-gateway --zone=us-central1-a -- -L 18789:127.0.0.1:18789
+gcloud compute ssh moltbot-gateway --zone=us-central1-a -- -L 18789:127.0.0.1:18789
 ```
 
 Open in your browser:
@@ -400,12 +400,12 @@ Paste your gateway token.
 
 ## What persists where (source of truth)
 
-Clawdbot runs in Docker, but Docker is not the source of truth.
+Moltbot runs in Docker, but Docker is not the source of truth.
 All long-lived state must survive restarts, rebuilds, and reboots.
 
 | Component | Location | Persistence mechanism | Notes |
 |---|---|---|---|
-| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `clawdbot.json`, tokens |
+| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `moltbot.json`, tokens |
 | Model auth profiles | `/home/node/.clawdbot/` | Host volume mount | OAuth tokens, API keys |
 | Skill configs | `/home/node/.clawdbot/skills/` | Host volume mount | Skill-level state |
 | Agent workspace | `/home/node/clawd/` | Host volume mount | Code and agent artifacts |
@@ -420,10 +420,10 @@ All long-lived state must survive restarts, rebuilds, and reboots.
 
 ## Updates
 
-To update Clawdbot on the VM:
+To update Moltbot on the VM:
 
 ```bash
-cd ~/clawdbot
+cd ~/moltbot
 git pull
 docker compose build
 docker compose up -d
@@ -453,15 +453,15 @@ If using e2-micro and hitting OOM, upgrade to e2-small or e2-medium:
 
 ```bash
 # Stop the VM first
-gcloud compute instances stop clawdbot-gateway --zone=us-central1-a
+gcloud compute instances stop moltbot-gateway --zone=us-central1-a
 
 # Change machine type
-gcloud compute instances set-machine-type clawdbot-gateway \
+gcloud compute instances set-machine-type moltbot-gateway \
   --zone=us-central1-a \
   --machine-type=e2-small
 
 # Start the VM
-gcloud compute instances start clawdbot-gateway --zone=us-central1-a
+gcloud compute instances start moltbot-gateway --zone=us-central1-a
 ```
 
 ---
@@ -474,14 +474,14 @@ For automation or CI/CD pipelines, create a dedicated service account with minim
 
 1. Create a service account:
    ```bash
-   gcloud iam service-accounts create clawdbot-deploy \
-     --display-name="Clawdbot Deployment"
+   gcloud iam service-accounts create moltbot-deploy \
+     --display-name="Moltbot Deployment"
    ```
 
 2. Grant Compute Instance Admin role (or narrower custom role):
    ```bash
-   gcloud projects add-iam-policy-binding my-clawdbot-project \
-     --member="serviceAccount:clawdbot-deploy@my-clawdbot-project.iam.gserviceaccount.com" \
+   gcloud projects add-iam-policy-binding my-moltbot-project \
+     --member="serviceAccount:moltbot-deploy@my-moltbot-project.iam.gserviceaccount.com" \
      --role="roles/compute.instanceAdmin.v1"
    ```
 

docs/platforms/hetzner.md

@@ -1,25 +1,25 @@
 ---
-summary: "Run Clawdbot Gateway 24/7 on a cheap Hetzner VPS (Docker) with durable state and baked-in binaries"
+summary: "Run Moltbot Gateway 24/7 on a cheap Hetzner VPS (Docker) with durable state and baked-in binaries"
 read_when:
-  - You want Clawdbot running 24/7 on a cloud VPS (not your laptop)
+  - You want Moltbot running 24/7 on a cloud VPS (not your laptop)
   - You want a production-grade, always-on Gateway on your own VPS
   - You want full control over persistence, binaries, and restart behavior
-  - You are running Clawdbot in Docker on Hetzner or a similar provider
+  - You are running Moltbot in Docker on Hetzner or a similar provider
 ---
 
-# Clawdbot on Hetzner (Docker, Production VPS Guide)
+# Moltbot on Hetzner (Docker, Production VPS Guide)
 
 ## Goal
-Run a persistent Clawdbot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior.
+Run a persistent Moltbot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior.
 
-If you want “Clawdbot 24/7 for ~$5”, this is the simplest reliable setup.
+If you want “Moltbot 24/7 for ~$5”, this is the simplest reliable setup.
 Hetzner pricing changes; pick the smallest Debian/Ubuntu VPS and scale up if you hit OOMs.
 
 ## What are we doing (simple terms)?
 
 - Rent a small Linux server (Hetzner VPS)
 - Install Docker (isolated app runtime)
-- Start the Clawdbot Gateway in Docker
+- Start the Moltbot Gateway in Docker
 - Persist `~/.clawdbot` + `~/clawd` on the host (survives restarts/rebuilds)
 - Access the Control UI from your laptop via an SSH tunnel
 
@@ -37,7 +37,7 @@ For the generic Docker flow, see [Docker](/install/docker).
 
 1) Provision Hetzner VPS  
 2) Install Docker  
-3) Clone Clawdbot repository  
+3) Clone Moltbot repository  
 4) Create persistent host directories  
 5) Configure `.env` and `docker-compose.yml`  
 6) Bake required binaries into the image  
@@ -93,11 +93,11 @@ docker compose version
 
 ---
 
-## 3) Clone the Clawdbot repository
+## 3) Clone the Moltbot repository
 
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/moltbot/moltbot.git
+cd moltbot
 ```
 
 This guide assumes you will build a custom image to guarantee binary persistence.
@@ -125,7 +125,7 @@ chown -R 1000:1000 /root/clawd
 Create `.env` in the repository root.
 
 ```bash
-CLAWDBOT_IMAGE=clawdbot:latest
+CLAWDBOT_IMAGE=moltbot:latest
 CLAWDBOT_GATEWAY_TOKEN=change-me-now
 CLAWDBOT_GATEWAY_BIND=lan
 CLAWDBOT_GATEWAY_PORT=18789
@@ -153,7 +153,7 @@ Create or update `docker-compose.yml`.
 
 ```yaml
 services:
-  clawdbot-gateway:
+  moltbot-gateway:
     image: ${CLAWDBOT_IMAGE}
     build: .
     restart: unless-stopped
@@ -259,15 +259,15 @@ CMD ["node","dist/index.js"]
 
 ```bash
 docker compose build
-docker compose up -d clawdbot-gateway
+docker compose up -d moltbot-gateway
 ```
 
 Verify binaries:
 
 ```bash
-docker compose exec clawdbot-gateway which gog
-docker compose exec clawdbot-gateway which goplaces
-docker compose exec clawdbot-gateway which wacli
+docker compose exec moltbot-gateway which gog
+docker compose exec moltbot-gateway which goplaces
+docker compose exec moltbot-gateway which wacli
 ```
 
 Expected output:
@@ -283,7 +283,7 @@ Expected output:
 ## 9) Verify Gateway
 
 ```bash
-docker compose logs -f clawdbot-gateway
+docker compose logs -f moltbot-gateway
 ```
 
 Success:
@@ -308,12 +308,12 @@ Paste your gateway token.
 
 ## What persists where (source of truth)
 
-Clawdbot runs in Docker, but Docker is not the source of truth.
+Moltbot runs in Docker, but Docker is not the source of truth.
 All long-lived state must survive restarts, rebuilds, and reboots.
 
 | Component | Location | Persistence mechanism | Notes |
 |---|---|---|---|
-| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `clawdbot.json`, tokens |
+| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `moltbot.json`, tokens |
 | Model auth profiles | `/home/node/.clawdbot/` | Host volume mount | OAuth tokens, API keys |
 | Skill configs | `/home/node/.clawdbot/skills/` | Host volume mount | Skill-level state |
 | Agent workspace | `/home/node/clawd/` | Host volume mount | Code and agent artifacts |

docs/platforms/index.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Platforms
 
-Clawdbot core is written in TypeScript. **Node is the recommended runtime**.
+Moltbot core is written in TypeScript. **Node is the recommended runtime**.
 Bun is not recommended for the Gateway (WhatsApp/Telegram bugs).
 
 Companion apps exist for macOS (menu bar app) and mobile nodes (iOS/Android). Windows and
@@ -34,17 +34,17 @@ Native companion apps for Windows are also planned; the Gateway is recommended v
 - Install guide: [Getting Started](/start/getting-started)
 - Gateway runbook: [Gateway](/gateway)
 - Gateway configuration: [Configuration](/gateway/configuration)
-- Service status: `clawdbot gateway status`
+- Service status: `moltbot gateway status`
 
 ## Gateway service install (CLI)
 
 Use one of these (all supported):
 
-- Wizard (recommended): `clawdbot onboard --install-daemon`
-- Direct: `clawdbot gateway install`
-- Configure flow: `clawdbot configure` → select **Gateway service**
-- Repair/migrate: `clawdbot doctor` (offers to install or fix the service)
+- Wizard (recommended): `moltbot onboard --install-daemon`
+- Direct: `moltbot gateway install`
+- Configure flow: `moltbot configure` → select **Gateway service**
+- Repair/migrate: `moltbot doctor` (offers to install or fix the service)
 
 The service target depends on OS:
 - macOS: LaunchAgent (`com.clawdbot.gateway` or `com.clawdbot.<profile>`)
-- Linux/WSL2: systemd user service (`clawdbot-gateway[-<profile>].service`)
+- Linux/WSL2: systemd user service (`moltbot-gateway[-<profile>].service`)

docs/platforms/ios.md

@@ -20,7 +20,7 @@ Availability: internal preview. The iOS app is not publicly distributed yet.
 - Gateway running on another device (macOS, Linux, or Windows via WSL2).
 - Network path:
   - Same LAN via Bonjour, **or**
-  - Tailnet via unicast DNS-SD (`clawdbot.internal.`), **or**
+  - Tailnet via unicast DNS-SD (`moltbot.internal.`), **or**
   - Manual host/port (fallback).
 
 ## Quick start (pair + connect)
@@ -28,7 +28,7 @@ Availability: internal preview. The iOS app is not publicly distributed yet.
 1) Start the Gateway:
 
 ```bash
-clawdbot gateway --port 18789
+moltbot gateway --port 18789
 ```
 
 2) In the iOS app, open Settings and pick a discovered gateway (or enable Manual Host and enter host/port).
@@ -36,26 +36,26 @@ clawdbot gateway --port 18789
 3) Approve the pairing request on the gateway host:
 
 ```bash
-clawdbot nodes pending
-clawdbot nodes approve <requestId>
+moltbot nodes pending
+moltbot nodes approve <requestId>
 ```
 
 4) Verify connection:
 
 ```bash
-clawdbot nodes status
-clawdbot gateway call node.list --params "{}"
+moltbot nodes status
+moltbot gateway call node.list --params "{}"
 ```
 
 ## Discovery paths
 
 ### Bonjour (LAN)
 
-The Gateway advertises `_clawdbot._tcp` on `local.`. The iOS app lists these automatically.
+The Gateway advertises `_moltbot._tcp` on `local.`. The iOS app lists these automatically.
 
 ### Tailnet (cross-network)
 
-If mDNS is blocked, use a unicast DNS-SD zone (recommended domain: `clawdbot.internal.`) and Tailscale split DNS.
+If mDNS is blocked, use a unicast DNS-SD zone (recommended domain: `moltbot.internal.`) and Tailscale split DNS.
 See [Bonjour](/gateway/bonjour) for the CoreDNS example.
 
 ### Manual host/port
@@ -67,22 +67,22 @@ In Settings, enable **Manual Host** and enter the gateway host + port (default `
 The iOS node renders a WKWebView canvas. Use `node.invoke` to drive it:
 
 ```bash
-clawdbot nodes invoke --node "iOS Node" --command canvas.navigate --params '{"url":"http://<gateway-host>:18793/__clawdbot__/canvas/"}'
+moltbot nodes invoke --node "iOS Node" --command canvas.navigate --params '{"url":"http://<gateway-host>:18793/__moltbot__/canvas/"}'
 ```
 
 Notes:
-- The Gateway canvas host serves `/__clawdbot__/canvas/` and `/__clawdbot__/a2ui/`.
+- The Gateway canvas host serves `/__moltbot__/canvas/` and `/__moltbot__/a2ui/`.
 - The iOS node auto-navigates to A2UI on connect when a canvas host URL is advertised.
 - Return to the built-in scaffold with `canvas.navigate` and `{"url":""}`.
 
 ### Canvas eval / snapshot
 
 ```bash
-clawdbot nodes invoke --node "iOS Node" --command canvas.eval --params '{"javaScript":"(() => { const {ctx} = window.__clawdbot; ctx.clearRect(0,0,innerWidth,innerHeight); ctx.lineWidth=6; ctx.strokeStyle=\"#ff2d55\"; ctx.beginPath(); ctx.moveTo(40,40); ctx.lineTo(innerWidth-40, innerHeight-40); ctx.stroke(); return \"ok\"; })()"}'
+moltbot nodes invoke --node "iOS Node" --command canvas.eval --params '{"javaScript":"(() => { const {ctx} = window.__moltbot; ctx.clearRect(0,0,innerWidth,innerHeight); ctx.lineWidth=6; ctx.strokeStyle=\"#ff2d55\"; ctx.beginPath(); ctx.moveTo(40,40); ctx.lineTo(innerWidth-40, innerHeight-40); ctx.stroke(); return \"ok\"; })()"}'
 ```
 
 ```bash
-clawdbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"maxWidth":900,"format":"jpeg"}'
+moltbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"maxWidth":900,"format":"jpeg"}'
 ```
 
 ## Voice wake + talk mode
@@ -94,7 +94,7 @@ clawdbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"ma
 
 - `NODE_BACKGROUND_UNAVAILABLE`: bring the iOS app to the foreground (canvas/camera/screen commands require it).
 - `A2UI_HOST_NOT_CONFIGURED`: the Gateway did not advertise a canvas host URL; check `canvasHost` in [Gateway configuration](/gateway/configuration).
-- Pairing prompt never appears: run `clawdbot nodes pending` and approve manually.
+- Pairing prompt never appears: run `moltbot nodes pending` and approve manually.
 - Reconnect fails after reinstall: the Keychain pairing token was cleared; re-pair the node.
 
 ## Related docs

docs/platforms/linux.md

@@ -14,8 +14,8 @@ Native Linux companion apps are planned. Contributions are welcome if you want t
 ## Beginner quick path (VPS)
 
 1) Install Node 22+  
-2) `npm i -g clawdbot@latest`  
-3) `clawdbot onboard --install-daemon`  
+2) `npm i -g moltbot@latest`  
+3) `moltbot onboard --install-daemon`  
 4) From your laptop: `ssh -N -L 18789:127.0.0.1:18789 <user>@<host>`  
 5) Open `http://127.0.0.1:18789/` and paste your token
 
@@ -35,19 +35,19 @@ Step-by-step VPS guide: [exe.dev](/platforms/exe-dev)
 Use one of these:
 
 ```
-clawdbot onboard --install-daemon
+moltbot onboard --install-daemon
 ```
 
 Or:
 
 ```
-clawdbot gateway install
+moltbot gateway install
 ```
 
 Or:
 
 ```
-clawdbot configure
+moltbot configure
 ```
 
 Select **Gateway service** when prompted.
@@ -55,26 +55,26 @@ Select **Gateway service** when prompted.
 Repair/migrate:
 
 ```
-clawdbot doctor
+moltbot doctor
 ```
 
 ## System control (systemd user unit)
-Clawdbot installs a systemd **user** service by default. Use a **system**
+Moltbot installs a systemd **user** service by default. Use a **system**
 service for shared or always-on servers. The full unit example and guidance
 live in the [Gateway runbook](/gateway).
 
 Minimal setup:
 
-Create `~/.config/systemd/user/clawdbot-gateway[-<profile>].service`:
+Create `~/.config/systemd/user/moltbot-gateway[-<profile>].service`:
 
 ```
 [Unit]
-Description=Clawdbot Gateway (profile: <profile>, v<version>)
+Description=Moltbot Gateway (profile: <profile>, v<version>)
 After=network-online.target
 Wants=network-online.target
 
 [Service]
-ExecStart=/usr/local/bin/clawdbot gateway --port 18789
+ExecStart=/usr/local/bin/moltbot gateway --port 18789
 Restart=always
 RestartSec=5
 
@@ -85,5 +85,5 @@ WantedBy=default.target
 Enable it:
 
 ```
-systemctl --user enable --now clawdbot-gateway[-<profile>].service
+systemctl --user enable --now moltbot-gateway[-<profile>].service
 ```

docs/platforms/mac/bundled-gateway.md

@@ -1,24 +1,24 @@
 ---
 summary: "Gateway runtime on macOS (external launchd service)"
 read_when:
-  - Packaging Clawdbot.app
+  - Packaging Moltbot.app
   - Debugging the macOS gateway launchd service
   - Installing the gateway CLI for macOS
 ---
 
 # Gateway on macOS (external launchd)
 
-Clawdbot.app no longer bundles Node/Bun or the Gateway runtime. The macOS app
-expects an **external** `clawdbot` CLI install, does not spawn the Gateway as a
+Moltbot.app no longer bundles Node/Bun or the Gateway runtime. The macOS app
+expects an **external** `moltbot` CLI install, does not spawn the Gateway as a
 child process, and manages a per‑user launchd service to keep the Gateway
 running (or attaches to an existing local Gateway if one is already running).
 
 ## Install the CLI (required for local mode)
 
-You need Node 22+ on the Mac, then install `clawdbot` globally:
+You need Node 22+ on the Mac, then install `moltbot` globally:
 
 ```bash
-npm install -g clawdbot@<version>
+npm install -g moltbot@<version>
 ```
 
 The macOS app’s **Install CLI** button runs the same flow via npm/pnpm (bun not recommended for Gateway runtime).
@@ -34,16 +34,16 @@ Plist location (per‑user):
 
 Manager:
 - The macOS app owns LaunchAgent install/update in Local mode.
-- The CLI can also install it: `clawdbot gateway install`.
+- The CLI can also install it: `moltbot gateway install`.
 
 Behavior:
-- “Clawdbot Active” enables/disables the LaunchAgent.
+- “Moltbot Active” enables/disables the LaunchAgent.
 - App quit does **not** stop the gateway (launchd keeps it alive).
 - If a Gateway is already running on the configured port, the app attaches to
   it instead of starting a new one.
 
 Logging:
-- launchd stdout/err: `/tmp/clawdbot/clawdbot-gateway.log`
+- launchd stdout/err: `/tmp/moltbot/moltbot-gateway.log`
 
 ## Version compatibility
 
@@ -53,15 +53,15 @@ incompatible, update the global CLI to match the app version.
 ## Smoke check
 
 ```bash
-clawdbot --version
+moltbot --version
 
 CLAWDBOT_SKIP_CHANNELS=1 \
 CLAWDBOT_SKIP_CANVAS_HOST=1 \
-clawdbot gateway --port 18999 --bind loopback
+moltbot gateway --port 18999 --bind loopback
 ```
 
 Then:
 
 ```bash
-clawdbot gateway call health --url ws://127.0.0.1:18999 --timeout 3000
+moltbot gateway call health --url ws://127.0.0.1:18999 --timeout 3000
 ```

docs/platforms/mac/canvas.md

@@ -15,16 +15,16 @@ UI surfaces.
 
 Canvas state is stored under Application Support:
 
-- `~/Library/Application Support/Clawdbot/canvas/<session>/...`
+- `~/Library/Application Support/Moltbot/canvas/<session>/...`
 
 The Canvas panel serves those files via a **custom URL scheme**:
 
-- `clawdbot-canvas://<session>/<path>`
+- `moltbot-canvas://<session>/<path>`
 
 Examples:
-- `clawdbot-canvas://main/` → `<canvasRoot>/main/index.html`
-- `clawdbot-canvas://main/assets/app.css` → `<canvasRoot>/main/assets/app.css`
-- `clawdbot-canvas://main/widgets/todo/` → `<canvasRoot>/main/widgets/todo/index.html`
+- `moltbot-canvas://main/` → `<canvasRoot>/main/index.html`
+- `moltbot-canvas://main/assets/app.css` → `<canvasRoot>/main/assets/app.css`
+- `moltbot-canvas://main/widgets/todo/` → `<canvasRoot>/main/widgets/todo/index.html`
 
 If no `index.html` exists at the root, the app shows a **built‑in scaffold page**.
 
@@ -50,10 +50,10 @@ Canvas is exposed via the **Gateway WebSocket**, so the agent can:
 CLI examples:
 
 ```bash
-clawdbot nodes canvas present --node <id>
-clawdbot nodes canvas navigate --node <id> --url "/"
-clawdbot nodes canvas eval --node <id> --js "document.title"
-clawdbot nodes canvas snapshot --node <id>
+moltbot nodes canvas present --node <id>
+moltbot nodes canvas navigate --node <id> --url "/"
+moltbot nodes canvas eval --node <id> --js "document.title"
+moltbot nodes canvas snapshot --node <id>
 ```
 
 Notes:
@@ -69,7 +69,7 @@ A2UI host page on first open.
 Default A2UI host URL:
 
 ```
-http://<gateway-host>:18793/__clawdbot__/a2ui/
+http://<gateway-host>:18793/__moltbot__/a2ui/
 ```
 
 ### A2UI commands (v0.8)
@@ -91,25 +91,25 @@ cat > /tmp/a2ui-v0.8.jsonl <<'EOFA2'
 {"beginRendering":{"surfaceId":"main","root":"root"}}
 EOFA2
 
-clawdbot nodes canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node <id>
+moltbot nodes canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node <id>
 ```
 
 Quick smoke:
 
 ```bash
-clawdbot nodes canvas a2ui push --node <id> --text "Hello from A2UI"
+moltbot nodes canvas a2ui push --node <id> --text "Hello from A2UI"
 ```
 
 ## Triggering agent runs from Canvas
 
 Canvas can trigger new agent runs via deep links:
 
-- `clawdbot://agent?...`
+- `moltbot://agent?...`
 
 Example (in JS):
 
 ```js
-window.location.href = "clawdbot://agent?message=Review%20this%20design";
+window.location.href = "moltbot://agent?message=Review%20this%20design";
 ```
 
 The app prompts for confirmation unless a valid key is provided.

docs/platforms/mac/child-process.md

@@ -8,7 +8,7 @@ read_when:
 The macOS app **manages the Gateway via launchd** by default and does not spawn
 the Gateway as a child process. It first tries to attach to an already‑running
 Gateway on the configured port; if none is reachable, it enables the launchd
-service via the external `clawdbot` CLI (no embedded runtime). This gives you
+service via the external `moltbot` CLI (no embedded runtime). This gives you
 reliable auto‑start at login and restart on crashes.
 
 Child‑process mode (Gateway spawned directly by the app) is **not in use** today.

docs/platforms/mac/dev-setup.md

@@ -1,11 +1,11 @@
 ---
-summary: "Setup guide for developers working on the Clawdbot macOS app"
+summary: "Setup guide for developers working on the Moltbot macOS app"
 read_when:
   - Setting up the macOS development environment
 ---
 # macOS Developer Setup
 
-This guide covers the necessary steps to build and run the Clawdbot macOS application from source.
+This guide covers the necessary steps to build and run the Moltbot macOS application from source.
 
 ## Prerequisites
 
@@ -24,7 +24,7 @@ pnpm install
 
 ## 2. Build and Package the App
 
-To build the macOS app and package it into `dist/Clawdbot.app`, run:
+To build the macOS app and package it into `dist/Moltbot.app`, run:
 
 ```bash
 ./scripts/package-mac-app.sh
@@ -33,22 +33,22 @@ To build the macOS app and package it into `dist/Clawdbot.app`, run:
 If you don't have an Apple Developer ID certificate, the script will automatically use **ad-hoc signing** (`-`). 
 
 For dev run modes, signing flags, and Team ID troubleshooting, see the macOS app README:
-https://github.com/clawdbot/clawdbot/blob/main/apps/macos/README.md
+https://github.com/moltbot/moltbot/blob/main/apps/macos/README.md
 
 > **Note**: Ad-hoc signed apps may trigger security prompts. If the app crashes immediately with "Abort trap 6", see the [Troubleshooting](#troubleshooting) section.
 
 ## 3. Install the CLI
 
-The macOS app expects a global `clawdbot` CLI install to manage background tasks.
+The macOS app expects a global `moltbot` CLI install to manage background tasks.
 
 **To install it (recommended):**
-1.  Open the Clawdbot app.
+1.  Open the Moltbot app.
 2.  Go to the **General** settings tab.
 3.  Click **"Install CLI"**.
 
 Alternatively, install it manually:
 ```bash
-npm install -g clawdbot@<version>
+npm install -g moltbot@<version>
 ```
 
 ## Troubleshooting
@@ -76,14 +76,14 @@ If the app crashes when you try to allow **Speech Recognition** or **Microphone*
    ```bash
    tccutil reset All com.clawdbot.mac.debug
    ```
-2. If that fails, change the `BUNDLE_ID` temporarily in [`scripts/package-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/package-mac-app.sh) to force a "clean slate" from macOS.
+2. If that fails, change the `BUNDLE_ID` temporarily in [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) to force a "clean slate" from macOS.
 
 ### Gateway "Starting..." indefinitely
 If the gateway status stays on "Starting...", check if a zombie process is holding the port:
 
 ```bash
-clawdbot gateway status
-clawdbot gateway stop
+moltbot gateway status
+moltbot gateway stop
 
 # If you’re not using a LaunchAgent (dev mode / manual runs), find the listener:
 lsof -nP -iTCP:18789 -sTCP:LISTEN

docs/platforms/mac/health.md

@@ -21,8 +21,8 @@ How to see whether the linked channel is healthy from the menu bar app.
 - **Channels tab** surfaces channel status + controls for WhatsApp/Telegram (login QR, logout, probe, last disconnect/error).
 
 ## How the probe works
-- App runs `clawdbot health --json` via `ShellExecutor` every ~60s and on demand. The probe loads creds and reports status without sending messages.
+- App runs `moltbot health --json` via `ShellExecutor` every ~60s and on demand. The probe loads creds and reports status without sending messages.
 - Cache the last good snapshot and the last error separately to avoid flicker; show the timestamp of each.
 
 ## When in doubt
-- You can still use the CLI flow in [Gateway health](/gateway/health) (`clawdbot status`, `clawdbot status --deep`, `clawdbot health --json`) and tail `/tmp/clawdbot/clawdbot-*.log` for `web-heartbeat` / `web-reconnect`.
+- You can still use the CLI flow in [Gateway health](/gateway/health) (`moltbot status`, `moltbot status --deep`, `moltbot health --json`) and tail `/tmp/moltbot/moltbot-*.log` for `web-heartbeat` / `web-reconnect`.

docs/platforms/mac/icon.md

@@ -1,5 +1,5 @@
 ---
-summary: "Menu bar icon states and animations for Clawdbot on macOS"
+summary: "Menu bar icon states and animations for Moltbot on macOS"
 read_when:
   - Changing menu bar icon behavior
 ---

docs/platforms/mac/logging.md

@@ -1,5 +1,5 @@
 ---
-summary: "Clawdbot logging: rolling diagnostics file log + unified log privacy flags"
+summary: "Moltbot logging: rolling diagnostics file log + unified log privacy flags"
 read_when:
   - Capturing macOS logs or investigating private data logging
   - Debugging voice wake/session lifecycle issues
@@ -7,11 +7,11 @@ read_when:
 # Logging (macOS)
 
 ## Rolling diagnostics file log (Debug pane)
-Clawdbot routes macOS app logs through swift-log (unified logging by default) and can write a local, rotating file log to disk when you need a durable capture.
+Moltbot routes macOS app logs through swift-log (unified logging by default) and can write a local, rotating file log to disk when you need a durable capture.
 
 - Verbosity: **Debug pane → Logs → App logging → Verbosity**
 - Enable: **Debug pane → Logs → App logging → “Write rolling diagnostics log (JSONL)”**
-- Location: `~/Library/Logs/Clawdbot/diagnostics.jsonl` (rotates automatically; old files are suffixed with `.1`, `.2`, …)
+- Location: `~/Library/Logs/Moltbot/diagnostics.jsonl` (rotates automatically; old files are suffixed with `.1`, `.2`, …)
 - Clear: **Debug pane → Logs → App logging → “Clear”**
 
 Notes:
@@ -22,7 +22,7 @@ Notes:
 
 Unified logging redacts most payloads unless a subsystem opts into `privacy -off`. Per Peter's write-up on macOS [logging privacy shenanigans](https://steipete.me/posts/2025/logging-privacy-shenanigans) (2025) this is controlled by a plist in `/Library/Preferences/Logging/Subsystems/` keyed by the subsystem name. Only new log entries pick up the flag, so enable it before reproducing an issue.
 
-## Enable for Clawdbot (`com.clawdbot`)
+## Enable for Moltbot (`com.clawdbot`)
 - Write the plist to a temp file first, then install it atomically as root:
 
 ```bash

docs/platforms/mac/menu-bar.md

@@ -40,7 +40,7 @@ read_when:
 
 ## Status row text (menu)
 - While work is active: `<Session role> · <activity label>`
-  - Examples: `Main · exec: pnpm test`, `Other · read: apps/macos/Sources/Clawdbot/AppState.swift`.
+  - Examples: `Main · exec: pnpm test`, `Other · read: apps/macos/Sources/Moltbot/AppState.swift`.
 - When idle: falls back to the health summary.
 
 ## Event ingestion

docs/platforms/mac/peekaboo.md

@@ -1,28 +1,28 @@
 ---
 summary: "PeekabooBridge integration for macOS UI automation"
 read_when:
-  - Hosting PeekabooBridge in Clawdbot.app
+  - Hosting PeekabooBridge in Moltbot.app
   - Integrating Peekaboo via Swift Package Manager
   - Changing PeekabooBridge protocol/paths
 ---
 # Peekaboo Bridge (macOS UI automation)
 
-Clawdbot can host **PeekabooBridge** as a local, permission‑aware UI automation
+Moltbot can host **PeekabooBridge** as a local, permission‑aware UI automation
 broker. This lets the `peekaboo` CLI drive UI automation while reusing the
 macOS app’s TCC permissions.
 
 ## What this is (and isn’t)
 
-- **Host**: Clawdbot.app can act as a PeekabooBridge host.
-- **Client**: use the `peekaboo` CLI (no separate `clawdbot ui ...` surface).
-- **UI**: visual overlays stay in Peekaboo.app; Clawdbot is a thin broker host.
+- **Host**: Moltbot.app can act as a PeekabooBridge host.
+- **Client**: use the `peekaboo` CLI (no separate `moltbot ui ...` surface).
+- **UI**: visual overlays stay in Peekaboo.app; Moltbot is a thin broker host.
 
 ## Enable the bridge
 
 In the macOS app:
 - Settings → **Enable Peekaboo Bridge**
 
-When enabled, Clawdbot starts a local UNIX socket server. If disabled, the host
+When enabled, Moltbot starts a local UNIX socket server. If disabled, the host
 is stopped and `peekaboo` will fall back to other available hosts.
 
 ## Client discovery order
@@ -31,7 +31,7 @@ Peekaboo clients typically try hosts in this order:
 
 1. Peekaboo.app (full UX)
 2. Claude.app (if installed)
-3. Clawdbot.app (thin broker)
+3. Moltbot.app (thin broker)
 
 Use `peekaboo bridge status --verbose` to see which host is active and which
 socket path is in use. You can override with:
@@ -43,7 +43,7 @@ export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock
 ## Security & permissions
 
 - The bridge validates **caller code signatures**; an allowlist of TeamIDs is
-  enforced (Peekaboo host TeamID + Clawdbot app TeamID).
+  enforced (Peekaboo host TeamID + Moltbot app TeamID).
 - Requests time out after ~10 seconds.
 - If required permissions are missing, the bridge returns a clear error message
   rather than launching System Settings.
@@ -58,5 +58,5 @@ If you need longer retention, re‑capture from the client.
 - If `peekaboo` reports “bridge client is not authorized”, ensure the client is
   properly signed or run the host with `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1`
   in **debug** mode only.
-- If no hosts are found, open one of the host apps (Peekaboo.app or Clawdbot.app)
+- If no hosts are found, open one of the host apps (Peekaboo.app or Moltbot.app)
   and confirm permissions are granted.

docs/platforms/mac/permissions.md

@@ -12,7 +12,7 @@ app's code signature, bundle identifier, and on-disk path. If any of those chang
 macOS treats the app as new and may drop or hide prompts.
 
 ## Requirements for stable permissions
-- Same path: run the app from a fixed location (for Clawdbot, `dist/Clawdbot.app`).
+- Same path: run the app from a fixed location (for Moltbot, `dist/Moltbot.app`).
 - Same bundle identifier: changing the bundle ID creates a new permission identity.
 - Signed app: unsigned or ad-hoc signed builds do not persist permissions.
 - Consistent signature: use a real Apple Development or Developer ID certificate

docs/platforms/mac/release.md

@@ -1,11 +1,11 @@
 ---
-summary: "Clawdbot macOS release checklist (Sparkle feed, packaging, signing)"
+summary: "Moltbot macOS release checklist (Sparkle feed, packaging, signing)"
 read_when:
-  - Cutting or validating a Clawdbot macOS release
+  - Cutting or validating a Moltbot macOS release
   - Updating the Sparkle appcast or feed assets
 ---
 
-# Clawdbot macOS release (Sparkle)
+# Moltbot macOS release (Sparkle)
 
 This app now ships Sparkle auto-updates. Release builds must be Developer ID–signed, zipped, and published with a signed appcast entry.
 
@@ -13,10 +13,10 @@ This app now ships Sparkle auto-updates. Release builds must be Developer ID–s
 - Developer ID Application cert installed (example: `Developer ID Application: <Developer Name> (<TEAMID>)`).
 - Sparkle private key path set in the environment as `SPARKLE_PRIVATE_KEY_FILE` (path to your Sparkle ed25519 private key; public key baked into Info.plist). If it is missing, check `~/.profile`.
 - Notary credentials (keychain profile or API key) for `xcrun notarytool` if you want Gatekeeper-safe DMG/zip distribution.
-  - We use a Keychain profile named `clawdbot-notary`, created from App Store Connect API key env vars in your shell profile:
+  - We use a Keychain profile named `moltbot-notary`, created from App Store Connect API key env vars in your shell profile:
     - `APP_STORE_CONNECT_API_KEY_P8`, `APP_STORE_CONNECT_KEY_ID`, `APP_STORE_CONNECT_ISSUER_ID`
-    - `echo "$APP_STORE_CONNECT_API_KEY_P8" | sed 's/\\n/\n/g' > /tmp/clawdbot-notary.p8`
-    - `xcrun notarytool store-credentials "clawdbot-notary" --key /tmp/clawdbot-notary.p8 --key-id "$APP_STORE_CONNECT_KEY_ID" --issuer "$APP_STORE_CONNECT_ISSUER_ID"`
+    - `echo "$APP_STORE_CONNECT_API_KEY_P8" | sed 's/\\n/\n/g' > /tmp/moltbot-notary.p8`
+    - `xcrun notarytool store-credentials "moltbot-notary" --key /tmp/moltbot-notary.p8 --key-id "$APP_STORE_CONNECT_KEY_ID" --issuer "$APP_STORE_CONNECT_ISSUER_ID"`
 - `pnpm` deps installed (`pnpm install --config.node-linker=hoisted`).
 - Sparkle tools are fetched automatically via SwiftPM at `apps/macos/.build/artifacts/sparkle/Sparkle/bin/` (`sign_update`, `generate_appcast`, etc.).
 
@@ -37,16 +37,16 @@ SIGN_IDENTITY="Developer ID Application: <Developer Name> (<TEAMID>)" \
 scripts/package-mac-app.sh
 
 # Zip for distribution (includes resource forks for Sparkle delta support)
-ditto -c -k --sequesterRsrc --keepParent dist/Clawdbot.app dist/Clawdbot-2026.1.26.zip
+ditto -c -k --sequesterRsrc --keepParent dist/Moltbot.app dist/Moltbot-2026.1.26.zip
 
 # Optional: also build a styled DMG for humans (drag to /Applications)
-scripts/create-dmg.sh dist/Clawdbot.app dist/Clawdbot-2026.1.26.dmg
+scripts/create-dmg.sh dist/Moltbot.app dist/Moltbot-2026.1.26.dmg
 
 # Recommended: build + notarize/staple zip + DMG
 # First, create a keychain profile once:
-#   xcrun notarytool store-credentials "clawdbot-notary" \
+#   xcrun notarytool store-credentials "moltbot-notary" \
 #     --apple-id "<apple-id>" --team-id "<team-id>" --password "<app-specific-password>"
-NOTARIZE=1 NOTARYTOOL_PROFILE=clawdbot-notary \
+NOTARIZE=1 NOTARYTOOL_PROFILE=moltbot-notary \
 BUNDLE_ID=com.clawdbot.mac \
 APP_VERSION=2026.1.26 \
 APP_BUILD="$(git rev-list --count HEAD)" \
@@ -55,22 +55,22 @@ SIGN_IDENTITY="Developer ID Application: <Developer Name> (<TEAMID>)" \
 scripts/package-mac-dist.sh
 
 # Optional: ship dSYM alongside the release
-ditto -c -k --keepParent apps/macos/.build/release/Clawdbot.app.dSYM dist/Clawdbot-2026.1.26.dSYM.zip
+ditto -c -k --keepParent apps/macos/.build/release/Moltbot.app.dSYM dist/Moltbot-2026.1.26.dSYM.zip
 ```
 
 ## Appcast entry
 Use the release note generator so Sparkle renders formatted HTML notes:
 ```bash
-SPARKLE_PRIVATE_KEY_FILE=/path/to/ed25519-private-key scripts/make_appcast.sh dist/Clawdbot-2026.1.26.zip https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml
+SPARKLE_PRIVATE_KEY_FILE=/path/to/ed25519-private-key scripts/make_appcast.sh dist/Moltbot-2026.1.26.zip https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml
 ```
-Generates HTML release notes from `CHANGELOG.md` (via [`scripts/changelog-to-html.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/changelog-to-html.sh)) and embeds them in the appcast entry.
+Generates HTML release notes from `CHANGELOG.md` (via [`scripts/changelog-to-html.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/changelog-to-html.sh)) and embeds them in the appcast entry.
 Commit the updated `appcast.xml` alongside the release assets (zip + dSYM) when publishing.
 
 ## Publish & verify
-- Upload `Clawdbot-2026.1.26.zip` (and `Clawdbot-2026.1.26.dSYM.zip`) to the GitHub release for tag `v2026.1.26`.
-- Ensure the raw appcast URL matches the baked feed: `https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml`.
+- Upload `Moltbot-2026.1.26.zip` (and `Moltbot-2026.1.26.dSYM.zip`) to the GitHub release for tag `v2026.1.26`.
+- Ensure the raw appcast URL matches the baked feed: `https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml`.
 - Sanity checks:
-  - `curl -I https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml` returns 200.
+  - `curl -I https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml` returns 200.
   - `curl -I <enclosure url>` returns 200 after assets upload.
   - On a previous public build, run “Check for Updates…” from the About tab and verify Sparkle installs the new build cleanly.
 

docs/platforms/mac/remote.md

@@ -1,16 +1,16 @@
 ---
-summary: "macOS app flow for controlling a remote Clawdbot gateway over SSH"
+summary: "macOS app flow for controlling a remote Moltbot gateway over SSH"
 read_when:
   - Setting up or debugging remote mac control
 ---
-# Remote Clawdbot (macOS ⇄ remote host)
+# Remote Moltbot (macOS ⇄ remote host)
 
 
-This flow lets the macOS app act as a full remote control for a Clawdbot gateway running on another host (desktop/server). It’s the app’s **Remote over SSH** (remote run) feature. All features—health checks, Voice Wake forwarding, and Web Chat—reuse the same remote SSH configuration from *Settings → General*.
+This flow lets the macOS app act as a full remote control for a Moltbot gateway running on another host (desktop/server). It’s the app’s **Remote over SSH** (remote run) feature. All features—health checks, Voice Wake forwarding, and Web Chat—reuse the same remote SSH configuration from *Settings → General*.
 
 ## Modes
 - **Local (this Mac)**: Everything runs on the laptop. No SSH involved.
-- **Remote over SSH (default)**: Clawdbot commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key and a local port-forward.
+- **Remote over SSH (default)**: Moltbot commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key and a local port-forward.
 - **Remote direct (ws/wss)**: No SSH tunnel. The mac app connects to the gateway URL directly (for example, via Tailscale Serve or a public HTTPS reverse proxy).
 
 ## Remote transports
@@ -19,21 +19,21 @@ Remote mode supports two transports:
 - **Direct (ws/wss)**: Connects straight to the gateway URL. The gateway sees the real client IP.
 
 ## Prereqs on the remote host
-1) Install Node + pnpm and build/install the Clawdbot CLI (`pnpm install && pnpm build && pnpm link --global`).
-2) Ensure `clawdbot` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed).
+1) Install Node + pnpm and build/install the Moltbot CLI (`pnpm install && pnpm build && pnpm link --global`).
+2) Ensure `moltbot` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed).
 3) Open SSH with key auth. We recommend **Tailscale** IPs for stable reachability off-LAN.
 
 ## macOS app setup
 1) Open *Settings → General*.
-2) Under **Clawdbot runs**, pick **Remote over SSH** and set:
+2) Under **Moltbot runs**, pick **Remote over SSH** and set:
    - **Transport**: **SSH tunnel** or **Direct (ws/wss)**.
    - **SSH target**: `user@host` (optional `:port`).
      - If the gateway is on the same LAN and advertises Bonjour, pick it from the discovered list to auto-fill this field.
    - **Gateway URL** (Direct only): `wss://gateway.example.ts.net` (or `ws://...` for local/LAN).
    - **Identity file** (advanced): path to your key.
    - **Project root** (advanced): remote checkout path used for commands.
-   - **CLI path** (advanced): optional path to a runnable `clawdbot` entrypoint/binary (auto-filled when advertised).
-3) Hit **Test remote**. Success indicates the remote `clawdbot status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely.
+   - **CLI path** (advanced): optional path to a runnable `moltbot` entrypoint/binary (auto-filled when advertised).
+3) Hit **Test remote**. Success indicates the remote `moltbot status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely.
 4) Health checks and Web Chat will now run through this SSH tunnel automatically.
 
 ## Web Chat
@@ -51,21 +51,21 @@ Remote mode supports two transports:
 - See [Security](/gateway/security) and [Tailscale](/gateway/tailscale).
 
 ## WhatsApp login flow (remote)
-- Run `clawdbot channels login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone.
+- Run `moltbot channels login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone.
 - Re-run login on that host if auth expires. Health check will surface link problems.
 
 ## Troubleshooting
-- **exit 127 / not found**: `clawdbot` isn’t on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`.
-- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`clawdbot status --json`).
+- **exit 127 / not found**: `moltbot` isn’t on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`.
+- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`moltbot status --json`).
 - **Web Chat stuck**: confirm the gateway is running on the remote host and the forwarded port matches the gateway WS port; the UI requires a healthy WS connection.
 - **Node IP shows 127.0.0.1**: expected with the SSH tunnel. Switch **Transport** to **Direct (ws/wss)** if you want the gateway to see the real client IP.
 - **Voice Wake**: trigger phrases are forwarded automatically in remote mode; no separate forwarder is needed.
 
 ## Notification sounds
-Pick sounds per notification from scripts with `clawdbot` and `node.invoke`, e.g.:
+Pick sounds per notification from scripts with `moltbot` and `node.invoke`, e.g.:
 
 ```bash
-clawdbot nodes notify --node <id> --title "Ping" --body "Remote gateway ready" --sound Glass
+moltbot nodes notify --node <id> --title "Ping" --body "Remote gateway ready" --sound Glass
 ```
 
 There is no global “default sound” toggle in the app anymore; callers choose a sound (or none) per request.

docs/platforms/mac/signing.md

@@ -5,13 +5,13 @@ read_when:
 ---
 # mac signing (debug builds)
 
-This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/package-mac-app.sh), which now:
+This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh), which now:
 
 - sets a stable debug bundle identifier: `com.clawdbot.mac.debug`
 - writes the Info.plist with that bundle id (override via `BUNDLE_ID=...`)
-- calls [`scripts/codesign-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/codesign-mac-app.sh) to sign the main binary and app bundle so macOS treats each rebuild as the same signed bundle and keeps TCC permissions (notifications, accessibility, screen recording, mic, speech). For stable permissions, use a real signing identity; ad-hoc is opt-in and fragile (see [macOS permissions](/platforms/mac/permissions)).
+- calls [`scripts/codesign-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/codesign-mac-app.sh) to sign the main binary and app bundle so macOS treats each rebuild as the same signed bundle and keeps TCC permissions (notifications, accessibility, screen recording, mic, speech). For stable permissions, use a real signing identity; ad-hoc is opt-in and fragile (see [macOS permissions](/platforms/mac/permissions)).
 - uses `CODESIGN_TIMESTAMP=auto` by default; it enables trusted timestamps for Developer ID signatures. Set `CODESIGN_TIMESTAMP=off` to skip timestamping (offline debug builds).
-- inject build metadata into Info.plist: `ClawdbotBuildTimestamp` (UTC) and `ClawdbotGitCommit` (short hash) so the About pane can show build, git, and debug/release channel.
+- inject build metadata into Info.plist: `MoltbotBuildTimestamp` (UTC) and `MoltbotGitCommit` (short hash) so the About pane can show build, git, and debug/release channel.
 - **Packaging requires Node 22+**: the script runs TS builds and the Control UI build.
 - reads `SIGN_IDENTITY` from the environment. Add `export SIGN_IDENTITY="Apple Development: Your Name (TEAMID)"` (or your Developer ID Application cert) to your shell rc to always sign with your cert. Ad-hoc signing requires explicit opt-in via `ALLOW_ADHOC_SIGNING=1` or `SIGN_IDENTITY="-"` (not recommended for permission testing).
 - runs a Team ID audit after signing and fails if any Mach-O inside the app bundle is signed by a different Team ID. Set `SKIP_TEAM_ID_CHECK=1` to bypass.
@@ -33,11 +33,11 @@ When signing with `SIGN_IDENTITY="-"` (ad-hoc), the script automatically disable
 ## Build metadata for About
 
 `package-mac-app.sh` stamps the bundle with:
-- `ClawdbotBuildTimestamp`: ISO8601 UTC at package time
-- `ClawdbotGitCommit`: short git hash (or `unknown` if unavailable)
+- `MoltbotBuildTimestamp`: ISO8601 UTC at package time
+- `MoltbotGitCommit`: short git hash (or `unknown` if unavailable)
 
 The About tab reads these keys to show version, build date, git commit, and whether it’s a debug build (via `#if DEBUG`). Run the packager to refresh these values after code changes.
 
 ## Why
 
-TCC permissions are tied to the bundle identifier *and* code signature. Unsigned debug builds with changing UUIDs were causing macOS to forget grants after each rebuild. Signing the binaries (ad‑hoc by default) and keeping a fixed bundle id/path (`dist/Clawdbot.app`) preserves the grants between builds, matching the VibeTunnel approach.
+TCC permissions are tied to the bundle identifier *and* code signature. Unsigned debug builds with changing UUIDs were causing macOS to forget grants after each rebuild. Signing the binaries (ad‑hoc by default) and keeping a fixed bundle id/path (`dist/Moltbot.app`) preserves the grants between builds, matching the VibeTunnel approach.

docs/platforms/mac/skills.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Skills (macOS)
 
-The macOS app surfaces Clawdbot skills via the gateway; it does not parse skills locally.
+The macOS app surfaces Moltbot skills via the gateway; it does not parse skills locally.
 
 ## Data source
 - `skills.status` (gateway) returns all skills plus eligibility and missing requirements
@@ -20,7 +20,7 @@ The macOS app surfaces Clawdbot skills via the gateway; it does not parse skills
   (brew when available, otherwise node manager from `skills.install`, default npm).
 
 ## Env/API keys
-- The app stores keys in `~/.clawdbot/clawdbot.json` under `skills.entries.<skillKey>`.
+- The app stores keys in `~/.clawdbot/moltbot.json` under `skills.entries.<skillKey>`.
 - `skills.update` patches `enabled`, `apiKey`, and `env`.
 
 ## Remote mode

docs/platforms/mac/webchat.md

@@ -18,7 +18,7 @@ agent (with a session switcher for other sessions).
 - Manual: Lobster menu → “Open Chat”.
 - Auto‑open for testing:
   ```bash
-  dist/Clawdbot.app/Contents/MacOS/Clawdbot --webchat
+  dist/Moltbot.app/Contents/MacOS/Moltbot --webchat
   ```
 - Logs: `./scripts/clawlog.sh` (subsystem `com.clawdbot`, category `WebChatSwiftUI`).
 

docs/platforms/mac/xpc.md

@@ -1,11 +1,11 @@
 ---
-summary: "macOS IPC architecture for Clawdbot app, gateway node transport, and PeekabooBridge"
+summary: "macOS IPC architecture for Moltbot app, gateway node transport, and PeekabooBridge"
 read_when:
   - Editing IPC contracts or menu bar app IPC
 ---
-# Clawdbot macOS IPC architecture
+# Moltbot macOS IPC architecture
 
-**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `clawdbot-mac` debug CLI exists for discovery/connect checks; agent actions still flow through the Gateway WebSocket and `node.invoke`. UI automation uses PeekabooBridge.
+**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `moltbot-mac` debug CLI exists for discovery/connect checks; agent actions still flow through the Gateway WebSocket and `node.invoke`. UI automation uses PeekabooBridge.
 
 ## Goals
 - Single GUI app instance that owns all TCC-facing work (notifications, screen recording, mic, speech, AppleScript).
@@ -32,7 +32,7 @@ Agent -> Gateway -> Node Service (WS)
 
 ### PeekabooBridge (UI automation)
 - UI automation uses a separate UNIX socket named `bridge.sock` and the PeekabooBridge JSON protocol.
-- Host preference order (client-side): Peekaboo.app → Claude.app → Clawdbot.app → local execution.
+- Host preference order (client-side): Peekaboo.app → Claude.app → Moltbot.app → local execution.
 - Security: bridge hosts require an allowed TeamID; DEBUG-only same-UID escape hatch is guarded by `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1` (Peekaboo convention).
 - See: [PeekabooBridge usage](/platforms/mac/peekaboo) for details.
 

docs/platforms/macos-vm.md

@@ -1,13 +1,13 @@
 ---
-summary: "Run Clawdbot in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage"
+summary: "Run Moltbot in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage"
 read_when:
-  - You want Clawdbot isolated from your main macOS environment
+  - You want Moltbot isolated from your main macOS environment
   - You want iMessage integration (BlueBubbles) in a sandbox
   - You want a resettable macOS environment you can clone
   - You want to compare local vs hosted macOS VM options
 ---
 
-# Clawdbot on macOS VMs (Sandboxing)
+# Moltbot on macOS VMs (Sandboxing)
 
 ## Recommended default (most users)
 
@@ -21,7 +21,7 @@ Use a macOS VM when you specifically need macOS-only capabilities (iMessage/Blue
 
 ### Local VM on your Apple Silicon Mac (Lume)
 
-Run Clawdbot in a sandboxed macOS VM on your existing Apple Silicon Mac using [Lume](https://cua.ai/docs/lume).
+Run Moltbot in a sandboxed macOS VM on your existing Apple Silicon Mac using [Lume](https://cua.ai/docs/lume).
 
 This gives you:
 - Full macOS environment in isolation (your host stays clean)
@@ -42,10 +42,10 @@ Once you have SSH access to a macOS VM, continue at step 6 below.
 ## Quick path (Lume, experienced users)
 
 1. Install Lume
-2. `lume create clawdbot --os macos --ipsw latest`
+2. `lume create moltbot --os macos --ipsw latest`
 3. Complete Setup Assistant, enable Remote Login (SSH)
-4. `lume run clawdbot --no-display`
-5. SSH in, install Clawdbot, configure channels
+4. `lume run moltbot --no-display`
+5. SSH in, install Moltbot, configure channels
 6. Done
 
 ---
@@ -84,7 +84,7 @@ Docs: [Lume Installation](https://cua.ai/docs/lume/guide/getting-started/install
 ## 2) Create the macOS VM
 
 ```bash
-lume create clawdbot --os macos --ipsw latest
+lume create moltbot --os macos --ipsw latest
 ```
 
 This downloads macOS and creates the VM. A VNC window opens automatically.
@@ -110,7 +110,7 @@ After setup completes, enable SSH:
 ## 4) Get the VM's IP address
 
 ```bash
-lume get clawdbot
+lume get moltbot
 ```
 
 Look for the IP address (usually `192.168.64.x`).
@@ -127,13 +127,13 @@ Replace `youruser` with the account you created, and the IP with your VM's IP.
 
 ---
 
-## 6) Install Clawdbot
+## 6) Install Moltbot
 
 Inside the VM:
 
 ```bash
-npm install -g clawdbot@latest
-clawdbot onboard --install-daemon
+npm install -g moltbot@latest
+moltbot onboard --install-daemon
 ```
 
 Follow the onboarding prompts to set up your model provider (Anthropic, OpenAI, etc.).
@@ -145,7 +145,7 @@ Follow the onboarding prompts to set up your model provider (Anthropic, OpenAI,
 Edit the config file:
 
 ```bash
-nano ~/.clawdbot/clawdbot.json
+nano ~/.clawdbot/moltbot.json
 ```
 
 Add your channels:
@@ -167,7 +167,7 @@ Add your channels:
 Then login to WhatsApp (scan QR):
 
 ```bash
-clawdbot channels login
+moltbot channels login
 ```
 
 ---
@@ -177,23 +177,23 @@ clawdbot channels login
 Stop the VM and restart without display:
 
 ```bash
-lume stop clawdbot
-lume run clawdbot --no-display
+lume stop moltbot
+lume run moltbot --no-display
 ```
 
-The VM runs in the background. Clawdbot's daemon keeps the gateway running.
+The VM runs in the background. Moltbot's daemon keeps the gateway running.
 
 To check status:
 
 ```bash
-ssh youruser@192.168.64.X "clawdbot status"
+ssh youruser@192.168.64.X "moltbot status"
 ```
 
 ---
 
 ## Bonus: iMessage integration
 
-This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to Clawdbot.
+This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to Moltbot.
 
 Inside the VM:
 
@@ -202,7 +202,7 @@ Inside the VM:
 3. Enable the Web API and set a password
 4. Point BlueBubbles webhooks at your gateway (example: `https://your-gateway-host:3000/bluebubbles-webhook?password=<password>`)
 
-Add to your Clawdbot config:
+Add to your Moltbot config:
 
 ```json
 {
@@ -227,16 +227,16 @@ Full setup details: [BlueBubbles channel](/channels/bluebubbles)
 Before customizing further, snapshot your clean state:
 
 ```bash
-lume stop clawdbot
-lume clone clawdbot clawdbot-golden
+lume stop moltbot
+lume clone moltbot moltbot-golden
 ```
 
 Reset anytime:
 
 ```bash
-lume stop clawdbot && lume delete clawdbot
-lume clone clawdbot-golden clawdbot
-lume run clawdbot --no-display
+lume stop moltbot && lume delete moltbot
+lume clone moltbot-golden moltbot
+lume run moltbot --no-display
 ```
 
 ---
@@ -257,9 +257,9 @@ For true always-on, consider a dedicated Mac mini or a small VPS. See [VPS hosti
 | Problem | Solution |
 |---------|----------|
 | Can't SSH into VM | Check "Remote Login" is enabled in VM's System Settings |
-| VM IP not showing | Wait for VM to fully boot, run `lume get clawdbot` again |
+| VM IP not showing | Wait for VM to fully boot, run `lume get moltbot` again |
 | Lume command not found | Add `~/.local/bin` to your PATH |
-| WhatsApp QR not scanning | Ensure you're logged into the VM (not host) when running `clawdbot channels login` |
+| WhatsApp QR not scanning | Ensure you're logged into the VM (not host) when running `moltbot channels login` |
 
 ---
 

docs/platforms/macos.md

@@ -1,12 +1,12 @@
 ---
-summary: "Clawdbot macOS companion app (menu bar + gateway broker)"
+summary: "Moltbot macOS companion app (menu bar + gateway broker)"
 read_when:
   - Implementing macOS app features
   - Changing gateway lifecycle or node bridging on macOS
 ---
-# Clawdbot macOS Companion (menu bar + gateway broker)
+# Moltbot macOS Companion (menu bar + gateway broker)
 
-The macOS app is the **menu‑bar companion** for Clawdbot. It owns permissions,
+The macOS app is the **menu‑bar companion** for Moltbot. It owns permissions,
 manages/attaches to the Gateway locally (launchd or manual), and exposes macOS
 capabilities to the agent as a node.
 
@@ -19,12 +19,12 @@ capabilities to the agent as a node.
 - Exposes macOS‑only tools (Canvas, Camera, Screen Recording, `system.run`).
 - Starts the local node host service in **remote** mode (launchd), and stops it in **local** mode.
 - Optionally hosts **PeekabooBridge** for UI automation.
-- Installs the global CLI (`clawdbot`) via npm/pnpm on request (bun not recommended for the Gateway runtime).
+- Installs the global CLI (`moltbot`) via npm/pnpm on request (bun not recommended for the Gateway runtime).
 
 ## Local vs remote mode
 
 - **Local** (default): the app attaches to a running local Gateway if present;
-  otherwise it enables the launchd service via `clawdbot gateway install`.
+  otherwise it enables the launchd service via `moltbot gateway install`.
 - **Remote**: the app connects to a Gateway over SSH/Tailscale and never starts
   a local process.
   The app starts the local **node host service** so the remote Gateway can reach this Mac.
@@ -43,7 +43,7 @@ launchctl bootout gui/$UID/com.clawdbot.gateway
 Replace the label with `com.clawdbot.<profile>` when running a named profile.
 
 If the LaunchAgent isn’t installed, enable it from the app or run
-`clawdbot gateway install`.
+`moltbot gateway install`.
 
 ## Node capabilities (mac)
 
@@ -105,14 +105,14 @@ Notes:
 
 ## Deep links
 
-The app registers the `clawdbot://` URL scheme for local actions.
+The app registers the `moltbot://` URL scheme for local actions.
 
-### `clawdbot://agent`
+### `moltbot://agent`
 
 Triggers a Gateway `agent` request.
 
 ```bash
-open 'clawdbot://agent?message=Hello%20from%20deep%20link'
+open 'moltbot://agent?message=Hello%20from%20deep%20link'
 ```
 
 Query parameters:
@@ -129,7 +129,7 @@ Safety:
 
 ## Onboarding flow (typical)
 
-1) Install and launch **Clawdbot.app**.
+1) Install and launch **Moltbot.app**.
 2) Complete the permissions checklist (TCC prompts).
 3) Ensure **Local** mode is active and the Gateway is running.
 4) Install the CLI if you want terminal access.
@@ -137,7 +137,7 @@ Safety:
 ## Build & dev workflow (native)
 
 - `cd apps/macos && swift build`
-- `swift run Clawdbot` (or Xcode)
+- `swift run Moltbot` (or Xcode)
 - Package app: `scripts/package-mac-app.sh`
 
 ## Debug gateway connectivity (macOS CLI)
@@ -147,8 +147,8 @@ logic that the macOS app uses, without launching the app.
 
 ```bash
 cd apps/macos
-swift run clawdbot-mac connect --json
-swift run clawdbot-mac discover --timeout 3000 --json
+swift run moltbot-mac connect --json
+swift run moltbot-mac discover --timeout 3000 --json
 ```
 
 Connect options:
@@ -163,7 +163,7 @@ Discovery options:
 - `--timeout <ms>`: overall discovery window (default: `2000`)
 - `--json`: structured output for diffing
 
-Tip: compare against `clawdbot gateway discover --json` to see whether the
+Tip: compare against `moltbot gateway discover --json` to see whether the
 macOS app’s discovery pipeline (NWBrowser + tailnet DNS‑SD fallback) differs from
 the Node CLI’s `dns-sd` based discovery.
 

docs/platforms/oracle.md

@@ -1,18 +1,18 @@
 ---
-summary: "Clawdbot on Oracle Cloud (Always Free ARM)"
+summary: "Moltbot on Oracle Cloud (Always Free ARM)"
 read_when:
-  - Setting up Clawdbot on Oracle Cloud
-  - Looking for low-cost VPS hosting for Clawdbot
-  - Want 24/7 Clawdbot on a small server
+  - Setting up Moltbot on Oracle Cloud
+  - Looking for low-cost VPS hosting for Moltbot
+  - Want 24/7 Moltbot on a small server
 ---
 
-# Clawdbot on Oracle Cloud (OCI)
+# Moltbot on Oracle Cloud (OCI)
 
 ## Goal
 
-Run a persistent Clawdbot Gateway on Oracle Cloud's **Always Free** ARM tier.
+Run a persistent Moltbot Gateway on Oracle Cloud's **Always Free** ARM tier.
 
-Oracle’s free tier can be a great fit for Clawdbot (especially if you already have an OCI account), but it comes with tradeoffs:
+Oracle’s free tier can be a great fit for Moltbot (especially if you already have an OCI account), but it comes with tradeoffs:
 
 - ARM architecture (most things work, but some binaries may be x86-only)
 - Capacity and signup can be finicky
@@ -40,7 +40,7 @@ Oracle’s free tier can be a great fit for Clawdbot (especially if you already
 1. Log into [Oracle Cloud Console](https://cloud.oracle.com/)
 2. Navigate to **Compute → Instances → Create Instance**
 3. Configure:
-   - **Name:** `clawdbot`
+   - **Name:** `moltbot`
    - **Image:** Ubuntu 24.04 (aarch64)
    - **Shape:** `VM.Standard.A1.Flex` (Ampere ARM)
    - **OCPUs:** 2 (or up to 4)
@@ -69,7 +69,7 @@ sudo apt install -y build-essential
 
 ```bash
 # Set hostname
-sudo hostnamectl set-hostname clawdbot
+sudo hostnamectl set-hostname moltbot
 
 # Set password for ubuntu user
 sudo passwd ubuntu
@@ -82,19 +82,19 @@ sudo loginctl enable-linger ubuntu
 
 ```bash
 curl -fsSL https://tailscale.com/install.sh | sh
-sudo tailscale up --ssh --hostname=clawdbot
+sudo tailscale up --ssh --hostname=moltbot
 ```
 
-This enables Tailscale SSH, so you can connect via `ssh clawdbot` from any device on your tailnet — no public IP needed.
+This enables Tailscale SSH, so you can connect via `ssh moltbot` from any device on your tailnet — no public IP needed.
 
 Verify:
 ```bash
 tailscale status
 ```
 
-**From now on, connect via Tailscale:** `ssh ubuntu@clawdbot` (or use the Tailscale IP).
+**From now on, connect via Tailscale:** `ssh ubuntu@moltbot` (or use the Tailscale IP).
 
-## 5) Install Clawdbot
+## 5) Install Moltbot
 
 ```bash
 curl -fsSL https://molt.bot/install.sh | bash
@@ -111,27 +111,27 @@ Use token auth as the default. It’s predictable and avoids needing any “inse
 
 ```bash
 # Keep the Gateway private on the VM
-clawdbot config set gateway.bind loopback
+moltbot config set gateway.bind loopback
 
 # Require auth for the Gateway + Control UI
-clawdbot config set gateway.auth.mode token
-clawdbot doctor --generate-gateway-token
+moltbot config set gateway.auth.mode token
+moltbot doctor --generate-gateway-token
 
 # Expose over Tailscale Serve (HTTPS + tailnet access)
-clawdbot config set gateway.tailscale.mode serve
-clawdbot config set gateway.trustedProxies '["127.0.0.1"]'
+moltbot config set gateway.tailscale.mode serve
+moltbot config set gateway.trustedProxies '["127.0.0.1"]'
 
-systemctl --user restart clawdbot-gateway
+systemctl --user restart moltbot-gateway
 ```
 
 ## 7) Verify
 
 ```bash
 # Check version
-clawdbot --version
+moltbot --version
 
 # Check daemon status
-systemctl --user status clawdbot-gateway
+systemctl --user status moltbot-gateway
 
 # Check Tailscale Serve
 tailscale serve status
@@ -159,7 +159,7 @@ This blocks SSH on port 22, HTTP, HTTPS, and everything else at the network edge
 From any device on your Tailscale network:
 
 ```
-https://clawdbot.<tailnet-name>.ts.net/
+https://moltbot.<tailnet-name>.ts.net/
 ```
 
 Replace `<tailnet-name>` with your tailnet name (visible in `tailscale status`).
@@ -175,7 +175,7 @@ No SSH tunnel needed. Tailscale provides:
 
 With the VCN locked down (only UDP 41641 open) and the Gateway bound to loopback, you get strong defense-in-depth: public traffic is blocked at the network edge, and admin access happens over your tailnet.
 
-This setup often removes the *need* for extra host-based firewall rules purely to stop Internet-wide SSH brute force — but you should still keep the OS updated, run `clawdbot security audit`, and verify you aren’t accidentally listening on public interfaces.
+This setup often removes the *need* for extra host-based firewall rules purely to stop Internet-wide SSH brute force — but you should still keep the OS updated, run `moltbot security audit`, and verify you aren’t accidentally listening on public interfaces.
 
 ### What's Already Protected
 
@@ -191,7 +191,7 @@ This setup often removes the *need* for extra host-based firewall rules purely t
 ### Still Recommended
 
 - **Credential permissions:** `chmod 700 ~/.clawdbot`
-- **Security audit:** `clawdbot security audit`
+- **Security audit:** `moltbot security audit`
 - **System updates:** `sudo apt update && sudo apt upgrade` regularly
 - **Monitor Tailscale:** Review devices in [Tailscale admin console](https://login.tailscale.com/admin)
 
@@ -216,7 +216,7 @@ If Tailscale Serve isn't working, use an SSH tunnel:
 
 ```bash
 # From your local machine (via Tailscale)
-ssh -L 18789:127.0.0.1:18789 ubuntu@clawdbot
+ssh -L 18789:127.0.0.1:18789 ubuntu@moltbot
 ```
 
 Then open `http://localhost:18789`.
@@ -237,14 +237,14 @@ Free tier ARM instances are popular. Try:
 sudo tailscale status
 
 # Re-authenticate
-sudo tailscale up --ssh --hostname=clawdbot --reset
+sudo tailscale up --ssh --hostname=moltbot --reset
 ```
 
 ### Gateway won't start
 ```bash
-clawdbot gateway status
-clawdbot doctor --non-interactive
-journalctl --user -u clawdbot-gateway -n 50
+moltbot gateway status
+moltbot doctor --non-interactive
+journalctl --user -u moltbot-gateway -n 50
 ```
 
 ### Can't reach Control UI
@@ -256,7 +256,7 @@ tailscale serve status
 curl http://localhost:18789
 
 # Restart if needed
-systemctl --user restart clawdbot-gateway
+systemctl --user restart moltbot-gateway
 ```
 
 ### ARM binary issues
@@ -277,7 +277,7 @@ All state lives in:
 
 Back up periodically:
 ```bash
-tar -czvf clawdbot-backup.tar.gz ~/.clawdbot ~/clawd
+tar -czvf moltbot-backup.tar.gz ~/.clawdbot ~/clawd
 ```
 
 ---

docs/platforms/raspberry-pi.md

@@ -1,16 +1,16 @@
 ---
-summary: "Clawdbot on Raspberry Pi (budget self-hosted setup)"
+summary: "Moltbot on Raspberry Pi (budget self-hosted setup)"
 read_when:
-  - Setting up Clawdbot on a Raspberry Pi
-  - Running Clawdbot on ARM devices
+  - Setting up Moltbot on a Raspberry Pi
+  - Running Moltbot on ARM devices
   - Building a cheap always-on personal AI
 ---
 
-# Clawdbot on Raspberry Pi
+# Moltbot on Raspberry Pi
 
 ## Goal
 
-Run a persistent, always-on Clawdbot Gateway on a Raspberry Pi for **~$35-80** one-time cost (no monthly fees).
+Run a persistent, always-on Moltbot Gateway on a Raspberry Pi for **~$35-80** one-time cost (no monthly fees).
 
 Perfect for:
 - 24/7 personal AI assistant
@@ -105,7 +105,7 @@ echo 'vm.swappiness=10' | sudo tee -a /etc/sysctl.conf
 sudo sysctl -p
 ```
 
-## 6) Install Clawdbot
+## 6) Install Moltbot
 
 ### Option A: Standard Install (Recommended)
 
@@ -116,8 +116,8 @@ curl -fsSL https://molt.bot/install.sh | bash
 ### Option B: Hackable Install (For tinkering)
 
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/moltbot/moltbot.git
+cd moltbot
 npm install
 npm run build
 npm link
@@ -128,7 +128,7 @@ The hackable install gives you direct access to logs and code — useful for deb
 ## 7) Run Onboarding
 
 ```bash
-clawdbot onboard --install-daemon
+moltbot onboard --install-daemon
 ```
 
 Follow the wizard:
@@ -141,13 +141,13 @@ Follow the wizard:
 
 ```bash
 # Check status
-clawdbot status
+moltbot status
 
 # Check service
-sudo systemctl status clawdbot
+sudo systemctl status moltbot
 
 # View logs
-journalctl -u clawdbot -f
+journalctl -u moltbot -f
 ```
 
 ## 9) Access the Dashboard
@@ -170,8 +170,8 @@ curl -fsSL https://tailscale.com/install.sh | sh
 sudo tailscale up
 
 # Update config
-clawdbot config set gateway.bind tailnet
-sudo systemctl restart clawdbot
+moltbot config set gateway.bind tailnet
+sudo systemctl restart moltbot
 ```
 
 ---
@@ -218,7 +218,7 @@ htop
 
 ### Binary Compatibility
 
-Most Clawdbot features work on ARM64, but some external binaries may need ARM builds:
+Most Moltbot features work on ARM64, but some external binaries may need ARM builds:
 
 | Tool | ARM64 Status | Notes |
 |------|--------------|-------|
@@ -268,13 +268,13 @@ The onboarding wizard sets this up, but to verify:
 
 ```bash
 # Check service is enabled
-sudo systemctl is-enabled clawdbot
+sudo systemctl is-enabled moltbot
 
 # Enable if not
-sudo systemctl enable clawdbot
+sudo systemctl enable moltbot
 
 # Start on boot
-sudo systemctl start clawdbot
+sudo systemctl start moltbot
 ```
 
 ---
@@ -301,12 +301,12 @@ free -h
 
 ```bash
 # Check logs
-journalctl -u clawdbot --no-pager -n 100
+journalctl -u moltbot --no-pager -n 100
 
 # Common fix: rebuild
-cd ~/clawdbot  # if using hackable install
+cd ~/moltbot  # if using hackable install
 npm run build
-sudo systemctl restart clawdbot
+sudo systemctl restart moltbot
 ```
 
 ### ARM Binary Issues

docs/platforms/windows.md

@@ -1,12 +1,12 @@
 ---
 summary: "Windows (WSL2) support + companion app status"
 read_when:
-  - Installing Clawdbot on Windows
+  - Installing Moltbot on Windows
   - Looking for Windows companion app status
 ---
 # Windows (WSL2)
 
-Clawdbot on Windows is recommended **via WSL2** (Ubuntu recommended). The
+Moltbot on Windows is recommended **via WSL2** (Ubuntu recommended). The
 CLI + Gateway run inside Linux, which keeps the runtime consistent and makes
 tooling far more compatible (Node/Bun/pnpm, Linux binaries, skills). Native
 Windows installs are untested and more problematic.
@@ -27,19 +27,19 @@ Native Windows companion apps are planned.
 Inside WSL2:
 
 ```
-clawdbot onboard --install-daemon
+moltbot onboard --install-daemon
 ```
 
 Or:
 
 ```
-clawdbot gateway install
+moltbot gateway install
 ```
 
 Or:
 
 ```
-clawdbot configure
+moltbot configure
 ```
 
 Select **Gateway service** when prompted.
@@ -47,7 +47,7 @@ Select **Gateway service** when prompted.
 Repair/migrate:
 
 ```
-clawdbot doctor
+moltbot doctor
 ```
 
 ## Advanced: expose WSL services over LAN (portproxy)
@@ -89,7 +89,7 @@ netsh interface portproxy add v4tov4 listenport=$ListenPort listenaddress=0.0.0.
 Notes:
 - SSH from another machine targets the **Windows host IP** (example: `ssh user@windows-host -p 2222`).
 - Remote nodes must point at a **reachable** Gateway URL (not `127.0.0.1`); use
-  `clawdbot status --all` to confirm.
+  `moltbot status --all` to confirm.
 - Use `listenaddress=0.0.0.0` for LAN access; `127.0.0.1` keeps it local only.
 - If you want this automatic, register a Scheduled Task to run the refresh
   step at login.
@@ -132,17 +132,17 @@ Re-open Ubuntu, then verify:
 systemctl --user status
 ```
 
-### 3) Install Clawdbot (inside WSL)
+### 3) Install Moltbot (inside WSL)
 
 Follow the Linux Getting Started flow inside WSL:
 
 ```bash
-git clone https://github.com/clawdbot/clawdbot.git
-cd clawdbot
+git clone https://github.com/moltbot/moltbot.git
+cd moltbot
 pnpm install
 pnpm ui:build # auto-installs UI deps on first run
 pnpm build
-clawdbot onboard
+moltbot onboard
 ```
 
 Full guide: [Getting Started](/start/getting-started)