You've heard the hype. AI agents are everywhere — automating customer support, managing social media accounts, monitoring servers, even trading crypto. But most tutorials make it sound like you need a PhD in machine learning to get started.
You don't. With OpenClaw and OpenAgent.Mom, you can go from zero to a running AI agent in about five minutes. Here's exactly how.
What Is an OpenClaw Agent?
An OpenClaw agent is a self-hosted AI assistant defined by a set of markdown files called a workspace. These files tell the agent who it is, how to behave, what tools to use, and who it works for. Think of it as a personality and instruction set that any compatible AI model (Claude, GPT-4o, Gemini) can load and follow.
The workspace contains seven files:
- IDENTITY.md — Name, creature type, visual identity
- SOUL.md — Core personality, values, communication style
- AGENTS.md — Operating instructions and workflows
- TOOLS.md — API endpoints, SSH hosts, auth methods
- USER.md — Info about the human the agent serves
- HEARTBEAT.md — Periodic background tasks
- MEMORY.md — Long-term memory seed
These files are portable. You can move them between servers, back them up to Git, or share them with your team.
Step 1: Answer the Wizard Questions
Head to OpenAgent.Mom and click Create AI Agent. Our wizard will ask you a series of conversational questions:
- What should this agent do? Describe its purpose in plain English. "Monitor my three websites and alert me on Telegram if any go down" is a perfectly good answer.
- What archetype fits? The wizard will classify your agent as an API/Pipeline Bot, Human-Facing Agent, or Hybrid. You'll confirm.
- Technical details — Which APIs does it call? What platforms does it use? Where should it run?
The whole interview takes about 3-5 minutes. The wizard handles the rest.
Step 2: Download Your Workspace Bundle
Once you confirm the summary, our AI generates all seven workspace files tailored to your exact requirements. You'll get a downloadable ZIP file containing:
workspace-my-agent/
├── IDENTITY.md
├── SOUL.md
├── AGENTS.md
├── TOOLS.md
├── USER.md
├── HEARTBEAT.md
└── MEMORY.md
Each file is pre-filled with real, actionable content — not generic templates. If you told the wizard your agent monitors websites via HTTP checks and alerts on Telegram, that's exactly what you'll find in AGENTS.md and TOOLS.md.
Step 3: Deploy to Your Server
Upload the workspace folder to your VPS or cloud server. If you don't have one, check our Free VPS Guide — we walk you through getting a free cloud server and setting up OpenClaw.
The deployment is straightforward:
# Copy workspace to your server
scp -r workspace-my-agent/ user@your-server:~/.openclaw/
# SSH into your server
ssh user@your-server
# Register the agent with OpenClaw
openclaw agent add --workspace ~/.openclaw/workspace-my-agent/
# Start the agent
openclaw agent start my-agent
That's it. Your agent is now running.
Step 4: Fill In Your Credentials
The workspace files use placeholders like YOUR_API_KEY and YOUR_BOT_TOKEN for security — we never ask for real credentials. Open TOOLS.md and replace the placeholders with your actual values:
## Telegram Bot
- Bot Token: YOUR_TELEGRAM_BOT_TOKEN
- Chat ID: YOUR_TELEGRAM_CHAT_ID
Becomes:
## Telegram Bot
- Bot Token: 7284619384:AAH...actual-token
- Chat ID: -1001234567890
Do the same for any API keys, SSH credentials, or OAuth tokens your agent needs.
Step 5: Test and Iterate
Send your agent a test message. Check the logs. See how it responds. If something isn't right, just edit the workspace files — they're plain markdown. No recompilation, no redeployment needed. Just save the file and the agent picks up the changes.
Common Mistakes
- Forgetting to set the timezone in USER.md. Your agent will schedule tasks in UTC by default, which might mean your "morning briefing" arrives at 3 AM.
- Leaving placeholder credentials. The agent will fail silently on API calls if you forget to replace
YOUR_API_KEYwith the real value. - Making SOUL.md too long. Every token in SOUL.md costs money on every API call. Keep it focused — personality traits, not a novel.
- Skipping HEARTBEAT.md. If your agent needs to check things periodically (server health, price alerts, RSS feeds), heartbeat tasks are how you set that up. An empty heartbeat file means no background monitoring.
Why Self-Hosted?
You might wonder why OpenClaw agents run on your own server instead of in the cloud. Three reasons:
- Privacy. Your agent reads your emails, calendars, and messages. That data stays on your server, not someone else's.
- Control. You choose the AI model, the update schedule, and the resource limits. No vendor lock-in.
- Cost. Running an agent on a $5/month VPS is far cheaper than SaaS agent platforms charging $50-200/month.
Security Guardrails
- Always run OpenClaw behind a firewall. Only expose the ports your agent actually needs (e.g., Telegram webhook on 443).
- Store API keys in environment variables or encrypted config, not directly in workspace files on shared systems.
- Use SSH keys instead of passwords for server access.
- Regularly rotate your agent's API tokens, especially for services with broad permissions.
- Review your agent's MEMORY.md periodically — it accumulates data over time, and you should ensure nothing sensitive is being stored in plain text.
What Can You Build?
The workspace format is flexible enough for almost any agent use case:
- DevOps monitor that checks server health and posts to Slack
- Social media manager that posts to Twitter/X with a consistent persona
- Research assistant that summarizes arxiv papers daily
- Customer support bot that handles FAQ questions on your website
- Personal chief of staff that reads your email and briefs you every morning
Each of these starts the same way: five minutes in the wizard, a ZIP download, and a deploy to your server.
Ready to Build?
Stop reading about AI agents and start building one. The wizard is free to try, and the whole process takes less time than making coffee.
Build Your First Agent Now
Our AI-powered wizard designs your complete agent workspace in minutes. No coding required.