@gguf/pigbot 0.0.6 → 0.0.7

package/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/moltbot/moltbot/blob/main/scripts/package-mac-app.sh), which now:
+This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/openclaw/openclaw/blob/main/scripts/package-mac-app.sh), which now:
 
-- sets a stable debug bundle identifier: `bot.molt.mac.debug`
+- sets a stable debug bundle identifier: `ai.openclaw.mac.debug`
 - writes the Info.plist with that bundle id (override via `BUNDLE_ID=...`)
-- 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)).
+- calls [`scripts/codesign-mac-app.sh`](https://github.com/openclaw/openclaw/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: `MoltbotBuildTimestamp` (UTC) and `MoltbotGitCommit` (short hash) so the About pane can show build, git, and debug/release channel.
+- inject build metadata into Info.plist: `OpenClawBuildTimestamp` (UTC) and `OpenClawGitCommit` (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:
-- `MoltbotBuildTimestamp`: ISO8601 UTC at package time
-- `MoltbotGitCommit`: short git hash (or `unknown` if unavailable)
+- `OpenClawBuildTimestamp`: ISO8601 UTC at package time
+- `OpenClawGitCommit`: 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/Moltbot.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/OpenClaw.app`) preserves the grants between builds, matching the VibeTunnel approach.

package/docs/platforms/mac/skills.md

@@ -6,21 +6,21 @@ read_when:
 ---
 # Skills (macOS)
 
-The macOS app surfaces Moltbot skills via the gateway; it does not parse skills locally.
+The macOS app surfaces OpenClaw skills via the gateway; it does not parse skills locally.
 
 ## Data source
 - `skills.status` (gateway) returns all skills plus eligibility and missing requirements
   (including allowlist blocks for bundled skills).
-- Requirements are derived from `metadata.clawdbot.requires` in each `SKILL.md`.
+- Requirements are derived from `metadata.openclaw.requires` in each `SKILL.md`.
 
 ## Install actions
-- `metadata.clawdbot.install` defines install options (brew/node/go/uv).
+- `metadata.openclaw.install` defines install options (brew/node/go/uv).
 - The app calls `skills.install` to run installers on the gateway host.
 - The gateway surfaces only one preferred installer when multiple are provided
   (brew when available, otherwise node manager from `skills.install`, default npm).
 
 ## Env/API keys
-- The app stores keys in `~/.clawdbot/moltbot.json` under `skills.entries.<skillKey>`.
+- The app stores keys in `~/.openclaw/openclaw.json` under `skills.entries.<skillKey>`.
 - `skills.update` patches `enabled`, `apiKey`, and `env`.
 
 ## Remote mode

package/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/Moltbot.app/Contents/MacOS/Moltbot --webchat
+  dist/OpenClaw.app/Contents/MacOS/OpenClaw --webchat
   ```
 - Logs: `./scripts/clawlog.sh` (subsystem `bot.molt`, category `WebChatSwiftUI`).
 

package/docs/platforms/mac/xpc.md

@@ -1,11 +1,11 @@
 ---
-summary: "macOS IPC architecture for Moltbot app, gateway node transport, and PeekabooBridge"
+summary: "macOS IPC architecture for OpenClaw app, gateway node transport, and PeekabooBridge"
 read_when:
   - Editing IPC contracts or menu bar app IPC
 ---
-# Moltbot macOS IPC architecture
+# OpenClaw macOS IPC architecture
 
-**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.
+**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `openclaw-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 → Moltbot.app → local execution.
+- Host preference order (client-side): Peekaboo.app → Claude.app → OpenClaw.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.
 

package/docs/platforms/macos-vm.md

@@ -1,13 +1,13 @@
 ---
-summary: "Run Moltbot in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage"
+summary: "Run OpenClaw in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage"
 read_when:
-  - You want Moltbot isolated from your main macOS environment
+  - You want OpenClaw 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
 ---
 
-# Moltbot on macOS VMs (Sandboxing)
+# OpenClaw 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 Moltbot in a sandboxed macOS VM on your existing Apple Silicon Mac using [Lume](https://cua.ai/docs/lume).
+Run OpenClaw 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 moltbot --os macos --ipsw latest`
+2. `lume create openclaw --os macos --ipsw latest`
 3. Complete Setup Assistant, enable Remote Login (SSH)
-4. `lume run moltbot --no-display`
-5. SSH in, install Moltbot, configure channels
+4. `lume run openclaw --no-display`
+5. SSH in, install OpenClaw, 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 moltbot --os macos --ipsw latest
+lume create openclaw --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 moltbot
+lume get openclaw
 ```
 
 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 Moltbot
+## 6) Install OpenClaw
 
 Inside the VM:
 
 ```bash
-npm install -g moltbot@latest
-moltbot onboard --install-daemon
+npm install -g openclaw@latest
+openclaw 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/moltbot.json
+nano ~/.openclaw/openclaw.json
 ```
 
 Add your channels:
@@ -167,7 +167,7 @@ Add your channels:
 Then login to WhatsApp (scan QR):
 
 ```bash
-moltbot channels login
+openclaw channels login
 ```
 
 ---
@@ -177,23 +177,23 @@ moltbot channels login
 Stop the VM and restart without display:
 
 ```bash
-lume stop moltbot
-lume run moltbot --no-display
+lume stop openclaw
+lume run openclaw --no-display
 ```
 
-The VM runs in the background. Moltbot's daemon keeps the gateway running.
+The VM runs in the background. OpenClaw's daemon keeps the gateway running.
 
 To check status:
 
 ```bash
-ssh youruser@192.168.64.X "moltbot status"
+ssh youruser@192.168.64.X "openclaw status"
 ```
 
 ---
 
 ## Bonus: iMessage integration
 
-This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to Moltbot.
+This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to OpenClaw.
 
 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 Moltbot config:
+Add to your OpenClaw config:
 
 ```json
 {
@@ -227,16 +227,16 @@ Full setup details: [BlueBubbles channel](/channels/bluebubbles)
 Before customizing further, snapshot your clean state:
 
 ```bash
-lume stop moltbot
-lume clone moltbot moltbot-golden
+lume stop openclaw
+lume clone openclaw openclaw-golden
 ```
 
 Reset anytime:
 
 ```bash
-lume stop moltbot && lume delete moltbot
-lume clone moltbot-golden moltbot
-lume run moltbot --no-display
+lume stop openclaw && lume delete openclaw
+lume clone openclaw-golden openclaw
+lume run openclaw --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 moltbot` again |
+| VM IP not showing | Wait for VM to fully boot, run `lume get openclaw` 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 `moltbot channels login` |
+| WhatsApp QR not scanning | Ensure you're logged into the VM (not host) when running `openclaw channels login` |
 
 ---
 

package/docs/platforms/macos.md

@@ -1,12 +1,12 @@
 ---
-summary: "Moltbot macOS companion app (menu bar + gateway broker)"
+summary: "OpenClaw macOS companion app (menu bar + gateway broker)"
 read_when:
   - Implementing macOS app features
   - Changing gateway lifecycle or node bridging on macOS
 ---
-# Moltbot macOS Companion (menu bar + gateway broker)
+# OpenClaw macOS Companion (menu bar + gateway broker)
 
-The macOS app is the **menu‑bar companion** for Moltbot. It owns permissions,
+The macOS app is the **menu‑bar companion** for OpenClaw. 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 (`moltbot`) via npm/pnpm on request (bun not recommended for the Gateway runtime).
+- Installs the global CLI (`openclaw`) 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 `moltbot gateway install`.
+  otherwise it enables the launchd service via `openclaw 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.
@@ -33,7 +33,7 @@ The app does not spawn the Gateway as a child process.
 ## Launchd control
 
 The app manages a per‑user LaunchAgent labeled `bot.molt.gateway`
-(or `bot.molt.<profile>` when using `--profile`/`CLAWDBOT_PROFILE`; legacy `com.clawdbot.*` still unloads).
+(or `bot.molt.<profile>` when using `--profile`/`OPENCLAW_PROFILE`; legacy `com.openclaw.*` still unloads).
 
 ```bash
 launchctl kickstart -k gui/$UID/bot.molt.gateway
@@ -43,7 +43,7 @@ launchctl bootout gui/$UID/bot.molt.gateway
 Replace the label with `bot.molt.<profile>` when running a named profile.
 
 If the LaunchAgent isn’t installed, enable it from the app or run
-`moltbot gateway install`.
+`openclaw gateway install`.
 
 ## Node capabilities (mac)
 
@@ -74,7 +74,7 @@ Gateway -> Node Service (WS)
 Security + ask + allowlist are stored locally on the Mac in:
 
 ```
-~/.clawdbot/exec-approvals.json
+~/.openclaw/exec-approvals.json
 ```
 
 Example:
@@ -105,14 +105,14 @@ Notes:
 
 ## Deep links
 
-The app registers the `moltbot://` URL scheme for local actions.
+The app registers the `openclaw://` URL scheme for local actions.
 
-### `moltbot://agent`
+### `openclaw://agent`
 
 Triggers a Gateway `agent` request.
 
 ```bash
-open 'moltbot://agent?message=Hello%20from%20deep%20link'
+open 'openclaw://agent?message=Hello%20from%20deep%20link'
 ```
 
 Query parameters:
@@ -129,7 +129,7 @@ Safety:
 
 ## Onboarding flow (typical)
 
-1) Install and launch **Moltbot.app**.
+1) Install and launch **OpenClaw.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 Moltbot` (or Xcode)
+- `swift run OpenClaw` (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 moltbot-mac connect --json
-swift run moltbot-mac discover --timeout 3000 --json
+swift run openclaw-mac connect --json
+swift run openclaw-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 `moltbot gateway discover --json` to see whether the
+Tip: compare against `openclaw 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.
 

package/docs/platforms/oracle.md

@@ -1,18 +1,18 @@
 ---
-summary: "Moltbot on Oracle Cloud (Always Free ARM)"
+summary: "OpenClaw on Oracle Cloud (Always Free ARM)"
 read_when:
-  - Setting up Moltbot on Oracle Cloud
-  - Looking for low-cost VPS hosting for Moltbot
-  - Want 24/7 Moltbot on a small server
+  - Setting up OpenClaw on Oracle Cloud
+  - Looking for low-cost VPS hosting for OpenClaw
+  - Want 24/7 OpenClaw on a small server
 ---
 
-# Moltbot on Oracle Cloud (OCI)
+# OpenClaw on Oracle Cloud (OCI)
 
 ## Goal
 
-Run a persistent Moltbot Gateway on Oracle Cloud's **Always Free** ARM tier.
+Run a persistent OpenClaw Gateway on Oracle Cloud's **Always Free** ARM tier.
 
-Oracle’s free tier can be a great fit for Moltbot (especially if you already have an OCI account), but it comes with tradeoffs:
+Oracle’s free tier can be a great fit for OpenClaw (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 Moltbot (especially if you already h
 1. Log into [Oracle Cloud Console](https://cloud.oracle.com/)
 2. Navigate to **Compute → Instances → Create Instance**
 3. Configure:
-   - **Name:** `moltbot`
+   - **Name:** `openclaw`
    - **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 moltbot
+sudo hostnamectl set-hostname openclaw
 
 # Set password for ubuntu user
 sudo passwd ubuntu
@@ -82,22 +82,22 @@ sudo loginctl enable-linger ubuntu
 
 ```bash
 curl -fsSL https://tailscale.com/install.sh | sh
-sudo tailscale up --ssh --hostname=moltbot
+sudo tailscale up --ssh --hostname=openclaw
 ```
 
-This enables Tailscale SSH, so you can connect via `ssh moltbot` from any device on your tailnet — no public IP needed.
+This enables Tailscale SSH, so you can connect via `ssh openclaw` from any device on your tailnet — no public IP needed.
 
 Verify:
 ```bash
 tailscale status
 ```
 
-**From now on, connect via Tailscale:** `ssh ubuntu@moltbot` (or use the Tailscale IP).
+**From now on, connect via Tailscale:** `ssh ubuntu@openclaw` (or use the Tailscale IP).
 
-## 5) Install Moltbot
+## 5) Install OpenClaw
 
 ```bash
-curl -fsSL https://molt.bot/install.sh | bash
+curl -fsSL https://openclaw.bot/install.sh | bash
 source ~/.bashrc
 ```
 
@@ -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
-moltbot config set gateway.bind loopback
+openclaw config set gateway.bind loopback
 
 # Require auth for the Gateway + Control UI
-moltbot config set gateway.auth.mode token
-moltbot doctor --generate-gateway-token
+openclaw config set gateway.auth.mode token
+openclaw doctor --generate-gateway-token
 
 # Expose over Tailscale Serve (HTTPS + tailnet access)
-moltbot config set gateway.tailscale.mode serve
-moltbot config set gateway.trustedProxies '["127.0.0.1"]'
+openclaw config set gateway.tailscale.mode serve
+openclaw config set gateway.trustedProxies '["127.0.0.1"]'
 
-systemctl --user restart moltbot-gateway
+systemctl --user restart openclaw-gateway
 ```
 
 ## 7) Verify
 
 ```bash
 # Check version
-moltbot --version
+openclaw --version
 
 # Check daemon status
-systemctl --user status moltbot-gateway
+systemctl --user status openclaw-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://moltbot.<tailnet-name>.ts.net/
+https://openclaw.<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 `moltbot 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 `openclaw security audit`, and verify you aren’t accidentally listening on public interfaces.
 
 ### What's Already Protected
 
@@ -190,8 +190,8 @@ This setup often removes the *need* for extra host-based firewall rules purely t
 
 ### Still Recommended
 
-- **Credential permissions:** `chmod 700 ~/.clawdbot`
-- **Security audit:** `moltbot security audit`
+- **Credential permissions:** `chmod 700 ~/.openclaw`
+- **Security audit:** `openclaw 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@moltbot
+ssh -L 18789:127.0.0.1:18789 ubuntu@openclaw
 ```
 
 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=moltbot --reset
+sudo tailscale up --ssh --hostname=openclaw --reset
 ```
 
 ### Gateway won't start
 ```bash
-moltbot gateway status
-moltbot doctor --non-interactive
-journalctl --user -u moltbot-gateway -n 50
+openclaw gateway status
+openclaw doctor --non-interactive
+journalctl --user -u openclaw-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 moltbot-gateway
+systemctl --user restart openclaw-gateway
 ```
 
 ### ARM binary issues
@@ -272,12 +272,12 @@ Most npm packages work fine. For binaries, look for `linux-arm64` or `aarch64` r
 ## Persistence
 
 All state lives in:
-- `~/.clawdbot/` — config, credentials, session data
-- `~/clawd/` — workspace (SOUL.md, memory, artifacts)
+- `~/.openclaw/` — config, credentials, session data
+- `~/.openclaw/workspace/` — workspace (SOUL.md, memory, artifacts)
 
 Back up periodically:
 ```bash
-tar -czvf moltbot-backup.tar.gz ~/.clawdbot ~/clawd
+tar -czvf openclaw-backup.tar.gz ~/.openclaw ~/.openclaw/workspace
 ```
 
 ---