ClawdBot on Mac Mini

🍎 Why Mac Mini is Perfect for ClawdBot

The Mac Mini has become the de facto standard for running ClawdBot as a home AI server. Here's why:

Real-World Use Case

Many ClawdBot users report running Mac Mini M1/M2 as dedicated AI servers, accessing their assistant via Telegram/WhatsApp from anywhere in the world. The Mac Mini sits quietly in a closet, consuming less power than a light bulb.

🛒 Which Mac Mini Should You Buy?

Recommended Configurations

Our Recommendation

Mac Mini M2 with 16GB RAM and 512GB SSD is the sweet spot for ClawdBot:

• ✅ 16GB RAM handles browser automation smoothly
• ✅ 512GB storage for conversation history and skills
• ✅ M2 chip is powerful enough for all ClawdBot features
• ✅ Can run small local models (7B parameters) via Ollama

Used vs. New

Used M1 Mac Mini (2020) can be found for $400-500 on eBay/Craigslist. Excellent budget option - performance is nearly identical to M2 for ClawdBot workloads.

🔧 Installation Steps

Step 1: Initial macOS Setup

# Update macOS to latest version
# System Settings > General > Software Update

# Install Xcode Command Line Tools
xcode-select --install

Step 2: Install Homebrew

# Install Homebrew package manager
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# Add Homebrew to PATH (M1/M2/M3 Macs)
echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

Step 3: Install Node.js

# Install Node.js 22 via Homebrew
brew install node@22

# Verify installation
node --version  # Should show v22.x.x
npm --version

Step 4: Install ClawdBot

# Install ClawdBot globally
npm install -g clawdbot@latest

# Run onboarding wizard
clawdbot onboard

Follow the wizard prompts to:

• Set up workspace directory
• Configure Gateway port (default: 18789)
• Add AI provider API keys
• Connect messaging channels

For detailed macOS installation, see: ClawdBot for Mac Guide

🚀 Auto-Start Configuration

To make ClawdBot start automatically when your Mac Mini boots:

Method 1: LaunchAgent (Recommended)

# Create LaunchAgent directory if it doesn't exist
mkdir -p ~/Library/LaunchAgents

# Create plist file
nano ~/Library/LaunchAgents/com.clawdbot.gateway.plist

Add this content:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.clawdbot.gateway</string>
    <key>ProgramArguments</key>
    <array>
        <string>/opt/homebrew/bin/clawdbot</string>
        <string>gateway</string>
        <string>start</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>KeepAlive</key>
    <true/>
    <key>StandardOutPath</key>
    <string>/tmp/clawdbot.log</string>
    <key>StandardErrorPath</key>
    <string>/tmp/clawdbot.error.log</string>
</dict>
</plist>

Load the LaunchAgent:

# Load the agent
launchctl load ~/Library/LaunchAgents/com.clawdbot.gateway.plist

# Verify it's running
launchctl list | grep clawdbot

Method 2: Using ClawdBot's Built-in Service Installer

# Let ClawdBot install itself as a service
clawdbot gateway install-service

# Start the service
clawdbot gateway start-service

🌐 Remote Access Setup

Access your Mac Mini ClawdBot server from anywhere:

Option 1: Tailscale (Recommended - Easiest)

Tailscale creates a secure VPN mesh network. No port forwarding needed!

# Install Tailscale
brew install --cask tailscale

# Open Tailscale and sign in
# Your Mac Mini gets a permanent Tailscale IP (e.g., 100.x.x.x)

# Access ClawdBot UI from anywhere:
# http://100.x.x.x:18789

Option 2: Dynamic DNS + Port Forwarding

For advanced users who want direct internet access:

1. Sign up for free DDNS service (No-IP, DuckDNS)
2. Configure your router to forward port 18789 to Mac Mini's local IP
3. Enable firewall rules on Mac Mini
4. Access via https://yourdomain.duckdns.org:18789

Security Warning: Always use HTTPS and strong authentication when exposing to internet!

Option 3: SSH Tunnel

# From remote machine, create SSH tunnel
ssh -L 18789:localhost:18789 user@your-mac-mini-ip

# Then access http://localhost:18789 on remote machine

⚙️ Power & Performance Optimization

Prevent Sleep Mode

Critical for 24/7 operation:

# Prevent system sleep while plugged in
sudo pmset -c sleep 0
sudo pmset -c disksleep 0
sudo pmset -c displaysleep 10  # Display can sleep

# Verify settings
pmset -g

System Settings Checklist

• ✅ Energy Saver: Prevent computer sleep when display is off
• ✅ Screen Saver: Set to "Never" or 1 hour
• ✅ Automatic Updates: Enable but set to install at 3 AM
• ✅ Firewall: Enable with ClawdBot port allowed

Power Consumption

📊 Monitoring & Maintenance

Check ClawdBot Status

# Check if Gateway is running
clawdbot gateway status

# View logs
tail -f /tmp/clawdbot.log

# Check resource usage
top -pid $(pgrep -f clawdbot)

Automated Health Checks

Create a simple monitoring script:

#!/bin/bash
# Save as ~/check-clawdbot.sh

if ! pgrep -f "clawdbot gateway" > /dev/null; then
    echo "ClawdBot is down! Restarting..."
    launchctl start com.clawdbot.gateway
    # Optional: Send notification via Telegram
fi

Run via cron every 5 minutes:

# Edit crontab
crontab -e

# Add this line:
*/5 * * * * ~/check-clawdbot.sh

Backup Strategy

# Backup ClawdBot data
tar -czf clawdbot-backup-$(date +%Y%m%d).tar.gz ~/.clawdbot/

# Restore from backup
tar -xzf clawdbot-backup-20260127.tar.gz -C ~/

💰 Total Cost of Ownership

5-Year Cost Comparison

Verdict: Mac Mini costs are comparable to cloud hosting, but you get:

• ✅ Complete privacy and control
• ✅ iMessage integration (macOS exclusive)
• ✅ No monthly bills (just electricity)
• ✅ Hardware you own and can repurpose

🔧 Troubleshooting Mac Mini Issues

Mac Mini Goes to Sleep Despite Settings

Solution:

# Use caffeinate to prevent sleep
caffeinate -s &

# Or add to LaunchAgent

Can't Access from Remote Network

Check:

• Mac Mini firewall settings (allow port 18789)
• Router port forwarding configuration
• ISP doesn't block incoming connections
• Use Tailscale as easier alternative

High Memory Usage

Solution:

# Restart ClawdBot Gateway
clawdbot gateway restart

# Clear browser cache if using browser automation
rm -rf ~/.clawdbot/browser-cache/