Before We Begin: Understanding What You're Building
Most AI installation guides treat software as a black box: download, install, forget. clawbot is different because you're not installing an app—you're establishing infrastructure. Think of this as setting up your own private email server, except instead of managing messages, you're orchestrating an AI that can genuinely control your digital environment.
This guide explains what each step does and why it matters. Understanding the architecture makes troubleshooting intuitive and customization straightforward.
What You'll Have After 30 Minutes
- A Gateway service running persistently on your device, coordinating all AI activity
- Connection to your chosen AI model (Claude, GPT-4, or free local Ollama)
- At least one messaging channel (WhatsApp, Telegram, etc.) linked to your AI
- A functioning automation that demonstrates genuine system control
- Understanding of how to extend, customize, and troubleshoot your setup
Prerequisites: What You Actually Need
Before downloading anything, verify your system meets these requirements. Each one serves a specific purpose:
Hardware Requirements
- Operating System: macOS 11+, Linux (Ubuntu 20.04+, Debian 11+), or Windows 10+ with WSL2
- RAM: Minimum 2GB available (4GB recommended for smoother operation)
- Disk Space: 500MB for core installation plus space for AI model caching
- Network: Stable internet connection for AI API calls (unless using local Ollama)
Software Dependencies
clawbot requires Node.js 22 or higher. Why this specific version? Newer Node.js versions include critical performance improvements and security patches that clawbot's real-time communication relies on. The installer typically handles this, but manual installations require it pre-installed.
AI Model Access (Choose One)
Cost-Benefit Analysis: Which AI Model Should You Choose?
Option 1: Anthropic Claude (Recommended for most users)
- Cost: ~$20-40/month for typical personal use
- Advantage: Exceptional reasoning, strong security awareness, long context windows
- Get API key: console.anthropic.com
Option 2: OpenAI GPT-4
- Cost: ~$25-50/month depending on usage patterns
- Advantage: Broad knowledge base, excellent for creative tasks
- Get API key: platform.openai.com
Option 3: Local Ollama Models (Completely free)
- Cost: $0 (runs entirely on your hardware)
- Advantage: Zero ongoing costs, complete privacy, offline operation
- Disadvantage: Slower responses, requires more powerful hardware (8GB+ RAM recommended)
- Setup: ollama.ai
Step 1: Download the Right Package for Your Platform
clawbot distributes platform-specific installers that bundle everything needed. Why multiple formats? Different operating systems handle background services differently—the installer configures these correctly.
macOS Installation
Download the DMG installer for the simplest experience:
curl -fsSL https://github.com/steipete/clawbot/releases/download/v2026.1.23/clawbot-2026.1.23.dmg -o clawbot.dmg
Or download directly from GitHub Releases.
What the installer does:
- Installs the Gateway service to
/Applications/clawbot.app - Creates configuration directory at
~/.clawbot/ - Configures system permissions for automation capabilities
- Optionally sets up launch-at-startup (recommended)
Linux Installation
Install via npm (recommended) or Docker:
npm install -g clawbot@latest
Then initialize the configuration:
clawbot init
Setting up as a systemd service (optional but recommended):
clawbot install-service
This ensures clawbot starts automatically on boot and restarts if it crashes.
Windows Installation (WSL2)
Windows requires WSL2 (Windows Subsystem for Linux). If not installed:
wsl --install
Then follow the Linux instructions inside your WSL2 Ubuntu environment.
⚠️ Windows Native Support
Native Windows support (without WSL2) is experimental. WSL2 provides better compatibility with Node.js system integrations and shell command execution.
Docker Deployment
For cross-platform compatibility or server deployments:
docker pull ghcr.io/steipete/clawbot:latest
Run with persistent configuration:
docker run -d \
--name clawbot \
-v ~/.clawbot:/root/.clawbot \
-p 18789:18789 \
ghcr.io/steipete/clawbot:latest
Understanding the Docker flags:
-d: Runs container in background (daemon mode)-v ~/.clawbot:/root/.clawbot: Persists configuration between restarts-p 18789:18789: Exposes Gateway WebSocket port for local clients
Step 2: Install and Launch the Gateway
The Gateway is clawbot's core—a persistent service that manages all communication between messaging platforms, AI models, and your system. Think of it as the central nervous system: channels send messages to the Gateway, which routes them to the appropriate AI model, receives responses, and delivers them back.
Run the Installer
macOS: Open the downloaded DMG and drag clawbot to Applications. Launch it.
Linux/WSL: After npm installation, start the Gateway:
clawbot gateway start
Verify it's running:
clawbot gateway status
You should see: Gateway is running on ws://127.0.0.1:18789
🔍 What's Happening Behind the Scenes
The Gateway creates a WebSocket server on port 18789 (customizable). This local-only server accepts connections from:
- Channel plugins (WhatsApp, Telegram, etc.) that forward user messages
- Node clients (mobile apps, web interfaces) for direct interaction
- Skills and tools that extend functionality
All communication stays on your machine unless you explicitly configure remote access (covered in advanced guides).
Step 3: Connect Your AI Brain
With the Gateway running, it needs an AI model to generate responses. This step configures which model(s) you'll use and authenticates API access.
Configure AI Provider
Open the configuration file:
clawbot config edit
Or manually edit ~/.clawbot/clawbot.json. Add your API credentials:
{
"aiProviders": {
"anthropic": {
"apiKey": "sk-ant-your-api-key-here",
"model": "claude-3-5-sonnet-20250219",
"enabled": true
}
},
"defaultProvider": "anthropic"
}
For local Ollama instead:
{
"aiProviders": {
"ollama": {
"baseURL": "http://localhost:11434",
"model": "llama3.1:8b",
"enabled": true
}
},
"defaultProvider": "ollama"
}
Security Best Practice: API Key Management
Never commit clawbot.json to version control if it contains API keys. Consider using
environment variables for production deployments:
export ANTHROPIC_API_KEY="your-key-here"
clawbot automatically reads from environment variables if present.
Step 4: Link Your Communication Channels
Channels are how you interact with your AI—WhatsApp for mobile, Telegram for desktop, Discord for team collaboration. Each channel connects independently to the Gateway, and clawbot maintains a unified conversation history across all of them.
Connect Your First Channel: WhatsApp Example
Install the WhatsApp channel plugin:
clawbot channel add whatsapp
This launches an interactive setup:
- A QR code appears in your terminal
- Open WhatsApp on your phone → Settings → Linked Devices → Link a Device
- Scan the QR code
- clawbot confirms connection and saves session credentials
How it works: clawbot uses the WhatsApp Web protocol (via Baileys library) to establish a persistent connection. Your phone remains the "primary" device; clawbot acts as a linked secondary device—just like WhatsApp Web in your browser.
⚠️ WhatsApp Account Safety
WhatsApp's terms of service prohibit bot usage. While clawbot implements rate limiting and human-like behavior patterns, we recommend using a secondary phone number rather than your primary personal WhatsApp account. Consider:
- Getting a Google Voice or similar virtual number
- Using an old SIM card you don't actively use
- Trying Telegram instead (officially supports bots)
Alternative Channels
Each channel has unique setup requirements. Popular options:
Telegram (Recommended for beginners):
clawbot channel add telegram
Follow the prompt to authenticate with your phone number. Telegram officially supports bots, making this the safest option.
Discord (Great for teams):
clawbot channel add discord
Requires creating a Discord bot application at discord.com/developers. Copy the bot token when prompted.
Full channel documentation: docs.clawd.bot/channels
Step 5: Execute Your First Autonomous Task
With everything configured, let's verify clawbot can genuinely control your system—not just respond with text.
Test System Integration
Open your connected messaging channel (WhatsApp, Telegram, etc.) and send this message:
"Create a text file called test.txt in my Documents folder with today's date and a motivational quote."
What should happen:
- clawbot receives your message through the channel
- Gateway routes it to your configured AI model
- AI generates a response plan including shell commands
- clawbot executes:
echo "..." > ~/Documents/test.txt - You receive confirmation: "Created test.txt with..."
- Check your Documents folder—the file exists
🎉 You Just Demonstrated Genuine AI Automation
What distinguishes clawbot from ChatGPT or Siri: it didn't just tell you how to create the file—it actually created it. This same capability extends to:
- Managing your calendar and sending meeting invites
- Monitoring log files and alerting you to errors
- Pulling data from APIs and generating reports
- Controlling smart home devices via Home Assistant
- Running development workflows (tests, builds, deployments)
What to Build Next
Your AI infrastructure is operational. Here's how to expand its capabilities:
1. Install Skills from ClawdHub
Skills are pre-built automation modules. Browse the marketplace:
clawbot skills browse
Popular starter skills:
- google-calendar: Natural language calendar management
- home-assistant: Smart home control integration
- github-assistant: Repository management and PR reviews
- daily-briefing: Morning summary of calendar, weather, news
2. Create Custom Automation
Skills are just folders with a SKILL.md file. Create your own:
mkdir -p ~/.clawbot/skills/my-automation
echo "# My Custom Skill" > ~/.clawbot/skills/my-automation/SKILL.md
Full guide: docs.clawd.bot/skills/creating
3. Configure Proactive Behaviors
Unlike traditional AI, clawbot can initiate contact. Enable heartbeat monitoring:
clawbot config set heartbeat.enabled true
clawbot config set heartbeat.interval "every day at 8am"
Now clawbot will proactively send you a morning briefing without being asked.
4. Deploy to the Cloud (Optional)
Running clawbot on your laptop works, but cloud deployment ensures 24/7 availability. Guides available for:
- DigitalOcean Droplets ($6/month)
- AWS EC2 Free Tier (12 months free)
- Hetzner Cloud (€4/month)
- Home Raspberry Pi (one-time hardware cost)
Common Issues and Solutions
Gateway Won't Start
Symptom: Error: EADDRINUSE: address already in use
Cause: Another process is using port 18789.
Solution: Find and kill the conflicting process:
lsof -ti:18789 | xargs kill -9
Or configure clawbot to use a different port in clawbot.json.
AI Model Returns Errors
Symptom: "API authentication failed" or "Invalid model specified"
Cause: Incorrect API key or model name in configuration.
Solution: Verify your API key is valid:
curl https://api.anthropic.com/v1/messages \
-H "x-api-key: YOUR_KEY" \
-H "anthropic-version: 2023-06-01"
Check model names at provider documentation (Anthropic, OpenAI).
WhatsApp Disconnects Frequently
Symptom: QR code authentication required every few days.
Cause: Session credentials not persisting correctly.
Solution: Ensure ~/.clawbot/channels/whatsapp/ has write permissions:
chmod 700 ~/.clawbot/channels/whatsapp/
Also verify your phone remains connected to internet—WhatsApp requires the primary device online.
You're Now Running Your Own AI Infrastructure
What you've built isn't just a chatbot—it's a personal automation platform that combines the intelligence of frontier AI models with the capability of local system control. Unlike cloud services that constrain what AI can do, your clawbot installation has the same access to your digital environment that you do.
This power comes with responsibility: clawbot can execute any command you approve. The sandboxing and permission system protects against accidental damage, but ultimately you're granting an AI meaningful control. Start with simple automations, understand how decisions are made, and gradually expand capabilities as you build trust.
Ready to Go Deeper?
Explore advanced configuration, skill development, and architectural deep dives