I Ran ClawdBot for 3 Weeks: VPS Setup, Cheapest Models & Real Experience (2026 Guide)

TL;DR - Quick Summary

What: 21-day real-world ClawdBot experience with VPS setup, cost optimization, and practical insights

Best Discovery: Anatigravity provides FREE generous Claude Opus 4.5 tier (better than paid Claude subscription)

Recommended Setup: Contabo VPS at $4.95/month + Anatigravity for models = total cost under $5/month

VPS vs Mac Mini: VPS wins for 90% of users (unless deeply integrated in Apple ecosystem)

Biggest Challenge: Software still early-stage, expect occasional SSH troubleshooting

Best Use Cases: Product analytics automation, email organization, move planning, financial calculations

🎯 Key Takeaways

✅ VPS is Sufficient: $4.95/month Contabo VPS handles ClawdBot perfectly (Mac Mini unnecessary for most)

✅ Anatigravity Hack: Free, generous Claude Opus 4.5 access (better limits than paid Claude subscription)

✅ Apple Ecosystem Trade-off: VPS can't access iMessage, iCloud, Apple Notes (only reason to choose Mac Mini)

✅ Memory System Superior: Markdown-based memory > ChatGPT's hidden memory system

✅ Full File System Access: ClawdBot's local access > cloud-based API integrations

✅ Maintenance Required: Expect occasional failures, SSH troubleshooting needed

✅ Real Productivity Gains: Product analytics, email parsing, cost basis calculations, packing lists

📖 Complete 3-Week Experience Report

Why I Started: The Airport Wi-Fi Problem

The origin story is unique: I was traveling around South America, and on many flights, they only offered free Wi-Fi for messaging services (WhatsApp, Telegram, etc.).

I wanted AI access on flights without paying for expensive in-flight Wi-Fi. Right after New Year's, people were buzzing about ClawdBot on Twitter, so I decided to give it a try.

Initial Setup: Started locally on MacBook, found it compelling

Next Step: Moved to 24/7 VPS deployment

Timeline: 21 days ago (as confirmed by asking ClawdBot itself)

VPS vs Mac Mini: The Real Comparison

Everyone on Twitter is talking about buying Mac Minis for ClawdBot. Here's the honest breakdown:

Mac Mini ($600-800 one-time)

Pros:

✅ Full Apple ecosystem integration
✅ Access to iMessage, iCloud Drive, Apple Notes
✅ Native Mac OS environment
✅ Can run local models easily
✅ One-time cost (no monthly fees)

Cons:

❌ $600-800 upfront investment
❌ Physical device management (power, space, maintenance)
❌ Home network dependency
❌ Limited portability

VPS ($4.95/month = $59/year)

Pros:

✅ 10x cheaper first year ($59 vs $600)
✅ No physical hardware to maintain
✅ True 24/7 uptime (no power outages)
✅ Access from anywhere with internet
✅ Easy backup and migration
✅ Scalable (upgrade RAM/CPU as needed)

Cons:

❌ Cannot access Apple ecosystem services
❌ Ongoing monthly cost (though minimal)
❌ Requires basic SSH knowledge
❌ Slightly more latency (negligible in practice)

My Verdict: For 90% of users, VPS is the smarter choice. Only choose Mac Mini if:

You heavily rely on iMessage integration
You need iCloud Drive access for file operations
You use Apple Notes extensively
You want to run fully local models (Ollama, etc.)

For me, the pain of not having Apple service access hasn't been enough to justify a Mac Mini purchase. Maybe in another month if frustration builds up, but so far, having access to Gmail and other non-Apple services has been sufficient.

Choosing a VPS Provider: Why Contabo Over Hetzner

Most people recommend Hetzner (German company), and there's nothing wrong with them. However:

Hetzner Issues:

❌ Very stringent verification process
❌ Quick to ban accounts (according to reports)
❌ I already run other services there (didn't want risk)

Contabo Alternative:

✅ Much easier verification
✅ No banning issues reported
✅ $4.95/month for lowest plan
✅ More than enough resources for ClawdBot
✅ 3 weeks of stable operation (no issues)

Contabo Plan Details:

💰 Price: $4.95/month (lowest tier)
🖥️ Resources: Sufficient for ClawdBot + occasional Claude Code sessions
🌍 Location: Multiple datacenter options
📊 Performance: No lag or issues observed

I even run remote Claude Code sessions on the same VPS occasionally - it handles both workloads without problems.

Other VPS Options:

DigitalOcean ($6/month)
Linode/Akamai ($5/month)
Vultr ($5/month)
AWS Lightsail ($3.50/month)

Step-by-Step VPS Setup Process

Step 1: Sign Up and Get VPS Details

Sign up for Contabo (or your preferred VPS provider)
Purchase lowest plan ($4.95/month)
Receive email with VPS details:
- IP address
- Root password
- SSH port (usually 22)

Step 2: Create SSH Connection String

If you're unsure how to format your SSH connection:

# Basic SSH format
ssh root@your-vps-ip-address

# Example
ssh root@185.123.45.67

Not sure how? Just ask ChatGPT: "How do I SSH into my VPS with IP X and port Y?"

Step 3: Choose SSH Client

I use Termius - it's popular, user-friendly, and handles SSH connections elegantly.

Termius Setup:

Download Termius (free plan works fine)
Open Termius
Click "New Host"
Enter:
- Label: "ClawdBot VPS"
- Address: Your VPS IP
- Port: 22 (default)
- Username: root
- Password: From email
Click Connect

First-time users: Termius guides you through the process step-by-step. If stuck, ask ChatGPT for help.

Alternative SSH Clients:

Terminal (Mac/Linux built-in)
PuTTY (Windows)
MobaXterm (Windows)
Tabby
iTerm2 (Mac)

Step 4: Install Tmux (Highly Recommended)

Why Tmux?

ClawdBot is still early-stage software. It fails occasionally and you'll need to SSH in to troubleshoot.

Without Tmux: Every SSH session is fresh, you lose context
With Tmux: Session persists in memory, pick up where you left off

Install Tmux:

# Ubuntu/Debian
apt update && apt install tmux

# Start tmux session
tmux new -s clawdbot

# Detach: Ctrl+B, then D
# Reattach later: tmux attach -t clawdbot

This is optional but highly recommended for quality of life.

Step 5: Create ClawdBot Folder

# Create dedicated directory
mkdir ~/clawdbot
cd ~/clawdbot

Step 6: Run ClawdBot Installer

The official website now has excellent, up-to-date instructions (much better than when I started 3 weeks ago).

# One-line installer from clawdbot.com
curl -fsSL https://clawdbot.ai/install.sh | bash

# Alternative: npm installation
npm install -g clawdbot

Onboarding Wizard:

If it doesn't run automatically:

clawdbot onboard

The wizard will guide you through:

Connecting messaging channels (Telegram/WhatsApp)
Choosing AI model provider
Setting up API keys
Configuring permissions

Messaging Channels: Telegram vs WhatsApp

I set up both Telegram and WhatsApp. Here's my experience:

Telegram (Recommended ⭐)

Pros:

✅ Easy setup (5 minutes)
✅ Looks like separate bot contact
✅ Better user experience
✅ More reliable
✅ Bot API is robust

Setup Process:

Open Telegram
Message @BotFather
Type /newbot
Follow instructions
Receive bot token
Paste token into ClawdBot onboarding
Done!

WhatsApp (Not Recommended)

Cons:

❌ Finicky setup process
❌ Doesn't look like separate contact properly
❌ Less reliable in my experience
❌ More complex configuration

When to Use WhatsApp:

You exclusively use WhatsApp
Your team/family is on WhatsApp
You have a dedicated phone number for the bot

For most users: Just use Telegram. The experience is significantly better.

The Model Choice: Anatigravity Changes Everything

This is the most important cost optimization discovery.

Available Models

Anthropic Claude:

Opus 4.5 (most capable)
Sonnet 4.5 (balanced)
Haiku (fast/cheap)

Other Options:

Minimax
GLM 4.7
GPT-4o
Local models (Ollama)

Why Claude Opus 4.5 is Essential

I tested multiple models. Claude Opus 4.5 is the only one that captures ClawdBot's "magic personality".

Other models work functionally, but the personality, understanding of context, and quality of responses don't compare. For ClawdBot specifically, Claude Opus is worth the premium.

The Problem: Token Consumption

ClawdBot burns through tokens rapidly. If you use your Claude subscription for:

ClawdBot conversations
Claude Code development sessions

You'll run out of tokens fast and can't code when you need to.

The Solution: Anatigravity (Free!)

What is Anatigravity?

Google's AI IDE - essentially a Cursor/Windsurf clone.

Why It's Perfect for ClawdBot:

✅ Very generous free tier of Claude Opus 4.5
✅ Better limits than paid Claude subscription
✅ I've only hit limits a few times in 3 weeks
✅ Separate from your coding Claude subscription

Comparison:

Provider	Cost	Limits	Experience
Claude Subscription	$20/month	Hit constantly with ClawdBot	Poor for dual use
Anatigravity	FREE	Rarely hit limits	Excellent
Anthropic API	Pay-per-token	Usage-based	Expensive with ClawdBot

How to Set Up Anatigravity with ClawdBot:

During the onboarding process, when asked for AI provider, select "Anatigravity" and follow authentication prompts.

Detailed instructions are in the ClawdBot docs at clawdbot.com/docs

This single trick saved me $20/month on Claude subscriptions.

Real-World Usage: What I Actually Use It For

After 3 weeks, here are my genuine, practical use cases:

Use Case 1: Travel Packing Lists

Command: "Create a packing list for my 2-week South America trip"

Result: Detailed, personalized list based on:

My previous packing list history (remembered)
Weather forecasts for destinations
Activities planned
Personal preferences learned over time

Much better than ChatGPT because it has access to my previous trip files.

Use Case 2: Email Management

Setup: Gave ClawdBot access to my Gmail via API

Commands:

"Summarize important emails from today"
"Find all emails related to Project X and create a timeline"
"Extract all meeting invites from this week and add to calendar"

Why It's Better: Full file system access means it can create local markdown files with organized information, not just give me text responses.

Use Case 3: Product Analytics Automation (Dumpling AI)

Setup:

Gave ClawdBot API access to PostHog (analytics platform)
Configured cron job to run weekly

Automated Workflow:

ClawdBot makes API requests to PostHog
Analyzes user behavior, retention, feature usage
Generates comprehensive report
Sends summary via Telegram every Monday morning

Time Saved: 2-3 hours of manual analytics work per week

Use Case 4: Financial Cost Basis Calculation

Scenario: Needed to calculate cost basis for my entire share portfolio for tax purposes.

What ClawdBot Did:

Accessed my Gmail inbox (with permission)
Searched through hundreds of emails from brokers
Cross-referenced buy/sell confirmations
Calculated cost basis for each position
Generated spreadsheet with complete records

Time Saved: 8+ hours of tedious manual work

Use Case 5: Move Organization

Scenario: Planning a residential move

How ClawdBot Helped:

Created markdown file just for the move project
Every conversation updated the move file
Tracked:
- Quotes from moving companies
- Utility transfer dates
- Address change notifications needed
- Packing timeline
- Budget tracking

vs ChatGPT Memory: ChatGPT has memory, but it's hidden behind the scenes and less detailed. ClawdBot creates explicit, detailed markdown files for major projects.

Why ClawdBot's Memory System is Superior

ChatGPT Memory:

❌ Hidden "black box" system
❌ Can't directly edit or view
❌ Less structured
❌ Forgets details over time

ClawdBot Memory:

✅ Explicit markdown files you can read
✅ Can manually edit if needed
✅ Super detailed project tracking
✅ Full file system access
✅ Create dedicated files for different projects

Example ClawdBot Memory Structure:

~/clawdbot-memory/
├── personal-info.md
├── projects/
│   ├── move-project.md
│   ├── dumpling-ai-analytics.md
│   └── south-america-trip.md
├── preferences/
│   ├── coding-style.md
│   └── communication-preferences.md
└── work/
    ├── meeting-notes.md
    └── project-timelines.md

Each file is continuously updated with relevant information as you chat with ClawdBot.

The Power of Full File System Access

This is the fundamental architectural advantage of ClawdBot:

Cloud AI (ChatGPT, Claude Web):

Can access services via APIs
Can use "tools" and integrations
Still sandboxed from your actual system
Limited to what APIs expose

ClawdBot (Local/VPS):

Full file system access
Can execute any command
Can read/write any file
Can install software
Can manage system services
Complete system control

Real Difference:

APIs and MCPs are powerful, but they're fundamentally different from giving someone full access to your device.

ClawdBot running locally (or on your VPS) has access to everything, enabling automation that's simply impossible with cloud-based agents.

Security Warning: The Risk You Need to Understand

Critical Warning: Running ClawdBot gives it access to basically everything on your device.

Potential Risks:

🚨 ClawdBot could delete files
🚨 ClawdBot could modify configurations
🚨 ClawdBot could execute destructive commands
🚨 ClawdBot could expose sensitive data

Mitigation Strategies:

Run on Dedicated VPS (what I do)
- Isolate from personal MacBook
- Limit what's stored on the VPS
- Easy to wipe and recreate if needed
Run in Docker Container
- Additional isolation layer
- Limit file system access
- Easier to contain damage
Use Permission Restrictions
- Start with minimal permissions
- Gradually expand as needed
- Review ClawdBot docs on sandboxing
Regular Backups
- Backup critical data elsewhere
- Use version control (Git)
- Test restore procedures

My Approach: I run ClawdBot on a dedicated Contabo VPS with only non-critical data. My main MacBook remains isolated.

Downsides & Challenges: The Honest Reality

Challenge 1: Software is Still Early-Stage

What This Means:

Bugs occur fairly frequently
ClawdBot sometimes stops responding
Need to SSH in to troubleshoot
Not "set it and forget it" yet

Frequency: I'd estimate I need to SSH in to fix something 2-3 times per week.

Typical Issues:

Process crashed, needs restart
Memory leak (restart required)
API connection timeout
Message queue backed up

Challenge 2: Manual Updates Required

ClawdBot doesn't auto-update. You need to:

SSH into your VPS
Run update command: clawdbot update (now available)
Restart ClawdBot

Frequency: Updates released weekly-ish

Challenge 3: Requires Technical Comfort

Minimum Skills Needed:

Basic SSH understanding
Terminal/command line comfort
Troubleshooting mindset
Reading error logs

Not For: Complete beginners expecting plug-and-play experience

Good For: Hobbyists, developers, tech enthusiasts willing to tinker

Challenge 4: VPS Means No Apple Ecosystem

As mentioned, this is my primary pain point.

Can't access:

iMessage
iCloud Drive
Apple Notes
Reminders
Apple Calendar (local)

I've learned to work around it by using Gmail, Google Calendar, and other cross-platform services. But if you're deeply embedded in Apple ecosystem, this limitation might justify the Mac Mini investment.

The Future: Why Local Agents are Inevitable

Despite the challenges, ClawdBot represents the future of AI assistants.

Core Insight: To do real work on your phone or laptop, AI needs to manipulate local files.

Cloud environments and sandboxes can replicate some of this, but the experience isn't there yet.

Analogy: Chromebooks a few years ago

Technically worked
Cloud-based everything
But the experience wasn't as good as local devices
Now they're better, but still have limitations

Prediction: In the future, everyone will run local AI agents because:

Privacy concerns grow
Need for real file system access
Desire for ownership over AI infrastructure
Cost optimization (own vs rent)

Whether the future is ClawdBot specifically or something else, this is a glimpse into where personal AI is heading.

Cost Breakdown: Total Monthly Investment

VPS Hosting: $4.95/month (Contabo)
AI Model: $0/month (Anatigravity free tier)
Messaging: $0 (Telegram is free)

Total: $4.95/month (or $59/year)

Compare to Alternatives:

ChatGPT Plus: $20/month ($240/year)
Claude Pro: $20/month ($240/year)
Mac Mini: $600-800 one-time (12-16 months of VPS cost)

My Setup is 4x cheaper than a paid AI subscription and provides far more capabilities.

🎓 Q&A - Common Questions

Q1: Why Contabo instead of Hetzner?
A: Easier verification, no reports of quick bans, and I already run other services on Hetzner (didn't want risk). Contabo has been rock-solid for 3 weeks.

Q2: Can I use Claude Pro subscription for ClawdBot?
A: Yes, but not recommended if you also use Claude Code for development. ClawdBot burns tokens fast and you'll hit limits constantly. Use Anatigravity instead.

Q3: What is Anatigravity exactly?
A: Google's AI IDE (Cursor/Windsurf clone) with a very generous free tier of Claude Opus 4.5. Perfect for ClawdBot use.

Q4: How often does ClawdBot break?
A: In my 3-week experience, I need to SSH in to fix something 2-3 times per week. Usually just a restart resolves it.

Q5: Should I buy a Mac Mini?
A: Only if:

You need iMessage integration
You rely heavily on iCloud Drive
You use Apple Notes/Reminders extensively
You want to run local models

For 90% of users, VPS is the better choice.

Q6: Is Telegram or WhatsApp better?
A: Telegram is significantly better. Easier setup, better UX, more reliable. I don't recommend WhatsApp unless you have a specific requirement.

Q7: What if I don't know SSH?
A: Ask ChatGPT or Claude to teach you the basics. It takes 30 minutes to learn enough to get started. Also, Termius makes it very user-friendly.

Q8: Can I run ClawdBot on my laptop?
A: Yes, it works perfectly. The only downside is it won't be 24/7 unless you keep your laptop on all the time.

Q9: What about security? Should I be worried?
A: Yes, be cautious. ClawdBot has full file system access. Run it on a dedicated VPS (not your main machine) until you're comfortable with the security model.

Q10: How much Anatigravity free tier do you get?
A: The limits aren't publicly documented, but in 3 weeks of fairly heavy use, I've only hit limits a few times - far better than Claude Pro subscription.

💡 Pro Tips & Best Practices

Tip #1: Start with Telegram Only
Don't complicate your setup with multiple channels initially. Get comfortable with Telegram first, expand later.

Tip #2: Use Tmux from Day One
Don't wait until you hit issues. Set up Tmux immediately - you'll thank yourself later.

Tip #3: Keep a Separate Claude Subscription
Use Anatigravity for ClawdBot, keep your Claude Pro for development/coding. Don't mix them.

Tip #4: Create Project-Specific Memory Files
Explicitly ask ClawdBot to create markdown files for major projects. Example:
"Create a new markdown file called move-project.md and track all information related to my move"

Tip #5: Set Up Cron Jobs for Recurring Tasks
Product analytics, morning briefings, backup checks - automate with cron from the start.

Tip #6: Monitor Token Usage
Even with free Anatigravity tier, keep an eye on usage. If you hit limits frequently, consider:

Using Haiku for simple tasks
Upgrading to paid API
Optimizing your prompts

Tip #7: Join the Discord
The ClawdBot community is active and helpful. Many problems have already been solved - search Discord before troubleshooting.

Tip #8: Document Your Setup
Keep notes on:

Your VPS details
SSH connection string
API keys used
Cron jobs configured
Custom configurations

Makes troubleshooting and migration easier.

🔧 Technical Setup Reference

Contabo VPS Specs (Lowest Plan)

Spec	Value
Price	$4.95/month
RAM	4GB
CPU	2 vCores
Storage	50GB SSD
Bandwidth	Unlimited
OS	Ubuntu 22.04 (recommended)

Essential Commands

# SSH into VPS
ssh root@your-vps-ip

# Start tmux session
tmux new -s clawdbot

# Install ClawdBot
curl -fsSL https://clawdbot.ai/install.sh | bash

# Run onboarding
clawdbot onboard

# Start ClawdBot
clawdbot start

# Update ClawdBot
clawdbot update

# Check status
clawdbot status

# View logs
clawdbot logs

# Restart ClawdBot
clawdbot restart

# Detach from tmux
Ctrl+B, then D

# Reattach to tmux
tmux attach -t clawdbot

Telegram Bot Setup

Open Telegram
Search for @BotFather
Send: /newbot
Choose bot name: "My ClawdBot"
Choose username: "my_clawdbot" (must end in 'bot')
Receive token: 1234567890:ABCdefGHIjklMNOpqrsTUVwxyz
Paste into ClawdBot onboarding

📊 3-Week Usage Statistics

Total Days Running: 21 days
Uptime: ~95% (downtime from my fixes/updates)
Messages Sent: 200+ conversations
Tasks Automated: 8 recurring cron jobs
Files Created: 15 project markdown files
SSH Fixes Required: 6 times (about 2-3 per week)
Token Limit Hits: 2 times (both on Anatigravity)
Total Cost: $4.95 (one month of VPS)
Time Saved: Estimated 10-15 hours over 3 weeks

🎯 Final Verdict: Should You Set Up ClawdBot?

Yes, if:

✅ You're comfortable with basic terminal/SSH
✅ You want true AI automation
✅ You're okay with occasional troubleshooting
✅ You value ownership over AI infrastructure
✅ You want to save money vs paid subscriptions
✅ You're excited about cutting-edge tech

No, if:

❌ You want plug-and-play with zero maintenance
❌ You're not comfortable with command line
❌ You need 100% uptime/reliability
❌ You don't have time for occasional fixes
❌ You prefer polished, finished products

My Honest Take:

ClawdBot is a hobbyist/high-maintenance tool right now, but it's also a peek into the future.

It's been very useful for me despite the occasional hiccups. The productivity gains from automated analytics, email organization, and project tracking have been worth the $5/month and occasional 15-minute troubleshooting sessions.

If you're the type who enjoys tinkering and doesn't mind early-stage software, absolutely try it. Even if the future of personal AI looks different, this is educational and fun to experiment with.

For me, it's staying. Looking forward to seeing how it evolves over the next few months.

🔗 Essential Resources

Official Links:

VPS Providers Mentioned:

Contabo - $4.95/month (what I use)
Hetzner - Popular alternative
DigitalOcean - $6/month
Vultr - $5/month

Related Articles:

Tags: #ClawdBot #VPSSetup #Contabo #Anatigravity #RealReview #CostOptimization #MacMiniAlternative #3WeekReview

Last Updated: January 27, 2026
Reading Time: 12 minutes
Difficulty: Intermediate
Cost: $4.95/month (VPS only)

💬 Share Your Experience

Have you set up ClawdBot on a VPS? What's been your experience? Drop a comment below or join the discussion:

Would love to hear what everyone is doing with their ClawdBots!