Full walkthrough for deploying an always-on AI agent from scratch
- Single-command deployment to a cloud server running 24/7
- Complete setup instructions for Telegram, Google apps, voice input, and scheduled tasks
- Deep dive into security practices, budget management, and intelligent model selection
- Perfect for: Anyone wanting a proactive AI assistant that executes real tasks autonomously
Jump to contents (24 comprehensive sections)
Introduction
This tutorial provides complete instructions for deploying OpenClaw – the open-source autonomous AI agent with over 333,000 GitHub stars. You’ll create a secure, continuously-running system that communicates via Telegram, integrates with Google Workspace, executes scheduled operations, and processes voice commands.
Zero coding experience needed. Every instruction is detailed.
Execute each step in sequence. Security sections are mandatory.
For background on OpenClaw capabilities and use cases, consult the OpenClaw Review article. For potential challenges and limitations, reference the OpenClaw Problems analysis.
Understanding OpenClaw’s Architecture
Traditional AI assistants require you to initiate every interaction through a web interface. OpenClaw operates fundamentally differently – it runs persistently on dedicated infrastructure, maintains constant app connections, and executes actions autonomously.
Three foundational components:
1. Intelligence & Persistence
Connects to AI models via API, stores all interactions in local Markdown files, and continuously improves through accumulated context.
2. Continuous Operation
Runs without interruption, enabling proactive outreach, scheduled task execution, event monitoring, and automatic notifications.
3. Integration Layer
Connects with Telegram, Gmail, Google Calendar, Drive, Slack, Discord, and numerous other platforms to perform tangible work.
Historical note: Originally called Clawdbot (renamed due to Anthropic trademark issues), briefly renamed Moltbot before final branding as OpenClaw.
Real-World Applications
Community-verified implementations currently in production:
- Morning briefing system: Daily 7:00 AM calendar and email review with prioritized Telegram summary
- Interview preparation automation: Automatic research document creation when calendar shows interview appointments
- Fitness class booking: Continuous monitoring of gym schedule with instant registration when spots open
- Email management workflow: Draft response generation with mandatory approval before sending
- Code review automation: Nightly pull request analysis with Slack notifications
These represent actual deployments documented in r/openclaw and official community channels.
Hosting Infrastructure Options
| Deployment Method | Advantages | Disadvantages |
|---|---|---|
| Personal computer | No cost, immediate setup | Stops during sleep mode; full access to personal files |
| Dedicated hardware (Mac Mini, etc.) | Complete isolation; continuous operation when powered | $500+ initial investment; self-managed power and connectivity |
| Cloud VPS | Low cost ($5–13/month); guaranteed uptime; complete isolation; simple recovery | Recurring monthly expense |
Recommendation for beginners: Cloud VPS provides optimal balance. This guide uses Hostinger’s one-click OpenClaw template, eliminating terminal commands and Docker complexity. Manual deployment on alternative providers (DigitalOcean, Hetzner, etc.) remains available through standard installation procedures.
VPS Deployment via Hostinger
Hostinger provides pre-configured OpenClaw VPS images with automated Docker, dependency, and environment management.
Plan selection guidelines:
- KVM1 – Sufficient for basic automation and limited tasks
- KVM2 (2 cores, 8GB RAM, 100GB storage) – Recommended for most users
- KVM4 or higher – Required for local model execution via Ollama
Checkout configuration:
- Select minimum 12-month term for discount eligibility (24 months offers best per-month value)
- Disable pre-selected “ready-to-use AI” addon (you’ll configure your own API key for cost efficiency)
- Enable daily automatic backups (~$3/month) – essential for rollback capability when OpenClaw modifies its own configuration
- Choose server location with lowest latency to your geography
- Complete registration and payment
Initial System Configuration
Post-payment, Hostinger displays the OpenClaw configuration interface.
Critical first step: The OpenClaw gateway token field contains your master authentication credential. Click the visibility icon, copy the complete token, and store it in a password manager. Never share, screenshot, or save this token in plaintext.
Connecting Your First AI Model (Anthropic Example)
OpenClaw requires an AI model API connection to function.
Anthropic Claude setup:
- Navigate to Anthropic Console in new browser tab
- Create account or authenticate
- Click “Buy credits” and add minimum $40 (not $5)
Rationale: $5 minimum maintains Tier 1 status with restrictive rate limits (60K tokens/minute) that cause initial setup failures. $40 unlocks Tier 2 (450K tokens/minute) and provides extended usage under normal conditions. - Navigate to Manage → Limits → Spend limits, configure monthly cap (recommended: $100)
- Disable auto-reload (system will halt when credits depleted rather than auto-charging)
- Access API keys → Create key, assign name (e.g., “openclaw”), copy the key (displayed once only), paste into Hostinger configuration field
Alternative providers (OpenAI, Google Gemini, etc.) follow identical key generation procedures.
Scroll to bottom and click Deploy.
Dashboard Access
After deployment completion:
- In Hostinger panel: VPS → Manage (on your Docker instance)
- Click “Open Claw gateway”
- Authenticate with your saved gateway token
Security notice: The URL displays “Not secure” (HTTP protocol). Avoid access from public Wi-Fi. Production deployments should implement reverse proxy with HTTPS or use Tailscale for secure remote access.
Initial Configuration – Identity Interview
In dashboard chat, send: "Hey, let's get you set up. Read BOOTSTRAP.md and walk me through it."
This initiates the first-run interview from BOOTSTRAP.md. Provide comprehensive responses:
- Full name, professional role, time zone
- Preferred bot name/identity
- Communication style preferences
- Work priorities and objectives
Importance of detail: Brief responses limit the agent’s contextual understanding.
Communication style example:"Be sharp, direct, and dry. No corporate fluff, no filler phrases."
Following interview completion, the bot confirms identity configuration, locks the first memory entry, and removes the bootstrap file.
Critical Security Implementation
OpenClaw possesses terminal command execution, file system access, web browsing, and messaging capabilities. This power requires robust security controls.
Before connecting external services:
- Open official security documentation
- Copy complete URL
- Paste into OpenClaw chat with instruction:
"Implement and verify everything on this page, but leave allow_insecure set to true." - Confirm bot executes security audit and gateway restart
This automates hardening procedures. For comprehensive security analysis, consult the security section in the OpenClaw review.
Behavioral Guardrails
Configure explicit rules individually for clarity:
"When sending messages on my behalf, always draft first and get my approval.""Always ask before deleting files or making network requests.""If a task fails three times, stop. Limit runtime to 10 minutes unless I say otherwise."
Rules persist in workspace files (specifically AGENTS.md).
Progressive integration approach: Start with Telegram and limited skills. Do not connect primary email, financial accounts, or password managers until system trust is established.
Telegram Integration
In OpenClaw chat: "Let's set up Telegram."
The bot requests network permission (verification of approval gate functionality). Grant permission.
Setup procedure:
- Open chat with @BotFather on Telegram
- Send
/newbot - Provide bot name and unique username (must end with “bot”)
- Copy API token from BotFather
- Paste token into OpenClaw chat
- Message your new bot on Telegram, copy returned pairing code
- Paste pairing code into OpenClaw (adds your user ID to allowlist)
Test: Send "hello" in Telegram. Bot should respond in both dashboard and Telegram.
Additional platforms: 20+ messaging platforms supported (WhatsApp, Discord, Slack, Signal, iMessage [macOS only], etc.). Request platform-specific instructions from the bot.
Skill Installation
Skills are plugins providing concrete capabilities – Gmail access, calendar management, web search, file operations.
Two skill sources:
- ClawHub – Official marketplace (~3,200 skills currently)
- Telegram interface: Type
/clawhub
Security warning: Community analysis identified malicious instructions in significant percentage of community skills.
Safety protocol:
- Review VirusTotal report on skill page
- Audit requested permissions (note-taking skill should not require network access)
- Prefer official or verified skills
- High download counts do not guarantee safety
Google Workspace Skill (GOG)
Most popular initial skill – provides Gmail, Calendar, Drive, Contacts, Sheets, and Docs integration.
Installation:
In Telegram or dashboard: "Install the GOG skill."
For VPS deployment (non-macOS): "I am on a VPS running Ubuntu, not macOS. Walk me through setting up OAuth."
Google Cloud Console configuration:
- Create new project: “OpenClaw”
- Enable APIs: Gmail, Calendar, Drive, Sheets, Docs, People (Contacts)
- Configure OAuth consent screen:
- Application name: “OpenClaw”
- User type: External
- Add your email as test user
- Create OAuth client ID (Desktop application type)
- Download JSON credentials file
- Attach JSON file to Telegram message with context:
"I enabled all Google Workspace APIs and configured OAuth. Here is my client secret JSON. Please connect my Google account." - Follow prompts: open authorization URL, select account, accept permissions (“unverified app” warning is expected – you are the developer), copy final redirect URL back to chat
Functionality test:
"Add a meeting with John Smith to my calendar at 12:00 p.m. this Friday for 1 hour.""What's on my calendar this Wednesday?"
Workspace File Architecture
All agent knowledge resides in Markdown files within workspace directory – no database backend.
Eight files loaded per session:
| File | Purpose |
|---|---|
| SOUL.md | Bot personality and permanent behavioral rules |
| AGENTS.md | Behavioral controls (approval gates, limits, preferences) |
| USER.md | Complete user profile (name, timezone, work style) |
| MEMORY.md | Long-term facts and daily interaction log |
| TOOLS.md | Available skills and tool configurations |
| IDENTITY.md | Bot name and identity settings |
| HEARTBEAT.md | Continuous monitoring rules |
| BOOTSTRAP.md | First-run setup (deleted post-initialization) |
File interaction:
View: "Show me the contents of SOUL.md."
Edit: "Add this rule to AGENTS.md: Always confirm before sending emails."
Update: "Update USER.md with my communication preferences."
Quick single-message edits work optimally. Reserve extended interactive sessions for complex modifications.
Memory Management Configuration
Execute: "Enable compaction, memory flush, and session memory."
This ensures:
- Critical information persists to disk before context window limits
- Memory continuity across conversation sessions
- Agent retention of key facts during extended interactions
Note: Memory compaction remains imperfect – context loss during extended sessions is documented. These settings minimize data loss.
Automation Systems: Cron Jobs and Heartbeat
Cron Jobs
Scheduled tasks executing at specified times.
Example:"Create a daily job: Every morning at 7 a.m., check the weather for my city, check my Google Calendar, scan my Gmail for urgent items, and send me a summary on Telegram with my top priorities."
Bot confirms schedule and offers immediate test execution.
Heartbeat
Runs at short intervals (e.g., every 30 minutes) for continuous monitoring.
Enable: "Enable HEARTBEAT.md."
Best practices:
- Fixed-time tasks → cron job
- Continuous monitoring → heartbeat
- Avoid excessive heartbeat tasks (burns tokens each cycle)
Model Selection and Cost Structure
OpenClaw itself is free (MIT license). Actual expenses:
| Expense Category | Monthly Range |
|---|---|
| VPS hosting | $5–13 |
| Budget models (Haiku, GPT-4o Mini) | $5–20 |
| Mid-tier models (Sonnet, GPT-4o) | $30–80 |
| Flagship models (Opus, o1 Pro) | $100–300+ |
| Local models via Ollama | $0 (compute only) |
Cost escalation factors:
Every prompt loads entire workspace (all 8 files) into context. Complex prompts consume 50,000–100,000 tokens. Multiply by always-on cron jobs and heartbeats for cumulative cost.
Three primary cost traps:
- Using flagship models for all tasks (route routine operations to Haiku or Mini)
- Uncontrolled retry loops (behavioral guardrails prevent this)
- Frequent expensive heartbeats (every 5 minutes vs. every 30)
For comprehensive cost optimization strategies, reference the cost section in the problems article.
Model Routing Configuration
Add additional API keys through hosting provider’s environment variables (more secure than chat-based configuration).
Hostinger procedure:
Docker Manager → your OpenClaw project → Environment variables → add new key (e.g., OPENAI_API_KEY)
Save and deploy (restarts container).
Routing rules instruction:
"Use Claude Sonnet by default. Fall back to GPT-4o if unavailable. For coding tasks: use Opus with GPT-4o as fallback. For routine tasks: Haiku first, then GPT-4o Mini. When you run a task, tell me which model you are using. Save this as a permanent rule."
Restart gateway post-changes. Verify current model with /model command in Telegram.
Free Fallback Model Configuration
Configure minimum one free fallback model to maintain agent functionality when paid credits depleted or rate limits reached.
Popular free option:
Kimi K2.5 via NVIDIA NIM (1-trillion-parameter model by Moonshot AI)
Free tier limitations: ~40 RPM rate limit, slower response times (30+ seconds), but maintains agent availability during paid provider outages.
Local models:
Ask bot: "I want to use an Ollama model, which one fits my system specs and supports tool use?"
Note: Only practical on KVM4+ VPS plans with sufficient RAM.
Voice Interaction Setup
Receiving Voice Messages (Speech-to-Text)
Execute: "Enable audio transcription in the settings so I can send voice messages."
Configures OpenAI Whisper for transcription. Restart required.
Sending Voice Replies (Text-to-Speech)
OpenClaw supports three TTS providers:
- ElevenLabs – Highest quality (paid)
- OpenAI TTS – Good quality (paid)
- Edge TTS – Free fallback with 300+ voices in 74 languages
Free option configuration:"Set up Edge TTS for voice responses so you can talk back when I send voice memos."
Restart and test with voice note in Telegram.
Sub-Agents for Parallel Execution
For complex research or multi-step workflows, main agent can spawn sub-agents for simultaneous execution:
"Research these three platforms at the same time: Notion, Zapier, Make.com. For each, find what it does, current pricing, and one major limitation. Use sub-agents to research simultaneously."
Prerequisite: Search tool installation. Brave Search API is widely used – sign up, generate key, add as environment variable in hosting provider, notify bot of addition.
Main agent delegates to sub-agents, aggregates findings, compiles unified report.
System Updates and Recovery
Updates
In Telegram: "Check for updates."
Approve if available, then restart.
Alternative: Hostinger Docker Manager: three dots next to project → Update.
Emergency Procedures
Immediate stop:"Stop all processes right now."
Or: Hostinger three dots → Stop project
Nuclear option:
Revoke API key in provider dashboard (Anthropic Console, OpenAI, etc.)
Rollback:
Restore from daily backups or manual snapshot created before risky modifications.
Best practice: Create snapshot before all major configuration changes.
Frequently Asked Questions
Q: Is coding knowledge required?
A: No. This complete guide uses natural language instructions via chat. The bot handles all technical implementation.
Q: What are monthly costs?
A: VPS: $5–13. API tokens: $5–80 depending on model selection and usage volume. With optimized model routing, most users average $20–40/month total.
Q: Is this secure?
A: Private by default, but powerful access requires proper guardrails. Execute every security step in this guide. For comprehensive risk analysis, read OpenClaw Problems.
Q: Can I use this from mobile devices?
A: Yes – through Telegram, WhatsApp, or any connected messaging platform. No dedicated mobile application exists.
Q: What if configuration breaks?
A: Restore from daily Hostinger backup. This is why auto-backup enablement was recommended during initial setup.
Q: Can this replace Cursor or Claude Code for development?
A: Not directly. OpenClaw is a general-purpose automation agent. For focused coding sessions, use Cursor or Claude Code CLI alongside OpenClaw. They serve complementary functions – OpenClaw handles always-on orchestration, dedicated coding tools handle actual code modifications.
Q: How does this compare to Agent Zero?
A: Agent Zero is another open-source agent framework focused on multi-agent hierarchies with Docker sandboxes. It targets developers and lacks OpenClaw’s messaging platform integrations. Select Agent Zero for orchestrated development workflows; choose OpenClaw for personal automation across communication platforms.
