@gguf/pigbot 0.0.6 → 0.0.7

package/docs/platforms/digitalocean.md

@@ -1,15 +1,15 @@
 ---
-summary: "Moltbot on DigitalOcean (simple paid VPS option)"
+summary: "OpenClaw on DigitalOcean (simple paid VPS option)"
 read_when:
-  - Setting up Moltbot on DigitalOcean
-  - Looking for cheap VPS hosting for Moltbot
+  - Setting up OpenClaw on DigitalOcean
+  - Looking for cheap VPS hosting for OpenClaw
 ---
 
-# Moltbot on DigitalOcean
+# OpenClaw on DigitalOcean
 
 ## Goal
 
-Run a persistent Moltbot Gateway on DigitalOcean for **$6/month** (or $4/mo with reserved pricing).
+Run a persistent OpenClaw 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 Moltbot
+## 3) Install OpenClaw
 
 ```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 Moltbot
-curl -fsSL https://molt.bot/install.sh | bash
+# Install OpenClaw
+curl -fsSL https://openclaw.bot/install.sh | bash
 
 # Verify
-moltbot --version
+openclaw --version
 ```
 
 ## 4) Run Onboarding
 
 ```bash
-moltbot onboard --install-daemon
+openclaw onboard --install-daemon
 ```
 
 The wizard will walk you through:
@@ -87,13 +87,13 @@ The wizard will walk you through:
 
 ```bash
 # Check status
-moltbot status
+openclaw status
 
 # Check service
-systemctl --user status moltbot-gateway.service
+systemctl --user status openclaw-gateway.service
 
 # View logs
-journalctl --user -u moltbot-gateway.service -f
+journalctl --user -u openclaw-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
-moltbot config set gateway.tailscale.mode serve
-moltbot gateway restart
+openclaw config set gateway.tailscale.mode serve
+openclaw gateway restart
 ```
 
 Open: `https://<magicdns>/`
@@ -127,8 +127,8 @@ Notes:
 
 **Option C: Tailnet bind (no Serve)**
 ```bash
-moltbot config set gateway.bind tailnet
-moltbot gateway restart
+openclaw config set gateway.bind tailnet
+openclaw gateway restart
 ```
 
 Open: `http://<tailscale-ip>:18789` (token required).
@@ -137,13 +137,13 @@ Open: `http://<tailscale-ip>:18789` (token required).
 
 ### Telegram
 ```bash
-moltbot pairing list telegram
-moltbot pairing approve telegram <CODE>
+openclaw pairing list telegram
+openclaw pairing approve telegram <CODE>
 ```
 
 ### WhatsApp
 ```bash
-moltbot channels login whatsapp
+openclaw channels login whatsapp
 # Scan QR code
 ```
 
@@ -180,12 +180,12 @@ htop
 ## Persistence
 
 All state lives in:
-- `~/.clawdbot/` — config, credentials, session data
-- `~/clawd/` — workspace (SOUL.md, memory, etc.)
+- `~/.openclaw/` — config, credentials, session data
+- `~/.openclaw/workspace/` — workspace (SOUL.md, memory, etc.)
 
 These survive reboots. Back them up periodically:
 ```bash
-tar -czvf moltbot-backup.tar.gz ~/.clawdbot ~/clawd
+tar -czvf openclaw-backup.tar.gz ~/.openclaw ~/.openclaw/workspace
 ```
 
 ---
@@ -213,9 +213,9 @@ For the full setup guide, see [Oracle Cloud](/platforms/oracle). For signup tips
 
 ### Gateway won't start
 ```bash
-moltbot gateway status
-moltbot doctor --non-interactive
-journalctl -u moltbot --no-pager -n 50
+openclaw gateway status
+openclaw doctor --non-interactive
+journalctl -u openclaw --no-pager -n 50
 ```
 
 ### Port already in use

package/docs/platforms/exe-dev.md

@@ -1,5 +1,5 @@
 ---
-summary: "Run Moltbot Gateway on exe.dev (VM + HTTPS proxy) for remote access"
+summary: "Run OpenClaw 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,181 +7,119 @@ read_when:
 
 # exe.dev
 
-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)
+Goal: OpenClaw Gateway running on an exe.dev VM, reachable from your laptop via: `https://<vm-name>.exe.xyz`
 
-This page assumes **Ubuntu/Debian**. If you picked a different distro, map packages accordingly.
-
-If you’re on any other Linux VPS, the same steps apply — you just won’t use the exe.dev proxy commands.
+This page assumes exe.dev's default **exeuntu** image. If you picked a different distro, map packages accordingly.
 
 ## Beginner quick path
 
-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
+1) [https://exe.new/openclaw](https://exe.new/openclaw)
+2) Fill in your auth key/token as needed
+3) Click on "Agent" next to your VM, and wait...
+4) ???
+5) Profit
 
 ## What you need
 
-- exe.dev account + `ssh exe.dev` working on your laptop
-- SSH keys set up (your laptop → exe.dev)
-- Model auth (OAuth or API key) you want to use
-- Provider credentials (optional): WhatsApp QR scan, Telegram bot token, Discord bot token, …
+- exe.dev account
+- `ssh exe.dev` access to [exe.dev](https://exe.dev) virtual machines (optional)
 
-## 1) Create the VM
 
-From your laptop:
+## Automated Install with Shelley
 
-```bash
-ssh exe.dev new --name=moltbot
-```
+Shelley, [exe.dev](https://exe.dev)'s agent, can install OpenClaw instantly with our
+prompt. The prompt used is as below:
 
-Then connect:
-
-```bash
-ssh moltbot.exe.xyz
-```
-
-Tip: keep this VM **stateful**. Moltbot stores state under `~/.clawdbot/` and `~/clawd/`.
-
-## 2) Install prerequisites (on the VM)
-
-```bash
-sudo apt-get update
-sudo apt-get install -y git curl jq ca-certificates openssl
 ```
-
-### Node 22
-
-Install Node **>= 22.12** (any method is fine). Quick check:
-
-```bash
-node -v
+Set up OpenClaw (https://docs.openclaw.ai/install) on this VM. Use the non-interactive and accept-risk flags for openclaw onboarding. Add the supplied auth or token as needed. Configure nginx to forward from the default port 18789 to the root location on the default enabled site config, making sure to enable Websocket support. Pairing is done by "openclaw devices list" and "openclaw device approve <request id>". Make sure the dashboard shows that OpenClaw's health is OK. exe.dev handles forwarding from port 8000 to port 80/443 and HTTPS for us, so the final "reachable" should be <vm-name>.exe.xyz, without port specification.
 ```
 
-If you don’t already have Node 22 on the VM, use your preferred Node manager (nvm/mise/asdf) or a distro package source that provides Node 22+.
-
-Common Ubuntu/Debian option (NodeSource):
+## Manual installation
 
-```bash
-curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
-sudo apt-get install -y nodejs
-```
-
-## 3) Install Moltbot
+## 1) Create the VM
 
-Recommended on servers: npm global install.
+From your device:
 
 ```bash
-npm i -g moltbot@latest
-moltbot --version
+ssh exe.dev new 
 ```
 
-If native deps fail to install (rare; usually `sharp`), add build tools:
+Then connect:
 
 ```bash
-sudo apt-get install -y build-essential python3
+ssh <vm-name>.exe.xyz
 ```
 
-## 4) First-time setup (wizard)
+Tip: keep this VM **stateful**. OpenClaw stores state under `~/.openclaw/` and `~/.openclaw/workspace/`.
 
-Run the onboarding wizard on the VM:
+## 2) Install prerequisites (on the VM)
 
 ```bash
-moltbot onboard --install-daemon
+sudo apt-get update
+sudo apt-get install -y git curl jq ca-certificates openssl
 ```
 
-It can set up:
-- `~/clawd` workspace bootstrap
-- `~/.clawdbot/moltbot.json` config
-- model auth profiles
-- model provider config/login
-- Linux systemd **user** service (service)
-
-If you’re doing OAuth on a headless VM: do OAuth on a normal machine first, then copy the auth profile to the VM (see [Help](/help)).
-
-## 5) Remote access options
+## 3) Install OpenClaw
 
-### Option A (recommended): SSH tunnel (loopback-only)
-
-Keep Gateway on loopback (default) and tunnel it from your laptop:
+Run the OpenClaw install script:
 
 ```bash
-ssh -N -L 18789:127.0.0.1:18789 moltbot.exe.xyz
+curl -fsSL https://openclaw.bot/install.sh | bash
 ```
 
-Open locally:
-- `http://127.0.0.1:18789/` (Control UI)
-
-Runbook: [Remote access](/gateway/remote)
-
-### Option B: exe.dev HTTPS proxy (no tunnel)
+## 4) Setup nginx to proxy OpenClaw to port 8000
 
-To let exe.dev proxy traffic to the VM, bind the Gateway to the LAN interface and set a token:
+Edit `/etc/nginx/sites-enabled/default` with
 
-```bash
-export CLAWDBOT_GATEWAY_TOKEN="$(openssl rand -hex 32)"
-moltbot gateway --bind lan --port 8080 --token "$CLAWDBOT_GATEWAY_TOKEN"
 ```
-
-For service runs, persist it in `~/.clawdbot/moltbot.json`:
-
-```json5
-{
-  gateway: {
-    mode: "local",
-    port: 8080,
-    bind: "lan",
-    auth: { mode: "token", token: "YOUR_TOKEN" }
-  }
+server {
+    listen 80 default_server;
+    listen [::]:80 default_server;
+    listen 8000;
+    listen [::]:8000;
+
+    server_name _;
+
+    location / {
+        proxy_pass http://127.0.0.1:18789;
+        proxy_http_version 1.1;
+
+        # WebSocket support
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+
+        # Standard proxy headers
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+
+        # Timeout settings for long-lived connections
+        proxy_read_timeout 86400s;
+        proxy_send_timeout 86400s;
+    }
 }
 ```
 
-Notes:
-- Non-loopback binds require `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`).
-- `gateway.remote.token` is only for remote CLI calls; it does not enable local auth.
+## 5) Access OpenClaw and grant privileges
 
-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 moltbot 8080
-```
+Access `https://<vm-name>.exe.xyz/?token=YOUR-TOKEN-FROM-TERMINAL`. Approve
+devices with `openclaw devices list` and `openclaw device approve`. When in doubt,
+use Shelley from your browser!
 
-Open:
-- `https://moltbot.exe.xyz/`
-
-In the Control UI, paste the token (UI → Settings → token). The UI sends it as `connect.params.auth.token`.
-
-Notes:
-- Prefer a **non-default** port (like `8080`) if your proxy expects an app port.
-- Treat the token like a password.
-
-Control UI details: [Control UI](/web/control-ui)
-
-## 6) Keep it running (service)
-
-On Linux, Moltbot uses a systemd **user** service. After `--install-daemon`, verify:
-
-```bash
-systemctl --user status moltbot-gateway[-<profile>].service
-```
-
-If the service dies after logout, enable lingering:
-
-```bash
-sudo loginctl enable-linger "$USER"
-```
+## Remote Access
 
-More: [Linux](/platforms/linux)
+Remote access is handled by [exe.dev](https://exe.dev)'s authentication. By
+default, HTTP traffic from port 8000 is forwarded to `https://<vm-name>.exe.xyz`
+with email auth. 
 
-## 7) Updates
+## Updating
 
 ```bash
-npm i -g moltbot@latest
-moltbot doctor
-moltbot gateway restart
-moltbot health
+npm i -g openclaw@latest
+openclaw doctor
+openclaw gateway restart
+openclaw health
 ```
 
 Guide: [Updating](/install/updating)

package/docs/platforms/fly.md

@@ -1,11 +1,11 @@
 ---
 title: Fly.io
-description: Deploy Moltbot on Fly.io
+description: Deploy OpenClaw on Fly.io
 ---
 
 # Fly.io Deployment
 
-**Goal:** Moltbot Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access.
+**Goal:** OpenClaw 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 Moltbot on Fly.io
 
 ```bash
 # Clone the repo
-git clone https://github.com/moltbot/moltbot.git
-cd moltbot
+git clone https://github.com/openclaw/openclaw.git
+cd openclaw
 
 # Create a new Fly app (pick your own name)
-fly apps create my-moltbot
+fly apps create my-openclaw
 
 # Create a persistent volume (1GB is usually enough)
-fly volumes create moltbot_data --size 1 --region iad
+fly volumes create openclaw_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-moltbot"  # Your app name
+app = "my-openclaw"  # Your app name
 primary_region = "iad"
 
 [build]
@@ -52,8 +52,8 @@ primary_region = "iad"
 
 [env]
   NODE_ENV = "production"
-  CLAWDBOT_PREFER_PNPM = "1"
-  CLAWDBOT_STATE_DIR = "/data"
+  OPENCLAW_PREFER_PNPM = "1"
+  OPENCLAW_STATE_DIR = "/data"
   NODE_OPTIONS = "--max-old-space-size=1536"
 
 [processes]
@@ -72,7 +72,7 @@ primary_region = "iad"
   memory = "2048mb"
 
 [mounts]
-  source = "moltbot_data"
+  source = "openclaw_data"
   destination = "/data"
 ```
 
@@ -82,15 +82,15 @@ primary_region = "iad"
 |---------|-----|
 | `--bind lan` | Binds to `0.0.0.0` so Fly's proxy can reach the gateway |
 | `--allow-unconfigured` | Starts without a config file (you'll create one after) |
-| `internal_port = 3000` | Must match `--port 3000` (or `CLAWDBOT_GATEWAY_PORT`) for Fly health checks |
+| `internal_port = 3000` | Must match `--port 3000` (or `OPENCLAW_GATEWAY_PORT`) for Fly health checks |
 | `memory = "2048mb"` | 512MB is too small; 2GB recommended |
-| `CLAWDBOT_STATE_DIR = "/data"` | Persists state on the volume |
+| `OPENCLAW_STATE_DIR = "/data"` | Persists state on the volume |
 
 ## 3) Set secrets
 
 ```bash
 # Required: Gateway token (for non-loopback binding)
-fly secrets set CLAWDBOT_GATEWAY_TOKEN=$(openssl rand -hex 32)
+fly secrets set OPENCLAW_GATEWAY_TOKEN=$(openssl rand -hex 32)
 
 # Model provider API keys
 fly secrets set ANTHROPIC_API_KEY=sk-ant-...
@@ -104,9 +104,9 @@ fly secrets set DISCORD_BOT_TOKEN=MTQ...
 ```
 
 **Notes:**
-- Non-loopback binds (`--bind lan`) require `CLAWDBOT_GATEWAY_TOKEN` for security.
+- Non-loopback binds (`--bind lan`) require `OPENCLAW_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 `moltbot.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 `openclaw.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/moltbot.json << 'EOF'
+cat > /data/openclaw.json << 'EOF'
 {
   "agents": {
     "defaults": {
@@ -185,13 +185,13 @@ cat > /data/moltbot.json << 'EOF'
     "bind": "auto"
   },
   "meta": {
-    "lastTouchedVersion": "2026.1.26"
+    "lastTouchedVersion": "2026.1.29"
   }
 }
 EOF
 ```
 
-**Note:** With `CLAWDBOT_STATE_DIR=/data`, the config path is `/data/moltbot.json`.
+**Note:** With `OPENCLAW_STATE_DIR=/data`, the config path is `/data/openclaw.json`.
 
 **Note:** The Discord token can come from either:
 - Environment variable: `DISCORD_BOT_TOKEN` (recommended for secrets)
@@ -214,9 +214,9 @@ Open in browser:
 fly open
 ```
 
-Or visit `https://my-moltbot.fly.dev/`
+Or visit `https://my-openclaw.fly.dev/`
 
-Paste your gateway token (the one from `CLAWDBOT_GATEWAY_TOKEN`) to authenticate.
+Paste your gateway token (the one from `OPENCLAW_GATEWAY_TOKEN`) to authenticate.
 
 ### Logs
 
@@ -243,7 +243,7 @@ The gateway is binding to `127.0.0.1` instead of `0.0.0.0`.
 
 Fly can't reach the gateway on the configured port.
 
-**Fix:** Ensure `internal_port` matches the gateway port (set `--port 3000` or `CLAWDBOT_GATEWAY_PORT=3000`).
+**Fix:** Ensure `internal_port` matches the gateway port (set `--port 3000` or `OPENCLAW_GATEWAY_PORT=3000`).
 
 ### OOM / Memory Issues
 
@@ -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/moltbot.json` should be read on restart.
+If using `--allow-unconfigured`, the gateway creates a minimal config. Your custom config at `/data/openclaw.json` should be read on restart.
 
 Verify the config exists:
 ```bash
-fly ssh console --command "cat /data/moltbot.json"
+fly ssh console --command "cat /data/openclaw.json"
 ```
 
 ### Writing Config via SSH
@@ -291,23 +291,23 @@ 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/moltbot.json"
+echo '{"your":"config"}' | fly ssh console -C "tee /data/openclaw.json"
 
 # Or use sftp
 fly sftp shell
-> put /local/path/config.json /data/moltbot.json
+> put /local/path/config.json /data/openclaw.json
 ```
 
 **Note:** `fly sftp` may fail if the file already exists. Delete first:
 ```bash
-fly ssh console --command "rm /data/moltbot.json"
+fly ssh console --command "rm /data/openclaw.json"
 ```
 
 ### State Not Persisting
 
 If you lose credentials or sessions after a restart, the state dir is writing to the container filesystem.
 
-**Fix:** Ensure `CLAWDBOT_STATE_DIR=/data` is set in `fly.toml` and redeploy.
+**Fix:** Ensure `OPENCLAW_STATE_DIR=/data` is set in `fly.toml` and redeploy.
 
 ## Updates
 
@@ -366,18 +366,18 @@ Or convert an existing deployment:
 
 ```bash
 # List current IPs
-fly ips list -a my-moltbot
+fly ips list -a my-openclaw
 
 # Release public IPs
-fly ips release <public-ipv4> -a my-moltbot
-fly ips release <public-ipv6> -a my-moltbot
+fly ips release <public-ipv4> -a my-openclaw
+fly ips release <public-ipv6> -a my-openclaw
 
 # 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-moltbot
+fly ips allocate-v6 --private -a my-openclaw
 ```
 
 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-moltbot
+fly proxy 3000:3000 -a my-openclaw
 
 # Then open http://localhost:3000 in browser
 ```
@@ -409,7 +409,7 @@ fly wireguard create
 
 **Option 3: SSH only**
 ```bash
-fly ssh console -a my-moltbot
+fly ssh console -a my-openclaw
 ```
 
 ### Webhooks with private deployment