Beginner Survival Guide: Your First 14 Days
The critical first 72 hours, common pitfalls that make people quit, and a day-by-day roadmap to going from confused to confident.
623 upvotes. 265 comments. 'I almost gave up on OpenClaw.' That Reddit post resonated because the first week is genuinely hard. This guide distills lessons from thousands of community members into a structured 14-day plan β so you don't have to learn everything the hard way.
Phase 1: First 72 Hours (Critical)
These three days determine whether you'll love OpenClaw or abandon it. Get these right.
- Install via one-liner: npx openclaw@latest
- Verify gateway is running: openclaw status
- Set a strong gateway password (not the default!)
- Connect your first messaging channel (Telegram recommended)
- Send 'hello' and confirm the agent responds
- Write your SOUL.md β who is your agent? What tone should it use?
- Create memory.md with your top 20 facts (name, timezone, preferences)
- Set up AGENTS.md with a simple role definition
- Test: ask your agent something personal and verify it remembers
- Pick ONE simple automation (daily weather, news summary, or reminder)
- Set up a cron job in TOOLS.md
- Verify it runs at the scheduled time
- Don't try to automate everything yet β this is your 'hello world'
Phase 2: Days 4-7 (Foundation)
Security hardening
Bind gateway to localhost only (127.0.0.1). Set up Tailscale or Cloudflare Tunnel for remote access. Never expose port 18789 to the internet.
Model configuration
Use tiered models: Haiku/Gemini Flash for heartbeats and simple tasks, Sonnet for core operations, Opus only for critical decisions. This saves 40K+ tokens/day.
Install 2-3 skills
Start with well-tested community skills. Check install counts and reviews. Never use 'latest' β pin versions.
Backup your config
Git-track your .openclaw/ directory. One bad config change can brick your setup. 'openclaw backup' saves everything.
Phase 3: Days 8-14 (Confidence)
Add browsing capabilities
Enable web browsing with starting URL constraints. Test with price monitoring or news tracking. Always give a specific URL β never let it browse freely.
Multi-channel setup
Add a second messaging channel. Create separate notification channels vs. interactive channels.
Memory optimization
Review what's in memory.md β is it cluttered? Move structured facts to SQLite. Keep memory.md for identity and critical preferences only.
Join the community
r/openclaw, r/better_claw, Discord. Ask questions. Share what works. The community is helpful and active.
The 7 Deadly Mistakes
Essential Guardrails
- Set daily token spending limits per API provider
- Enable auto-approve only for read-only operations
- Lock SOUL.md and AGENTS.md as read-only at runtime
- Never grant sudo access to agents
- Create separate workspaces for testing vs. production
- Review tool call logs weekly for unexpected patterns
Cost Expectations
Minimal
$5-15
Local models (Ollama) for heartbeats + Haiku for basic tasks
Standard
$30-60
Tiered API models with spending limits. Most users land here.
Power User
$100-200
Opus for everything, heavy browsing, 24/7 cron jobs