AI Agent

OpenClaw Review & Setup Guide: The AI Assistant with 120K GitHub Stars

In-depth review and setup guide for OpenClaw, the hottest open-source AI assistant of 2025.

OpenClawClaudeChatGPT

# OpenClaw Review & Setup Guide: The AI Assistant with 120K GitHub Stars

If you've been anywhere near the developer Twitterverse in 2025, you've probably seen OpenClaw. The open-source AI assistant project went from zero to 120,000+ GitHub stars in roughly two months — making it one of the fastest-growing repositories in GitHub's history. But what is it, exactly? Is it just hype, or does it actually deliver?

We've been running OpenClaw daily for the past several weeks. This is our honest, in-depth review — plus a complete setup guide so you can try it yourself.

What Is OpenClaw, and Why Did It Explode?

OpenClaw (formerly known as Moltbot, then Clawdbot) is an open-source gateway that connects AI coding agents to your everyday messaging apps — WhatsApp, Telegram, Discord, and iMessage. Created by Peter Steinberger ([@steipete](https://x.com/steipete)), a well-known figure in the iOS and developer tools community, OpenClaw turns your messaging app into a command center for an AI that can read your emails, manage your calendar, execute code, control your browser, and remember everything you tell it.

The tagline on the docs says it all: "Send a message, get an agent response — from your pocket."

Why It Went Viral

Several factors contributed to OpenClaw's meteoric rise:

  1. The "AI in your pocket" promise — Instead of switching to yet another app, OpenClaw meets you where you already are: WhatsApp, Telegram, or Discord.
  2. Truly open source — No cloud lock-in. Your data stays on your machine. The entire codebase is on [GitHub](https://github.com/openclaw/openclaw).
  3. It actually works — This isn't a toy demo. It's a production-grade system with session management, memory, heartbeats, multi-agent routing, and plugin architecture.
  4. Peter Steinberger's credibility — @steipete has a track record of building widely-used developer tools. When he tweets about it, people pay attention.

Reactions on X have been overwhelmingly positive:

> "OpenClaw is the first AI tool that actually replaced a workflow for me. I message it on WhatsApp and it handles my inbox. Wild." — Developer on X

> "120K stars in 2 months isn't hype — it's a paradigm shift in how we interact with AI." — AI researcher

Core Features: What Can OpenClaw Actually Do?

Let's break down the main capabilities. OpenClaw isn't just a chatbot wrapper — it's a full agent platform.

📱 Messaging Integration

OpenClaw bridges multiple messaging platforms simultaneously:

  • WhatsApp — via Baileys (WhatsApp Web protocol). Uses a dedicated second phone number (recommended).
  • Telegram — Bot API via grammY. Supports DMs and group chats with mention-based activation.
  • Discord — Bot API via discord.js. Supports DMs and guild channels.
  • iMessage — Local `imsg` CLI integration (macOS only).
  • Mattermost — Available as a plugin with Bot API + WebSocket support.

You can run all of these simultaneously through a single Gateway process.

📧 Email Management

Through its agent workspace and tool integrations, OpenClaw can check your inbox, summarize unread emails, and draft responses. During heartbeat cycles (configurable proactive checks), it can alert you about urgent messages without you having to ask.

📅 Calendar Integration

Calendar checks are part of OpenClaw's proactive heartbeat system. It can scan upcoming events in the next 24–48 hours and remind you — all through your preferred messaging app.

⏱️ Cron Jobs & Heartbeats

One of OpenClaw's most distinctive features is its heartbeat system. By default, it runs a heartbeat every 30 minutes, checking a `HEARTBEAT.md` file in the workspace for tasks. You can also set up dedicated cron jobs for precise timing — "remind me at 9 AM every Monday" style tasks.

The difference: heartbeats batch multiple checks together (email + calendar + notifications), while cron jobs are isolated, precisely-timed tasks.

🌐 Browser Control

OpenClaw includes a browser control tool that can:

  • Navigate to URLs
  • Take snapshots (accessibility tree or screenshot)
  • Click, type, hover, drag, and interact with web pages
  • Run JavaScript in the page context
  • Manage tabs and profiles

This isn't just "fetch a webpage" — it's full Playwright-powered browser automation, accessible from your phone via a text message.

📁 File Operations & Code Execution

The underlying Pi agent can:

  • Read and write files in the workspace
  • Execute shell commands
  • Edit files with surgical precision
  • Manage git repositories

All from your messaging app. You literally text "commit and push the changes" and it does it.

🧠 Memory System

OpenClaw's memory is refreshingly simple: plain Markdown files.

  • `memory/YYYY-MM-DD.md` — Daily logs (today + yesterday loaded at session start)
  • `MEMORY.md` — Curated long-term memory (only loaded in private sessions for security)

There's also a vector memory search feature that builds a semantic index over your memory files, so the agent can find related notes even when wording differs. It supports OpenAI embeddings, Gemini, or local models.

The pre-compaction memory flush is clever: when a session is about to hit context limits, OpenClaw triggers a silent turn that reminds the agent to write durable memories before the context is compacted.

Installation Guide: macOS, Linux & Windows

Prerequisites

  • Node.js ≥ 22 (required)
  • pnpm (optional, recommended for building from source)
  • A Brave Search API key (recommended for web search capabilities)

macOS / Linux

The fastest path is the install script:

curl -fsSL https://openclaw.bot/install.sh | bash

Or install via npm/pnpm globally:

npm install -g openclaw@latest

# or

pnpm add -g openclaw@latest

Then run the onboarding wizard:

openclaw onboard --install-daemon

The wizard walks you through:

  • Choosing local vs. remote gateway
  • Setting up authentication (API keys or OAuth)
  • Configuring messaging channels
  • Installing the background service (launchd on macOS, systemd on Linux)

Windows (WSL2 Recommended)

OpenClaw strongly recommends WSL2 on Windows. Native Windows is untested and has poorer tool compatibility.

  1. Install WSL2 with Ubuntu:
wsl --install

  1. Inside WSL2, follow the Linux steps:
curl -fsSL https://openclaw.bot/install.sh | bash

openclaw onboard --install-daemon

There's also a PowerShell installer for adventurous users:

iwr -useb https://openclaw.ai/install.ps1 | iex

From Source (Development)

git clone https://github.com/openclaw/openclaw.git

cd openclaw

pnpm install

pnpm ui:build

pnpm build

openclaw onboard --install-daemon

Verify Installation

openclaw status

openclaw health

openclaw security audit --deep

Connecting Telegram

  1. Create a bot via [@BotFather](https://t.me/botfather) on Telegram and get your bot token.
  2. During `openclaw onboard`, select Telegram and enter the token — or configure it manually in `~/.openclaw/openclaw.json`.
  3. Start the gateway: `openclaw gateway`
  4. Send a DM to your bot. You'll receive a pairing code on first contact.
  5. Approve it:
openclaw pairing list telegram

openclaw pairing approve telegram

Group chat tip: By default, the bot only responds when mentioned. The owner can toggle this with `/activation always|mention`.

Connecting WhatsApp

This is the setup that got everyone excited — AI in WhatsApp.

  1. Get a second phone number (SIM, eSIM, or prepaid). Don't link your personal WhatsApp — every message would become agent input.
  2. Run the QR login:
openclaw channels login

  1. Scan the QR code with WhatsApp → Settings → Linked Devices on the assistant phone.
  2. Configure allowed senders in `~/.openclaw/openclaw.json`:
{

"channels": {

"whatsapp": {

"allowFrom": ["+15555550123"]

}

}

}

  1. Message the assistant number from your allowlisted phone. Done!

Real-World Usage Experience

We've been using OpenClaw as our daily assistant for several weeks. Here's what stood out:

What We Love

  • The "always there" factor. Having an AI agent in your existing messaging app is transformative. No context switching, no opening a separate app. You just... text it.
  • Memory actually works. The Markdown-based memory system is simple but effective. We told it our project deadlines once, and it remembered them across sessions.
  • Browser control from mobile. Texting "check the status of our deployment dashboard" and getting back a screenshot with analysis feels like the future.
  • Heartbeats are brilliant. Proactive email and calendar checks mean it often tells us about important things before we think to ask.
  • Self-hosted = peace of mind. All data stays on our machine. Session files, memory, credentials — everything local.

What Could Be Better

  • Setup isn't trivial. You need Node 22+, a dedicated phone number for WhatsApp, API keys, and comfort with the terminal. This is not a "download and go" consumer app.
  • API costs add up. Since you bring your own API key, heavy usage with Claude Opus 4.5 can get expensive (see Pricing below).
  • WhatsApp quirks. The Baileys library occasionally has connection drops. It reconnects automatically, but it's noticeable.
  • Windows is second-class. WSL2 works, but native Windows support is minimal. macOS and Linux are clearly the primary targets.

Pricing Analysis

OpenClaw itself is free and open-source. However, it requires an AI provider API key to function:

API Key Options

ProviderAuth MethodNotes
Anthropic (Claude)API key (recommended)Best experience with Claude Opus 4.5 or Sonnet
OpenAIOAuth or API keySupported via OpenAI Codex subscription

Estimated Monthly Costs

Your costs depend entirely on usage. Here's our rough breakdown:

Usage LevelModelEst. Monthly Cost
Light (10-20 msgs/day)Claude Sonnet$5–15
Moderate (30-50 msgs/day)Claude Sonnet$15–40
Heavy (50+ msgs/day, with heartbeats)Claude Opus 4.5$50–150+
Power user (coding + browser + heartbeats)Claude Opus 4.5$100–300+

Tips to reduce costs:

  • Use Claude Sonnet instead of Opus for routine tasks
  • Set heartbeat interval to 60 minutes or disable when not needed
  • Use `/compact` to compress session context
  • Configure session auto-reset (daily or after idle periods)

Other Costs

  • Brave Search API: Free tier available; paid plans for heavy use
  • Dedicated phone number (for WhatsApp): ~$3–10/month for a prepaid SIM
  • Server (optional): Free if running on your own machine; ~$5–20/month for a VPS

OpenClaw vs ChatGPT vs Claude Desktop

FeatureOpenClawChatGPT (Plus/Pro)Claude Desktop (Pro/Max)
PriceFree (BYOK)$20–200/mo$20–100/mo
Open Source✅ Yes❌ No❌ No
Data Privacy✅ Fully local❌ Cloud❌ Cloud
WhatsApp Integration✅ Native❌ No❌ No
Telegram Integration✅ Native❌ No❌ No
Discord Integration✅ Native❌ No❌ No
Browser Control✅ Full automation❌ No✅ Limited (computer use)
Code Execution✅ Full shell access✅ Sandboxed✅ Sandboxed
File System Access✅ Full❌ Limited✅ Local files
Persistent Memory✅ Markdown + Vector✅ Built-in✅ Project memory
Proactive (Heartbeats)✅ Configurable❌ No❌ No
Cron Jobs✅ Yes❌ No❌ No
Multi-Agent Routing✅ Yes❌ No❌ No
Custom Persona✅ SOUL.md❌ Limited (GPTs)❌ System prompt
Setup Difficulty🔧 Medium–High✅ Easy✅ Easy
Mobile Access✅ Via messaging apps✅ Native app✅ Native app

The key differentiator: OpenClaw is the only option that puts a full-powered AI agent in your existing messaging apps with complete data sovereignty. ChatGPT and Claude Desktop are easier to set up but locked to their own interfaces and cloud infrastructure.

Who Is OpenClaw For?

✅ Perfect For

  • Developers and power users who want an AI agent integrated into their daily messaging workflow
  • Privacy-conscious users who want all data to stay on their own hardware
  • Tinkerers and customizers who love configuring, scripting, and extending tools
  • Remote workers who want proactive email/calendar management via their phone
  • Teams that want a shared AI assistant in their Discord/Mattermost channels

❌ Not Ideal For

  • Non-technical users — Setup requires terminal comfort and understanding of API keys
  • Cost-sensitive users — API costs for heavy usage with Opus-class models can add up
  • iPhone-only users who want native iOS app experience (there's an iOS node, but it's a companion, not a standalone app)
  • Users wanting a "just works" consumer product — This is a power tool, not a polished consumer app

FAQ

1. Is OpenClaw truly free?

The software is 100% free and open-source. However, you need to bring your own AI provider API key (Anthropic or OpenAI), which has usage-based costs. Think of it like a self-hosted email client — the software is free, but you need an email provider.

2. Can I use OpenClaw without WhatsApp?

Absolutely. You can use it with Telegram, Discord, iMessage, Mattermost (via plugin), or even just the built-in web dashboard at `http://127.0.0.1:18789/`. WhatsApp is popular but completely optional.

3. Is my data safe? Can anyone else see my messages?

All data is stored locally on your machine — session files, memory, credentials, everything. OpenClaw runs on your hardware with a loopback-first network model (WebSocket defaults to `127.0.0.1`). API calls go to your chosen provider (Anthropic/OpenAI), so standard provider privacy policies apply to the content of your prompts.

4. Can I run OpenClaw on a VPS/server?

Yes! Many users run it on a headless Linux server or VPS. Use `openclaw onboard --install-daemon` to set it up as a systemd service. For remote access, use an SSH tunnel or Tailscale. See the official docs on [Remote access](https://docs.openclaw.ai/gateway/remote).

5. How does OpenClaw compare to running Claude Code locally?

OpenClaw actually uses Pi (a coding agent) under the hood and bridges it to your messaging apps. Claude Code (now Pi) is the agent engine; OpenClaw is the gateway layer that adds messaging integration, heartbeats, memory management, multi-agent routing, and persistent sessions on top. They're complementary, not competing.

Conclusion

OpenClaw is one of those rare projects that earns its hype. The 120K GitHub stars aren't just vanity metrics — they reflect genuine enthusiasm from developers who've been waiting for exactly this: an open-source, self-hosted AI assistant that lives in your existing messaging apps.

Is it perfect? No. The setup has a learning curve, API costs require management, and Windows support is still catching up. But if you're a developer or power user who values privacy, customization, and the convenience of texting an AI from WhatsApp or Telegram, OpenClaw is in a category of one.

The heartbeat system alone — having your AI proactively check your email and calendar and reach out when something's important — changes the dynamic from "tool you use" to "assistant that helps." And the Markdown-based memory system is both elegantly simple and surprisingly effective.

Our verdict: 9/10. A genuinely transformative tool for technical users. The setup barrier is the main thing keeping it from being a 10.

Get started: [https://docs.openclaw.ai/start/getting-started](https://docs.openclaw.ai/start/getting-started)

GitHub: [https://github.com/openclaw/openclaw](https://github.com/openclaw/openclaw)

---

This review is based on our hands-on experience running OpenClaw in production. We are not affiliated with the OpenClaw project. Reviewed January 2026.

Discover More AI Tools

Browse our AI tools directory to find the perfect tool for your needs.

Browse Tools