My OpenClaw setup that finally works (Complete Walkthrough)
March 19, 2026
AI Summary
5 min readMoritz Kram shares a 10-step guide to setting up OpenClaw, an open-source personal AI agent that runs locally, remembers interactions, uses tools, and acts proactively via features like heartbeat timers and cron jobs. Unlike cloud-based ChatGPT, which is mainly a chat interface, or local Claude Code/Cowork, which excels at file access for coding and has a nicer UI, OpenClaw integrates with apps like Telegram and offers more built-in autonomy. The episode details fixes for common issues like errors, forgetting, and unreliability, turning it into a reliable "digital employee" for tasks beyond coding, such as marketing.
Establishing a Reliable Baseline
Start with a troubleshooting project in Claude's desktop app or ChatGPT's projects feature. Upload OpenClaw documentation from context7.com—a compressed, up-to-date version—to ensure accurate fixes for errors like Telegram pairing. This prevents hallucinations or irrelevant Reddit suggestions by forcing the model to reference docs first.
Next, personalize via the workspace folder (opened in Cursor or any editor). Key files include agents.md (behavior), soul.md (personality), identity.md, and user.md (your info). Dump context here or chat to build it over time; instruct OpenClaw to update them when patterns emerge. These load by default in sessions, making outputs feel tailored—like you—without constant re-prompting.
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
What you'll learn
- 1 (00:00) **Episode Intro** - Host previews tactical OpenClaw setup from install to production as a digital employee
- 2 (01:15) **Guest Overview** - Moritz outlines episode value: 10 steps to optimize OpenClaw into superhuman employee plus real use cases
- 3 (02:23) **What is OpenClaw** - Personal proactive agent with memory, tools, skills, and chat app integration
- 4 (03:15) **OpenClaw vs ChatGPT** - ChatGPT is cloud-based chat with added memory/tools; lacks local file access and proactivity
- 5 (04:14) **OpenClaw vs Claude Code** - Both local with memory/tools/files; OpenClaw adds chat apps, built-in tools, heartbeat (30-min checks), and crons
- 6 (07:43) **OpenClaw vs Claude Cowork** - Cowork is nicer UI on Code; Anthropic adding OpenClaw-like features (e.g., Dispatch for phone access)
- 7 (11:03) **10-Step Optimized Setup Intro** - Basic install easy but usage breaks; these steps fix errors and boost reliability
+ Full timestamped outline available in the app
Show Notes
I sit down with Moritz Kremb, an OpenClaw power user and agency builder based in Berlin, to break down how to actually make OpenClaw useful. Moritz walks through a 10-step optimization guide covering everything from troubleshooting and memory management to model selection and security basics. He then demos two real systems he built with OpenClaw: a full short-form video content pipeline and a conversational CRM. This episode is for anyone who tried OpenClaw, hit a wall, and wants a clear path to turning it into a superhuman digital employee.
Timestamps
00:00 – Intro and episode promise
02:17 – What is OpenClaw
03:17 – OpenClaw vs. ChatGPT vs. Claude Code
07:43 – Where Claude Cowork and Dispatch fit in
09:47 – Why choose OpenClaw over Cowork
11:03 – Step 1: Setting up OpenClaw
14:46 – Step 2: Personalize your workspace files
18:04 – Step 3: Fix and optimize memory
22:43 – Step 4: Choose the right model (OAuth method)
25:56 – Anthropic ban and model provider gray areas
27:33 – Step 5: Organize Telegram groups and topics
30:19 – Step 6: Understand the three browser modes
35:18 – Step 7: Skills — built-in, marketplace, and custom
39:03 – Step 8: Optimize the heartbeat file
42:00 – Step 9: Security basics and prompt injection
48:08 – Step 10: Least access principle and agent-owned accounts
49:52 – Use case 1: No AI Slop content system
58:37 – Use case 2: Conversational CRM
01:01:15 – Final thoughts on the future of personal agents
01:02:55 – Jensen Huang's take: OpenClaw as the new computer
Key Points
Upload the OpenClaw documentation into a Claude project to create a dedicated troubleshooting baseline — it solves roughly 99% of setup issues.
Use the OAuth method (your existing $20 ChatGPT or Anthropic subscription) to avoid expensive API costs, and always configure backup models.
Memory problems are almost always caused by memory never being saved in the first place; add an auto-save instruction to the heartbeat file so it logs every 30 minutes.
Organize your OpenClaw conversations into separate Telegram groups and topics with group-specific system prompts to avoid context bleed.
More from this podcast
The Startup Ideas Podcast →