Clawdbot Now OpenClaw - Local AI Agent Install & Setup

curl -fsSL https://openclaw.app/install.sh | bash

💡 Quickstart vs Custom

brew install openclaw
openclaw --tag beta

# PowerShell
iwr https://openclaw.app/install.ps1 -UseBasicParsing | iex
openclaw --tag beta

# On your VPS (Ubuntu/Debian)
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh

# Then run OpenClaw in Docker
sudo docker run -d \
  --name openclaw \
  -p 8080:8080 \
  --restart unless-stopped \
  openclaw/openclaw:latest

Safety Warning

OpenClaw (Clawdbot) official documentation explicitly states: "There is no 'perfectly secure' setup."

If you plan to run Clawdbot in a production environment or on a machine with sensitive data, you must read this entire section.

1. Core Definition: It's a SysAdmin, Not a ChatBot

OpenClaw (Clawdbot) was designed to "do things". In computing, "doing things" means: executing arbitrary commands. This isn't a bug—it's a feature. This also means it has extremely high privileges:

• ✅ Full shell access
• ✅ File system read/write permissions
• ✅ Cross-session persistent memory

2. Prompt Injection Attacks — The Unsolvable Problem

This is what keeps security experts up at night. Attackers can manipulate the Clawdbot AI to perform unintended actions through carefully crafted content (web pages, emails, documents).

🦞 Real Case: "The find ~ Incident"
Early in the project, a tester asked Clawdbot to run the find ~ command.Clawdbot happily complied and sent the entire home directory file structure to a public group chat.
Lesson: Even "harmless" requests can instantly leak your privacy.

3. Network Exposure Risks

By default, OpenClaw (Clawdbot) may listen on port 18789. If you misconfigure your Clawdbot (e.g., bind to 0.0.0.0) or expose it to the public internet via Tailscale Funnel:

• Token Brute Force: Attackers scan ports, brute-force tokens. Once successful, they can take over your machine.
• Unauthenticated Access: If no token is set, any local process can connect and modify configuration.

4. Browser Control Vulnerabilities

OpenClaw (Clawdbot) can control your browser sessions.

Risk Scenario: If your browser is logged into Gmail or online banking, and the Clawdbot Agentgets prompt-injected (or maliciously controlled), it can directly operate your accounts to transfer money or send phishing emails.

📊 Threat Matrix

📝 Clawdbot Final Recommendations

If you must use OpenClaw (Clawdbot) locally:

1. Physical Isolation: Don't use your main machine! Don't use your main machine! Use a VPS or a spare Mac Mini.
2. Network Isolation: Always run in a Docker container and configure a firewall.
3. Sensitive Data: Never send passwords, API keys, or bank information in conversations (these are all logged).

🔥 Deep Dive

Why manually type commands when you can let Claude Code be your DevOps engineer? This guide teaches you how to use Claude Code to automatically deploy OpenClaw (Clawdbot) to your home NAS via SSH.

# OpenClaw (Clawdbot) NAS Deployment Technical Guide (For Claude Code)

## 1. Environment Preparation
**Goal**: Install prerequisites on a Debian-based Linux system (e.g., Ubuntu 22.04).

### Tasks:
1. Update system packages.
2. Install Node.js 22.x (using nodesource).
3. Install Git.

## 2. Installation
**Goal**: Clone the repo and run setup.

### Tasks:
1. Clone https://github.com/openclaw/openclaw
2. Run ./docker-setup.sh
3. Handle the interactive wizard (API keys/Tokens required).

## 3. Docker Compose Management
**Goal**: Manage the service via docker compose.

### Commands Reference:
- Start: docker compose up -d
- Logs: docker compose logs -f openclaw-gateway
- Stop: docker compose down

## 4. Configuration Paths
- Compose File: /path/to/openclaw/docker-compose.yml
- Config File: ~/.openclaw/openclaw.json

/bug Reading the file "deployment_guide.md", please deploy OpenClaw (Clawdbot) to my NAS.
I authorize you to configure it fully. Here is the key data you need:

🔑 **Key Configuration Data:**
1. **API Key:** sk-ant-xxxx (Your Anthropic Key)
2. **Base URL:** https://your.proxy.site (If using a proxy)
3. **Discord Token:** xxxxx (Your Bot Token)
4. **NAS IP:** 192.168.0.xx
5. **SSH User:** your_username
6. **Sudo Password:** your_password (Required for Docker commands)
7. **SSH Port:** 22

**Execution Goal:** I want to see a running service. Handle the SSH connection and Docker setup autonomously.

Please find my API KEY and Base URL from previous context.
Update the `clawdbot.json` on the remote NAS with this specific structure:

{
  "gateway": {
    "tailscale": { "resetOnExit": false }
  },
  "models": {
    "mode": "merge",
    "providers": {
      "anthropic": {
        "baseUrl": "YOUR_BASE_URL",
        "apiKey": "YOUR_API_KEY",
        "api": "anthropic-messages",
        "models": []
      }
    }
  }
}

💡 The Philosophy: "Using AI to command AI to deploy AI." This is the core appeal ofClawdbot and Claude Code—letting AI act as your operations engineer. No manual command typing, no copy-pasting errors—just describe what you want, and watch it happen.

Container won't start

Check the container logs for errors:

Port already in use

Change the port mapping:

docker run -d --name clawdbot -p 8081:8080 clawdbot/clawdbot:latest

Out of memory

Ensure Docker Desktop has enough memory allocated. Go to Docker Desktop Settings → Resources → Advanced and increase the memory limit.

disconnected (1008): unauthorized: gateway token missing (open a tokenized dashboard URL or paste token in Control UI settings)

clawdbot devices list
clawdbot devices approve <Request ID>

Alternative: Dashboard Settings

In the Dashboard's Gateway Access section:

• Enter your Gateway Token (found via clawdbot doctor --generate-gateway-token)
• Or use a tokenized dashboard URL: clawdbot dashboard --no-open
• Click Connect to apply changes