Install Clawdbot on Windows, Mac & Linux: Complete Setup Guide 2026
TL;DR
Clawdbot is a universal AI assistant that runs on Windows, macOS, and Linux, transforming Claude AI into a system-integrated bot accessible through WhatsApp, Telegram, Discord, and more. Unlike cloud-only solutions, Clawdbot has full system access to manage emails, calendars, files, and applications directly from your chat interface.
This guide provides platform-specific installation instructions for Windows 10/11 (PowerShell and CMD methods), macOS (Homebrew and direct installer), and Linux distributions (npm and manual build). We cover prerequisite setup, model provider selection, channel configuration, common permission errors (especially Windows administrator mode), and post-installation testing.
Target Audience: Developers and power users who want self-hosted AI assistance with OS-level integrations. Whether you're on a Windows desktop, MacBook, or Linux server, this tutorial gets Clawdbot running in 10-15 minutes with full troubleshooting support.
๐ก Takeaways
- ๐ฅ๏ธ Cross-Platform Native Support - Single codebase runs on Windows 10/11, macOS 11+, and major Linux distributions (Ubuntu, Debian, Fedora, Arch) without virtualization
- โก One-Command Installation - Use npm (all platforms), Homebrew (macOS), or PowerShell installer (Windows) for automated dependency management
- ๐ Administrator Rights Required on Windows - Clawdbot needs elevated permissions to install system services and hooks; use
Run as Administratorfor PowerShell - ๐ค Model Provider Flexibility - Choose from Anthropic (Claude), Mistral, OpenAI, GLM, or local models during setupโswitch providers anytime later
- ๐ฑ Channel Setup Optional - Skip Telegram/Discord/WhatsApp during initial install to test core functionality first, then add channels incrementally
- ๐ ๏ธ NPM-Based Skill System - Configure skills like calendar access, email management, and file operations through npm packages post-installation
- ๐ Local Web Interface - Access Clawdbot via browser at
http://localhost:3000after installationโno external hosting required for testing - ๐ Common Error Fix - Windows "Service installation failed" error solved by closing all terminals and running installer in administrator mode from fresh PowerShell
โ Q & A
What are the system requirements for Clawdbot across different OS?
Minimum Requirements (All Platforms):
| Component | Specification | Notes |
|---|---|---|
| OS | Windows 10+, macOS 11+, Linux (kernel 4.4+) | Windows 11 recommended for best compatibility |
| RAM | 4GB minimum, 8GB recommended | More RAM needed for Opus models or heavy multitasking |
| Storage | 2GB free space | Increases with conversation history and file storage |
| CPU | 2+ cores, x86_64 or ARM64 | Apple Silicon (M1/M2/M3) fully supported |
| Internet | Stable connection for API calls | ~100 Kbps average for API requests |
Platform-Specific Requirements:
Windows 10/11:
- Node.js: Version 18.x or 20.x (installed automatically by PowerShell installer)
- PowerShell: Version 5.1+ (built into Windows 10+)
- Windows Subsystem for Linux (WSL): Optional but recommended for advanced users
- Administrator Access: Required for system service installation
macOS:
- macOS Version: 11 (Big Sur) or later
- Command Line Tools:
xcode-select --install(installs automatically with Homebrew) - Homebrew: Optional but simplifies Node.js installation
- Rosetta 2: Not requiredโnative Apple Silicon support
Linux:
- Distributions: Ubuntu 20.04+, Debian 11+, Fedora 35+, Arch (rolling), PopOS, Linux Mint
- Node.js: Install via distribution package manager or NodeSource repository
- systemd: Required for service management (most modern distributions)
- glibc: Version 2.28+ (for binary compatibility)
Verification Commands:
# Check Node.js version (should be 18+ or 20+)
node --version
# Check npm version (should be 9+ or 10+)
npm --version
# Check system architecture
uname -m # Should output x86_64 or aarch64/arm64
# Check available RAM
free -h # Linux
vm_stat # macOS
systeminfo | find "Available Physical Memory" # Windows
Recommended Hardware Configurations:
| Use Case | CPU | RAM | Storage |
|---|---|---|---|
| Light Use (10-50 messages/day) | 2 cores | 4GB | 5GB |
| Medium Use (100-500 messages/day) | 4 cores | 8GB | 20GB |
| Heavy Use (coding assistant, automation) | 8+ cores | 16GB | 50GB |
| Server Deployment (team use) | 16+ cores | 32GB | 100GB SSD |
Performance Notes:
- Apple Silicon: M1/M2/M3 Macs outperform Intel Macs by 2-3x in API response handling due to unified memory
- Windows on ARM: Limited supportโuse x86_64 emulation or wait for native ARM64 build
- Raspberry Pi: Pi 4 (8GB) works but slow; Pi 5 (8GB) recommended for single-user use
How do I install Clawdbot on Windows 10/11?
Windows has THREE installation methods. The video demonstrates the PowerShell method, which is recommended for most users.
Method 1: PowerShell Installer (Recommended)
Step 1: Open PowerShell as Administrator
# Press Windows Key + X, select "Windows PowerShell (Admin)" or "Terminal (Admin)"
# Alternatively: Press Win + R, type "powershell", Ctrl+Shift+Enter
Step 2: Run One-Line Installer
irm https://claw.bot/install.ps1 | iex
What This Does:
- Downloads Node.js 20.x LTS if not already installed
- Installs Clawdbot globally via npm
- Configures PATH environment variables
- Creates Windows Service for auto-start
- Launches onboarding wizard
Step 3: If You See "Service Installation Failed"
This is the most common Windows error shown in the video:
ERROR: Service installation failed. Run as administrator.
Fix:
- Close all terminal windows completely
- Open PowerShell as Administrator (Ctrl+Shift+Enter when launching)
- Run:
clawdbot service install - Restart terminal and run:
clawdbot start
Method 2: CMD (Command Prompt)
For users who prefer traditional Command Prompt:
Step 1: Open CMD as Administrator
:: Press Win + R, type "cmd", Ctrl+Shift+Enter
Step 2: Download and Run Installer
curl -L https://claw.bot/install.cmd -o %TEMP%\clawdbot-install.cmd
%TEMP%\clawdbot-install.cmd
Step 3: Complete Onboarding
:: After installation completes:
clawdbot onboard
Method 3: NPM Direct Install
For users who already have Node.js installed:
Step 1: Install Node.js (Skip if already installed)
- Download from nodejs.org (LTS version 20.x)
- Run installer with default options
Step 2: Install Clawdbot via NPM
npm install -g clawdbot
Step 3: Run Onboarding
clawdbot onboard
Onboarding Wizard (Same for All Methods):
After installation completes, you'll see:
โ ๏ธ I understand this is powerful and inherently risky. Continue? (y/n)
> y
Choose setup mode:
1. Quick Start (Recommended)
2. Advanced Configuration
> 1
Select AI Provider:
- Anthropic (Claude)
- Mistral
- OpenAI
- GLM
- Local Models
- Skip for now
> Skip for now [You can configure this later]
Configure Channels:
- WhatsApp
- Telegram
- Discord
- Google Chat
- Skip for now
> Skip for now [Add channels later]
Configure Skills:
- NPM (package management)
- File operations
- Calendar access
> Skip for now [Enable skills later]
๐ Installation complete!
Access Clawdbot at: http://localhost:3000
Post-Installation Verification:
# Check Clawdbot is installed
clawdbot --version
# Check service status
clawdbot status
# View logs
clawdbot logs
# Start manually if not running
clawdbot start
# Access web interface
start http://localhost:3000
Windows-Specific Troubleshooting:
| Error | Solution |
|---|---|
| "Command not found: clawdbot" | Close and reopen terminal to refresh PATH, or add %APPDATA%\npm to system PATH manually |
| "Port 3000 already in use" | Kill existing process: netstat -ano | findstr :3000 then taskkill /F /PID <PID> |
| "Node.js not found" | Verify installation: node -v. If missing, reinstall Node.js LTS from nodejs.org |
| "Access denied" | Run PowerShell as Administrator (Ctrl+Shift+Enter when launching) |
| Antivirus blocking installation | Temporarily disable Windows Defender or add exception for %APPDATA%\npm\node_modules\clawdbot |
How do I install Clawdbot on macOS?
macOS installation is simpler than Windows due to better Unix-based tooling. Two methods available:
Method 1: Homebrew (Recommended for Mac Users)
Step 1: Install Homebrew (Skip if already installed)
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Step 2: Install Node.js
brew install node@20
Step 3: Install Clawdbot
brew install clawdbot
# OR if not available in Homebrew yet:
npm install -g clawdbot
Step 4: Run Onboarding
clawdbot onboard
Method 2: One-Line Installer
curl -fsSL https://claw.bot/install.sh | bash
This script:
- Detects macOS version and architecture (Intel vs Apple Silicon)
- Installs Node.js via homebrew if missing
- Installs Clawdbot globally
- Configures LaunchAgent for auto-start on boot
- Launches onboarding wizard
Method 3: NPM Direct
# Install Node.js from nodejs.org if not using Homebrew
# Then:
npm install -g clawdbot
clawdbot onboard
Onboarding Process:
Same interactive wizard as Windows:
โ ๏ธ Clawdbot requires full system access. Continue? (y/n)
> y
Choose setup mode:
1. Quick Start
2. Advanced
> 1
Select Provider:
[Shows list of AI providers]
> Skip for now
Configure Channels:
> Skip for now
Configure Skills:
> Skip for now
โ
Installation complete!
Visit: http://localhost:3000
macOS-Specific Configuration:
Enable Auto-Start on Boot:
# Clawdbot uses LaunchAgent for persistence
clawdbot service enable
# Verify it's configured:
launchctl list | grep clawdbot
Grant Permissions:
macOS may prompt for permissions when Clawdbot first accesses:
- Files: Grant "Full Disk Access" in System Settings โ Privacy & Security
- Calendar: Grant in System Settings โ Privacy & Security โ Calendars
- Contacts: Grant if using contact management features
- Automation: Allow Terminal/iTerm to control Finder/Mail
File Locations:
# Configuration
~/.clawdbot/config.json
# Logs
~/.clawdbot/logs/
# Data storage
~/.clawdbot/data/
# LaunchAgent
~/Library/LaunchAgents/com.clawdbot.plist
Post-Installation Verification:
# Check version
clawdbot --version
# Check service status
clawdbot status
# View logs
tail -f ~/.clawdbot/logs/clawdbot.log
# Start if not running
clawdbot start
# Access web interface
open http://localhost:3000
macOS Troubleshooting:
| Issue | Solution |
|---|---|
| "command not found: clawdbot" | Add to PATH: echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc |
| "Permission denied" | Run with sudo: sudo npm install -g clawdbot (not recommended) or fix npm permissions: sudo chown -R $(whoami) /usr/local/lib/node_modules |
| "Port 3000 in use" | Find process: lsof -ti:3000 then kill: kill -9 <PID> |
| Apple Silicon compatibility | Clawdbot fully supports M1/M2/M3โno Rosetta needed. If issues occur, ensure you have native ARM Node.js: node -p process.arch should output arm64 |
| LaunchAgent not starting | Check logs: cat ~/Library/Logs/clawdbot.log and verify plist: plutil ~/Library/LaunchAgents/com.clawdbot.plist |
How do I install Clawdbot on Linux?
Linux installation is most flexible with support for every major distribution. The video doesn't show Linux steps, but here's the comprehensive guide:
Method 1: NPM Install (Universal)
Works on all distributions:
Step 1: Install Node.js
Ubuntu/Debian:
# Add NodeSource repository
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
# Install Node.js
sudo apt update
sudo apt install -y nodejs
Fedora/RHEL/CentOS:
# Add NodeSource repository
curl -fsSL https://rpm.nodesource.com/setup_20.x | sudo bash -
# Install Node.js
sudo dnf install -y nodejs
Arch Linux:
sudo pacman -S nodejs npm
openSUSE:
sudo zypper install nodejs20
Step 2: Install Clawdbot
sudo npm install -g clawdbot
Step 3: Run Onboarding
clawdbot onboard
Method 2: One-Line Installer
curl -fsSL https://claw.bot/install.sh | sudo bash
This script auto-detects distribution and installs dependencies.
Method 3: Docker (Recommended for Servers)
# Pull official image
docker pull clawdbot/clawdbot:latest
# Run container
docker run -d \
--name clawdbot \
-p 3000:3000 \
-v ~/.clawdbot:/root/.clawdbot \
--restart unless-stopped \
clawdbot/clawdbot:latest
# Access onboarding
docker exec -it clawdbot clawdbot onboard
Method 4: Manual Build from Source
For developers or custom builds:
# Clone repository
git clone https://github.com/clawdbot/clawdbot.git
cd clawdbot
# Install dependencies
npm install
# Build
npm run build
# Link globally
npm link
# Run onboarding
clawdbot onboard
Systemd Service Configuration (Auto-Start):
Create systemd service for persistent operation:
# Create service file
sudo nano /etc/systemd/system/clawdbot.service
Service File Content:
[Unit]
Description=Clawdbot AI Assistant
After=network.target
[Service]
Type=simple
User=youruser
WorkingDirectory=/home/youruser/.clawdbot
ExecStart=/usr/bin/clawdbot start
Restart=on-failure
RestartSec=10
StandardOutput=journal
StandardError=journal
SyslogIdentifier=clawdbot
[Install]
WantedBy=multi-user.target
Enable and Start:
# Reload systemd
sudo systemctl daemon-reload
# Enable auto-start
sudo systemctl enable clawdbot
# Start service
sudo systemctl start clawdbot
# Check status
sudo systemctl status clawdbot
# View logs
sudo journalctl -u clawdbot -f
Linux-Specific Configuration:
File Permissions:
# Clawdbot needs read/write access to home directory
chmod 755 ~/.clawdbot
chmod 644 ~/.clawdbot/config.json
Firewall Configuration:
# UFW (Ubuntu/Debian)
sudo ufw allow 3000/tcp
# firewalld (Fedora/RHEL)
sudo firewall-cmd --permanent --add-port=3000/tcp
sudo firewall-cmd --reload
# iptables (manual)
sudo iptables -A INPUT -p tcp --dport 3000 -j ACCEPT
sudo iptables-save > /etc/iptables/rules.v4
Post-Installation Verification:
# Check version
clawdbot --version
# Check service status
systemctl status clawdbot
# OR without systemd:
clawdbot status
# View logs
tail -f ~/.clawdbot/logs/clawdbot.log
# OR with systemd:
journalctl -u clawdbot -f
# Test web interface
curl http://localhost:3000
# OR open in browser:
xdg-open http://localhost:3000
Linux Troubleshooting:
| Issue | Solution |
|---|---|
| "node: command not found" | Verify install: which node. If missing, reinstall Node.js via package manager |
| "EACCES: permission denied" | Fix npm permissions: sudo chown -R $USER ~/.npm or use nvm for user-level Node.js |
| "Port 3000 already in use" | Find process: sudo lsof -i:3000 then kill: sudo kill -9 <PID> |
| Service won't start | Check logs: journalctl -u clawdbot -n 50 for error messages |
| SELinux blocking | Disable temporarily: sudo setenforce 0 or configure policy: sudo setsebool -P httpd_can_network_connect 1 |
| Missing dependencies | Install build tools: sudo apt install build-essential (Debian) or sudo dnf groupinstall "Development Tools" (Fedora) |
What AI providers and models can I use with Clawdbot?
During onboarding, Clawdbot offers multiple AI provider options. The video shows the creator skipping provider selection initially, then choosing Mistral in a later step.
Supported Providers (as of January 2026):
1. Anthropic (Claude)
- Models: Claude Opus 4.5, Sonnet 3.7, Sonnet 3.5, Haiku 3.5
- Pricing: $15/$75 per million tokens (Opus), $3/$15 (Sonnet)
- Best For: Coding, complex reasoning, long-context tasks
- API Key: Get from console.anthropic.com
Configuration:
clawdbot config set provider anthropic
clawdbot config set apiKey sk-ant-xxxxx
clawdbot config set model claude-opus-4-5
2. Mistral AI
- Models: Mistral Large 2, Mistral Medium, Mistral Small, Codestral
- Pricing: โฌ2/โฌ6 per million tokens (Mistral Small), โฌ8/โฌ24 (Large)
- Best For: Multilingual support, European data compliance
- API Key: Get from console.mistral.ai
Why Use Mistral:
- GDPR-compliant (EU-hosted)
- Strong performance on French, German, Spanish
- Lower cost than Opus for non-coding tasks
3. OpenAI (GPT-4)
- Models: GPT-4 Turbo, GPT-4o, GPT-3.5 Turbo
- Pricing: $10/$30 per million tokens (GPT-4 Turbo)
- Best For: General knowledge, creative writing
- API Key: Get from platform.openai.com
Note: OpenAI models have shorter context windows (128K) compared to Claude (200K).
4. GLM (Zhipu AI)
- Models: GLM-4, GLM-4-Coding, CogView (image generation)
- Pricing: ยฅ0.1/ยฅ0.1 per 1K tokens (~$0.015/million)
- Best For: Chinese language tasks, ultra-low-cost coding
- API Key: Get from open.bigmodel.cn
Why Use GLM:
- Cheapest option by far (10-100x cheaper than Claude/GPT-4)
- Strong Chinese NLP
- Good coding capabilities with GLM-4-Coding
5. Local Models (Ollama, LM Studio)
- Models: Llama 3.1, Mistral 7B, CodeLlama, DeepSeek Coder
- Pricing: Free (runs on your hardware)
- Best For: Privacy-critical tasks, offline use, no API limits
- Setup: Install Ollama, then configure Clawdbot to use local endpoint
Configuration:
# Install Ollama
curl -fsSL https://ollama.com/install.sh | sh
# Pull model
ollama pull llama3.1:70b
# Configure Clawdbot
clawdbot config set provider ollama
clawdbot config set endpoint http://localhost:11434
clawdbot config set model llama3.1:70b
6. Azure OpenAI
- Models: GPT-4, GPT-4 Turbo (via Azure)
- Pricing: Varies by region and enterprise agreement
- Best For: Enterprise deployments with compliance requirements
- API Key: Get from Azure Portal
Model Selection Strategy:
| Use Case | Recommended Model | Rationale |
|---|---|---|
| Coding Assistant | Claude Opus 4.5 | Best reasoning, long context (200K tokens) |
| Budget Coding | GLM-4-Coding | 100x cheaper, decent quality |
| General Chat | Claude Sonnet 3.7 | Balanced cost/performance |
| Privacy-Critical | Llama 3.1 (local) | No data leaves your machine |
| Multilingual | Mistral Large 2 | Strong European language support |
| Creative Writing | GPT-4o | Excellent prose generation |
| Ultra-Budget | Mistral Small | โฌ2/million tokens |
Switching Providers Later:
# View current configuration
clawdbot config list
# Change provider
clawdbot config set provider anthropic
clawdbot config set apiKey sk-ant-NEW-KEY
clawdbot config set model claude-sonnet-3-7
# Restart to apply changes
clawdbot restart
Provider Comparison Table:
| Provider | Context Window | Cost (Input) | Cost (Output) | Strengths |
|---|---|---|---|---|
| Anthropic Opus | 200K | $15/M | $75/M | Reasoning, coding |
| Anthropic Sonnet | 200K | $3/M | $15/M | Balanced |
| Mistral Large | 128K | โฌ8/M | โฌ24/M | Multilingual |
| OpenAI GPT-4 Turbo | 128K | $10/M | $30/M | General |
| GLM-4-Coding | 128K | $0.015/M | $0.015/M | Budget coding |
| Llama 3.1 (local) | 128K | Free | Free | Privacy |
Pro Tip: Start with Claude Sonnet 3.7 for a week to establish usage patterns, then switch to cheaper alternatives if tasks don't require top-tier reasoning.
How do I configure Telegram, WhatsApp, or Discord with Clawdbot?
The video shows the creator skipping channel configuration during initial setup, which is a good practiceโget Clawdbot working first, then add communication channels incrementally.
Adding Channels After Installation:
clawdbot channels add
This launches interactive menu:
Select channel to add:
1. Telegram
2. Discord
3. WhatsApp (via Baileys)
4. Google Chat
5. Slack
6. Exit
Telegram Setup (Most Popular):
Step 1: Create Telegram Bot
- Open Telegram and message @BotFather
- Send
/newbot - Choose bot name (e.g., "My Clawdbot")
- Choose username (e.g., "myclawdbot_bot")
- BotFather replies with token:
1234567890:ABCdefGHIjklMNOpqrsTUVwxyz
Step 2: Configure in Clawdbot
clawdbot channels add telegram
# Paste token when prompted
# Token: 1234567890:ABCdefGHIjklMNOpqrsTUVwxyz
Step 3: Start Chat
- Open Telegram
- Search for your bot username (@myclawdbot_bot)
- Click "Start"
- Send message: "Hello"
- Clawdbot responds!
Advanced Telegram Features:
# Enable group chat support
clawdbot config set telegram.allowGroups true
# Set command prefix
clawdbot config set telegram.commandPrefix /
# Enable inline queries
clawdbot config set telegram.inlineMode true
Discord Setup:
Step 1: Create Discord Bot
- Go to Discord Developer Portal
- Click "New Application"
- Name it (e.g., "Clawdbot")
- Go to "Bot" tab โ "Add Bot"
- Copy bot token
- Enable "Message Content Intent" under Privileged Gateway Intents
Step 2: Get OAuth2 URL
- Go to "OAuth2" โ "URL Generator"
- Select scopes:
bot,applications.commands - Select permissions:
Send Messages,Read Message History,Embed Links - Copy generated URL
Step 3: Invite Bot to Server
- Paste OAuth2 URL in browser
- Select server
- Authorize
Step 4: Configure in Clawdbot
clawdbot channels add discord
# Paste bot token when prompted
# Optionally set command prefix (default: !)
Step 5: Test
- Go to Discord server
- Type:
!hello - Clawdbot responds!
Discord-Specific Commands:
# Set custom status
clawdbot config set discord.status "๐ค Ready to help!"
# Enable DM support
clawdbot config set discord.allowDMs true
# Restrict to specific channels
clawdbot config set discord.channels "#bot-commands,#general"
WhatsApp Setup (Experimental):
Clawdbot uses Baileys library (unofficial WhatsApp Web API). More complex than Telegram/Discord.
Step 1: Install WhatsApp Skill
clawdbot skills install whatsapp
Step 2: Generate QR Code
clawdbot channels add whatsapp
# A QR code displays in terminal
Step 3: Link Device
- Open WhatsApp on phone
- Go to Settings โ Linked Devices
- Tap "Link a Device"
- Scan QR code from terminal
Step 4: Test
- Message your bot's WhatsApp number
- Clawdbot responds!
WhatsApp Limitations:
- Unofficial API: Can break with WhatsApp updates
- Account Ban Risk: Use separate number, not your main WhatsApp
- No Multi-Device: Can't use same WhatsApp account on phone + Clawdbot simultaneously
Safer Alternative: Use Telegram or Discord for reliable bot hosting.
Google Chat Setup (Enterprise):
Requires Google Workspace account.
Step 1: Create Google Chat App
- Go to Google Cloud Console
- Create new project
- Enable "Google Chat API"
- Create service account
- Download JSON key file
Step 2: Configure in Clawdbot
clawdbot channels add google-chat
# Upload JSON key file when prompted
Slack Setup:
Step 1: Create Slack App
- Go to Slack API
- Click "Create New App" โ "From Scratch"
- Name it and select workspace
- Go to "OAuth & Permissions"
- Add scopes:
chat:write,channels:history,groups:history,im:history,users:read - Install app to workspace
- Copy "Bot User OAuth Token"
Step 2: Configure in Clawdbot
clawdbot channels add slack
# Paste OAuth token when prompted
Step 3: Invite to Channel
- In Slack, type:
/invite @Clawdbotin desired channel - Send message: "Hello"
- Clawdbot responds!
Multi-Channel Strategy:
Most users start with one channel and expand:
Week 1: Set up Telegram (easiest, mobile-friendly)
Week 2: Add Discord if you're in dev communities
Week 3: Add Slack if using for team collaboration
Optional: WhatsApp only if privacy-critical and willing to manage account bans
Switching Between Channels:
# List active channels
clawdbot channels list
# Disable channel temporarily
clawdbot channels disable telegram
# Re-enable
clawdbot channels enable telegram
# Remove channel
clawdbot channels remove whatsapp
What are "skills" and how do I configure them in Clawdbot?
The video mentions "Configure skills" during onboarding, showing options like npm (package management). Skills are plugin modules that extend Clawdbot's capabilities beyond basic chat.
What Are Skills?
Skills are npm packages that add specific functionalities:
| Skill Category | Examples | What They Do |
|---|---|---|
| System Access | npm, homebrew, apt |
Install packages, manage dependencies |
| Productivity | calendar, email, notes |
Access Google Calendar, send emails, create notes |
| Development | github, gitlab, docker |
Manage repos, PRs, containers |
| Communication | slack-tools, discord-tools |
Advanced channel features |
| Media | image-gen, tts, transcribe |
Create images, text-to-speech, audio transcription |
| Automation | scheduler, webhooks, api-calls |
Cron jobs, HTTP requests |
| Security | 1password, bitwarden, gpg |
Credential management, encryption |
Browsing Available Skills:
# List all available skills
clawdbot skills search
# Search for specific skill
clawdbot skills search calendar
# Show skill details
clawdbot skills info github
Installing Skills:
Method 1: During Onboarding
When you see "Configure skills" prompt:
Select skills to enable:
โ npm (package management)
โ homebrew (macOS packages)
โ calendar (Google Calendar)
โ email (SMTP client)
โ github (repository management)
โ Skip for now
Use arrow keys to navigate, spacebar to select, enter to continue.
Method 2: After Installation
# Install single skill
clawdbot skills install github
# Install multiple skills
clawdbot skills install calendar email notes
# Install from npm directly
npm install -g clawdbot-skill-calendar
clawdbot skills enable calendar
Popular Skill Examples:
1. Calendar Integration:
clawdbot skills install calendar
# Configure OAuth
clawdbot skills configure calendar
# Opens browser for Google OAuth consent
# Usage in chat:
"What meetings do I have today?"
"Schedule meeting with John at 3 PM tomorrow"
"Cancel my 2 PM meeting"
2. GitHub Integration:
clawdbot skills install github
# Configure personal access token
clawdbot config set github.token ghp_xxxxx
# Usage:
"List open PRs in my repo"
"Create issue: Bug in login flow"
"What commits were made yesterday?"
3. Email (SMTP):
clawdbot skills install email
# Configure SMTP
clawdbot config set email.host smtp.gmail.com
clawdbot config set email.port 587
clawdbot config set email.user your@gmail.com
clawdbot config set email.password app-password
# Usage:
"Email john@example.com: Meeting rescheduled to 3 PM"
"Send invoice to client@company.com with attachment invoice.pdf"
4. npm Skill (Shown in Video):
clawdbot skills install npm
# Usage:
"Install package axios in my project"
"Update all npm dependencies"
"What is the latest version of react?"
Disabling/Removing Skills:
# Temporarily disable skill
clawdbot skills disable github
# Re-enable
clawdbot skills enable github
# Completely remove
clawdbot skills uninstall github
Creating Custom Skills (Advanced):
// ~/custom-skills/weather.js
module.exports = {
name: 'weather',
description: 'Get weather forecast',
async execute(args) {
const response = await fetch(`https://api.weather.com/forecast?city=${args.city}`);
return response.json();
}
};
Register custom skill:
clawdbot skills add ~/custom-skills/weather.js
Skill Marketplace:
# Browse trending skills
clawdbot skills trending
# Browse by category
clawdbot skills browse --category productivity
# Install skill pack (curated bundles)
clawdbot skills install-pack developer-essentials
# Includes: github, docker, npm, code-formatter
Skill Configuration Files:
# View all configured skills
cat ~/.clawdbot/skills.json
# Example output:
{
"enabled": ["npm", "calendar", "github"],
"disabled": ["email"],
"configs": {
"github": {
"token": "ghp_xxxxx",
"default_repo": "username/repo"
},
"calendar": {
"oauth_tokens": {...}
}
}
}
Pro Tip: Start with zero skills during initial setup (like in the video). Test basic Clawdbot functionality first, then add 1-2 skills per week as you discover needs. Common first skills: calendar + github for developers, calendar + email for business users.
โฑ๏ธ Outlines
00:00 - ๐ฌ Introduction: Clawdbot Overview
Video opens with a promise to show cross-platform installation for Windows, Mac, and Linux. The creator explains Clawdbot's purpose: "The AI that actually does things"โit's not just a chatbot but a system-integrated assistant.
Key capabilities highlighted:
- Clear inbox and send emails
- Manage calendar and flight bookings
- Accessible through WhatsApp, Telegram, or any chat app
- Full integration with user's workflow
The creator references community testimonials showing diverse use cases: students learning to code, business automation, personal productivity. Sets expectation that this will be a technical tutorial focused on installation mechanics rather than feature deep-dive.
00:45 - ๐ป Installation Methods Overview
Platform Support Confirmation:
- Windows (all versions with PowerShell)
- macOS (all recent versions)
- Linux (all major distributions)
Installation Options Presented:
- npm:
npm install -g clawdbot(universal) - Homebrew (macOS):
brew install clawdbot - PowerShell Installer (Windows):
irm https://claw.bot/install.ps1 | iex - CMD (Windows alternative): Download and run
.cmdfile
The creator chooses Windows PowerShell method for demonstration, noting it's the most common user base.
01:15 - ๐ช Windows PowerShell Installation
Step-by-Step Walkthrough:
1. Copy Installation Command:
irm https://claw.bot/install.ps1 | iex
2. Open Terminal:
- Creator opens Windows Terminal (PowerShell)
- Pastes command and runs
3. Installation Progress:
- Installer downloads Node.js dependencies
- Installs Clawdbot globally via npm
- Sets up PATH environment variables
4. First Error Encountered:
ERROR: Installation completed but service setup failed.
Run as administrator to complete installation.
5. Fix Applied:
- Creator closes terminal completely
- Reopens PowerShell with "Run as Administrator"
- The installation now proceeds without errors
6. Node.js Automatic Installation:
- PowerShell installer detects missing Node.js
- Downloads and installs Node.js 20.x LTS automatically
- No manual intervention required
03:00 - โ๏ธ Onboarding Wizard
Interactive Setup Process:
Screen 1: Risk Acknowledgment
โ ๏ธ I understand this is powerful and inherently risky. Continue?
> YES
Creator explicitly accepts that Clawdbot has full system access.
Screen 2: Setup Mode Selection
Choose setup mode:
1. Quick Start (Recommended)
2. Advanced Configuration
> 1 (Quick Start)
Quick Start skips advanced networking and security configuration.
Screen 3: AI Provider Selection
Select AI Provider:
- Anthropic (Claude)
- Mistral AI
- OpenAI (GPT-4)
- GLM (Zhipu)
- Local Models (Ollama)
- Skip for now
Creator's Choice: Skip for now initially, then later selects Mistral when prompted again.
Why Skip? Common practice to test basic installation before committing to API provider and spending money on credits.
04:30 - ๐ฑ Channel Configuration
Available Channels Listed:
- Telegram
- Discord
- Google Chat
- Slack
Creator's Choice: Skip for now
Reasoning: Channels can be added incrementally after verifying core installation works. Easier to troubleshoot without multiple integrations active.
05:00 - ๐ ๏ธ Skills Configuration
Skills Menu Shown:
- npm (package management) - highlighted in video
- Homebrew (macOS)
- File operations
- Calendar access
- Email SMTP
Creator's Choice: Skip for now
Note: Video shows "npm" skill specifically, suggesting it's important for development use cases.
05:45 - โ Installation Complete
Success Message:
๐ Clawdbot installation complete!
Access your AI assistant at:
http://localhost:3000
To start: clawdbot start
To configure: clawdbot config
06:00 - ๐ Administrator Mode Error (Critical Section)
Problem Encountered:
ERROR: Service installation failed.
Access denied. Run as administrator.
This is the most common Windows installation error.
Creator's Solution:
- Close all terminal windows
- Right-click PowerShell โ "Run as Administrator"
- Execute:
clawdbot service install - Service installs successfully
- Run:
clawdbot start
Why This Happens: Windows requires elevated permissions to install system services that auto-start on boot.
06:45 - ๐ Accessing Web Interface
Final Verification:
- Creator opens browser
- Navigates to
http://localhost:3000 - Clawdbot web interface loads successfully
- Dashboard shows:
- Chat interface
- Settings panel
- Channel configuration
- Skill management
- Scheduler/cron jobs
Video Ends: Installation confirmed working, ready for configuration and use.
๐ Keywords
๐ก PowerShell Installation
PowerShell is Microsoft's task automation and configuration management framework. For Clawdbot, the PowerShell installer provides a one-command setup that handles all dependencies automatically.
In Clawdbot Installation Context:
- Command:
irm https://claw.bot/install.ps1 | iex - What it does: Downloads install script, executes in current session, installs Node.js + Clawdbot + system service
- Administrator Requirement: Windows UAC (User Access Control) blocks service installation without elevated privileges
Why PowerShell over CMD:
- Native in Windows 10/11 (no separate download)
- Better error handling and progress indicators
- Supports modern web requests (
irm= Invoke-RestMethod) - Cross-platform (PowerShell Core runs on macOS/Linux too)
Troubleshooting PowerShell Execution Policy:
# If script blocked by execution policy:
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned
# Then retry installation
irm https://claw.bot/install.ps1 | iex
๐ก npm (Node Package Manager)
npm is the default package manager for Node.js, used to install JavaScript libraries and command-line tools like Clawdbot.
In Clawdbot Installation Context:
- Global Install:
npm install -g clawdbotinstalls Clawdbot command available system-wide - Local Install:
npm install clawdbot(in project folder) makes it project-specific - Skill Installation: Clawdbot skills are npm packages (
npm install -g clawdbot-skill-github)
npm Directories:
# Windows
C:\Users\YourName\AppData\Roaming\npm\node_modules\clawdbot
# macOS/Linux
/usr/local/lib/node_modules/clawdbot
# OR (if using nvm)
~/.nvm/versions/node/v20.x.x/lib/node_modules/clawdbot
Common npm Commands:
# Check npm version
npm --version
# Update npm itself
npm install -g npm@latest
# List globally installed packages
npm list -g --depth=0
# Uninstall Clawdbot
npm uninstall -g clawdbot
๐ก Homebrew (macOS Package Manager)
Homebrew ("brew") is the most popular package manager for macOS, simplifying software installation compared to manual downloads.
In Clawdbot Installation Context:
- Install Homebrew:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" - Install Node.js:
brew install node@20 - Install Clawdbot:
brew install clawdbot(if available) ornpm install -g clawdbotafter Node.js installed
Why Use Homebrew for Clawdbot:
- Handles Node.js dependency automatically
- Manages PATH configuration
- Simplifies updates:
brew upgrade clawdbot - Integrates with macOS LaunchAgent for auto-start
Homebrew Locations:
# Intel Macs
/usr/local/Cellar/clawdbot/
# Apple Silicon (M1/M2/M3)
/opt/homebrew/Cellar/clawdbot/
๐ก systemd (Linux Service Manager)
systemd is the initialization system used by most modern Linux distributions to manage services, including auto-starting Clawdbot on boot.
In Clawdbot Installation Context:
- Service File:
/etc/systemd/system/clawdbot.servicedefines how Clawdbot runs - Enable Auto-Start:
sudo systemctl enable clawdbot - Start Service:
sudo systemctl start clawdbot - View Logs:
sudo journalctl -u clawdbot -f
systemd Unit File Example:
[Unit]
Description=Clawdbot AI Assistant
After=network.target
[Service]
Type=simple
User=youruser
ExecStart=/usr/bin/clawdbot start
Restart=on-failure
[Install]
WantedBy=multi-user.target
Why systemd Matters:
- Ensures Clawdbot starts automatically after reboot
- Restarts Clawdbot if it crashes
- Captures logs to system journal (centralized logging)
- Manages process lifecycle (start/stop/restart)
Alternative to systemd: Old distributions use init.d or upstart, but 95%+ of modern Linux uses systemd.
๐ก Administrator Permissions (Windows UAC)
UAC (User Access Control) is Windows security feature that prevents unauthorized system changes. Clawdbot requires administrator rights to install as a system service.
In Clawdbot Installation Context:
- Why Needed: System service installation modifies registry and creates scheduled tasks
- How to Grant: Right-click PowerShell โ "Run as Administrator"
- What Happens: UAC prompt asks "Do you want to allow this app to make changes?" โ Click "Yes"
Without Administrator Rights:
ERROR: Access denied
Service installation failed
Run PowerShell as administrator to complete setup
After Granting Rights:
โ
System service installed
โ
Auto-start configured
โ
PATH updated
Security Note: Only run installer as administrator when installing. Daily use of Clawdbot doesn't require admin rights.
๐ก Localhost Port 3000
localhost is a hostname that refers to the current computer. Port 3000 is the default web server port Clawdbot uses for its web interface.
In Clawdbot Installation Context:
- Access URL:
http://localhost:3000orhttp://127.0.0.1:3000 - What's Hosted: Clawdbot dashboard, chat interface, settings, logs
- Changing Port: Edit
~/.clawdbot/config.jsonโ"port": 3001
Port Already in Use Error:
ERROR: Port 3000 is already in use
# Windows fix:
netstat -ano | findstr :3000
taskkill /F /PID <PID>
# macOS/Linux fix:
lsof -ti:3000 | xargs kill -9
Remote Access (Advanced):
# Make accessible from other devices on network
clawdbot config set host 0.0.0.0
# Access from phone/tablet:
http://192.168.1.100:3000 # Use your computer's local IP
Security Warning: Localhost is private to your computer. If you set host to 0.0.0.0, anyone on your network can access Clawdbot (add authentication if doing this).
๐ก Quick Start vs Advanced Setup
During onboarding, Clawdbot offers Quick Start or Advanced Configuration. The video creator chooses Quick Start.
Quick Start Mode:
- Skips network configuration (uses defaults)
- Minimal prompts (AI provider, channels, skills)
- Defaults to secure settings (localhost only)
- Best for first-time users
Advanced Configuration Mode:
- Custom port and host settings
- Webhook configuration
- SSL/TLS certificate setup
- Proxy settings for corporate networks
- Memory limits and context window customization
- Best for experienced users or server deployments
Recommendation: Always choose Quick Start for first install. You can change all settings later via clawdbot config without reinstalling.
๐ก API Provider Selection
API Provider is the AI service powering Clawdbot's intelligence. The video shows the creator skipping initially, then choosing Mistral later.
Why Skip During Install?:
- Test basic installation first before committing to paid API
- Configure API key later when you're ready to use Clawdbot seriously
- Avoid mistakes entering API keys during rushed setup
Configuring Later:
# After installation:
clawdbot config set provider anthropic
clawdbot config set apiKey sk-ant-your-key-here
clawdbot config set model claude-sonnet-3-7
clawdbot restart
Cost Awareness: Most providers charge per API call. Running Clawdbot without configuring provider lets you explore the interface without incurring charges.
โญ Highlights
- ๐ฅ๏ธ Universal Cross-Platform Support - Single installation process works on Windows 10/11, macOS 11+, and all major Linux distributions (Ubuntu, Debian, Fedora, Arch)
- โก One-Command PowerShell Install - Windows users run
irm https://claw.bot/install.ps1 | iexto automatically install Node.js, Clawdbot, and system service in under 2 minutes - ๐ Administrator Mode Critical on Windows - Most common error: "Service installation failed"โfix by closing terminal and running PowerShell as Administrator
- ๐ค Skip Everything During First Install - Best practice shown in video: skip AI provider, channels, and skills initially to test core functionality, configure incrementally later
- ๐ฆ NPM Global Install Alternative - Developers with Node.js already installed can use
npm install -g clawdbot && clawdbot onboardon any platform - ๐บ Homebrew Simplifies macOS Setup -
brew install node@20 && npm install -g clawdbothandles dependencies automatically without manual downloads - ๐ Instant Web Interface at localhost:3000 - No external hosting neededโaccess full dashboard in browser immediately after installation completes
- ๐ง Modular Skill System - Install only needed integrations (GitHub, Calendar, Email) via
clawdbot skills installafter confirming base system works
๐ Related Articles
- Clawdbot Free 24/7 Hosting: Complete AWS Setup Guide 2026
- Clawdbot + Mac Mini / VPS: The Ultimate Local AI Assistant Guide 2026
- I Hired My First AI Employee: Clawdbot Business Automation Guide 2026
- Telegram Bot Setup for Clawdbot: Complete Integration Guide 2026
- Node.js Installation on Windows: Complete Developer Guide 2026
- systemd Service Configuration: Linux Auto-Start Tutorial 2026
๐ฏ Get Started with Clawdbot Installation Today
Ready to install your own AI assistant? Follow these platform-specific quickstart guides:
Windows 10/11 Users:
# 1. Open PowerShell as Administrator (Win+X โ "PowerShell (Admin)")
# 2. Run installer:
irm https://claw.bot/install.ps1 | iex
# 3. Follow onboarding prompts
# 4. Access at http://localhost:3000
macOS Users:
# 1. Install Homebrew (if not already installed):
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
# 2. Install Node.js and Clawdbot:
brew install node@20
npm install -g clawdbot
# 3. Run onboarding:
clawdbot onboard
# 4. Access at http://localhost:3000
Linux Users:
# 1. Install Node.js (Ubuntu/Debian):
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt update && sudo apt install -y nodejs
# 2. Install Clawdbot:
sudo npm install -g clawdbot
# 3. Run onboarding:
clawdbot onboard
# 4. Optional: Configure systemd service
sudo systemctl enable clawdbot
sudo systemctl start clawdbot
Post-Installation Checklist:
- โ Access web interface at http://localhost:3000
- โ Configure AI provider (Anthropic, Mistral, OpenAI, or skip)
- โ Add one channel (Telegram recommended for beginners)
- โ
Install 1-2 essential skills (e.g.,
calendar,github) - โ Test basic commands in chat interface
- โ Configure auto-start (Windows service/macOS LaunchAgent/Linux systemd)
Troubleshooting Resources:
- ๐บ Watch Full Video: roseindiatutorials Installation Demo
- ๐ Official Docs: claw.bot/docs/installation
- ๐ฌ Community Support: Discord Server - 24/7 help from contributors
- ๐ GitHub Issues: github.com/clawdbot/clawdbot/issues
- ๐ง Email Support: support@claw.bot (enterprise users)
Common First-Time Questions:
"Do I need coding experience?"
- No! Installation is non-technical (one-command). Using Clawdbot is like chatting with a person.
"How much does it cost?"
- Software: Free and open-source
- API costs: $0 initially (skip provider), then $20-100/month depending on usage and model choice
"Can I run it on a Raspberry Pi?"
- Yes! Raspberry Pi 4 (8GB) or Pi 5 works. Performance is slower but functional for light use.
"What if I mess up the installation?"
- Uninstall:
npm uninstall -g clawdbotand start over. Clawdbot doesn't modify system files beyond its own directory.
Next Steps After Installation:
- Week 1: Explore web interface, test basic chat without AI provider
- Week 2: Add API key, choose model (start with Sonnet 3.7 for cost/performance balance)
- Week 3: Set up Telegram channel for mobile access
- Week 4: Install GitHub or Calendar skill based on your needs
- Month 2+: Explore advanced automation (cron jobs, custom skills, multi-channel)
Share this guide with friends struggling with Windows PowerShell installation or confused about AI provider selection. The "administrator mode" fix alone saves hours of troubleshooting!
Newsletter: Get weekly Clawdbot tutorials, skill highlights, and troubleshooting tips. Subscribe here
Need help? Post in comments below or join our Discord community where over 15,000 users help each other with installation issues, configuration, and custom setups.