OpenClaw has been doing the rounds — personal AI agent framework, runs locally, hooks into Telegram and WhatsApp, wraps an external LLM (I ran Claude Sonnet), keeps state in a stack of markdown files: SOUL.md, MEMORY.md, USER.md, HEARTBEAT.md. The concept is genuinely impressive, and the viral response is earned. I ran it for a few days to see what it actually delivers. Source on GitHub.
What it is
At its core, OpenClaw is scaffolding. It gives an LLM a persistent identity, a memory layer, and a way to reach into the world through messaging and integrations. The markdown files aren't just configuration — they're the agent's character and context, updated over time. The heartbeat tasks let it check in on things without you asking. Done well, it's close to the JARVIS moment people are calling it.
I can see why it catches people. It's a real thing, not vapourware.
What it actually costs
Here is where I part ways with most of the coverage.
The pitch is "runs locally, your data, no subscription." That's technically accurate and practically incomplete. The full stack looks like this: an always-on machine — VPS or home server, which you're either paying for or already have; API costs that mount faster than you'd expect, because every heartbeat task and every memory update burns tokens; Zapier at a premium tier if you want the automation integrations that make it useful; and several of the more interesting MCP integrations sitting behind their own paid tiers.
None of that is hidden exactly, but it doesn't feature prominently in the demos. The token burn is the one that surprised me most. Heartbeat tasks run on a schedule whether you're watching or not. Memory consolidation, context refreshes, ambient checks — it adds up. You're not paying a subscription, but you're running a token furnace.
The risk picture
Real, but manageable with common sense.
Don't give it access to anything you wouldn't hand to a capable but unpredictable junior. That framing does most of the work. Start read-only. Add write access incrementally, once you've watched the behaviour under real conditions. Keep logs you can actually audit. Don't connect production anything until you trust it.
That's not a counsel of fear — it's just sensible tool adoption. The same caution applies to any system that acts on your behalf.
Who it's actually for
People who already have the infrastructure appetite. Comfortable with the command line, have an API budget that won't give them pause, run a home server or VPS already. For that person, the costs are already half-covered, the setup friction is low, and the reward is proportionate. It genuinely delivers.
For someone coming in cold — setting up a server for the first time, watching API spend for the first time, signing up for Zapier for the first time — the total cost of ownership is higher than it looks from the demos.
What I did instead
I built a lean CLAUDE.md framework. Personal context, behavioural contract, memory index — all in a single auditable file that loads into every Claude session. No always-on machine beyond the Dell 3040 I already run, no token furnace, no premium connectors. It covers most of what I wanted from an agent setup without the infrastructure overhead.
That's a personal trade-off, not a verdict on OpenClaw. My setup doesn't do autonomous heartbeat tasks or ambient monitoring. If that's the thing you want — and it is a compelling thing — then CLAUDE.md won't get you there.
Worth trying?
Yes, with open eyes. Know what it costs before you're three weeks in. Start small, read-only, with an API key you're watching. If you have the infrastructure appetite and the budget, it might well be the right tool. Just make sure you've read the full invoice before you sign up.
