OpenClaw: The AI Agent That Actually Does Stuff - Part 1

Let me be honest with you before we get into anything.

I’ve been exploring developer tools for a while now and I've gotten pretty good at spotting how the hype cycles work. Something new drops and GitHub, Twitter trends it, and then everyone starts moving on to it. I assumed OpenClaw — or Clawdbot, or Moltbot, whatever name you saw it under — was going to be exactly like that.

Then I actually sat down, researched it, installed it and spent a proper week using it as a part of my daily workflow.

And here we are.

This blog is not just going to be a list of features. I want you to actually understand what OpenClaw is doing differently, how it works, what you can do with it, and what you should know if you’re just getting started with AI agents. By the end, you’ll have enough knowledge to make a decision about whether this actually matters.

Let’s begin.

The Name Story (As It Changed Three Times)

If you’ve seen Clawdbot, Moltbot, and OpenClaw and thought they were different projects, they’re not. It’s the same project, just renamed over time.

In November 2025, Austrian developer Peter Steinberger built it as a small weekend experiment and called it Clawdbot, a playful nod to Claude, with a lobster mascot to match. He open sourced it and didn’t expect much.

In January 2026, it suddenly blew up, gaining around 60,000 GitHub stars in just a few days. Soon after, Anthropic raised a trademark concern because “Clawdbot” sounded too close to “Claude.”

On January 27, it was renamed Moltbot, keeping the lobster theme. A few days later, the community voted and the final name became OpenClaw, which better reflects what it actually is.

The current name is OpenClaw. Any tutorial mentioning Clawdbot or Moltbot is referring to the same project.

What Is OpenClaw?

Currently, most of the AI tools work like chatboxes. You open the tab, type a prompt, get the response and then manually select what you need and where you’re actually doing your work. The AI lives on someone’s server, and you’re the one who connects its output to the real environment.

OpenClaw takes a completely different approach.

It’s a free, open-source AI agent you run yourself. Once you set it up, it lives on a machine you control — your laptop, desktop, a cloud VPS, even a Raspberry Pi 4. Once it’s installed and working, you communicate with it through the texting apps you use everyday like WhatsApp, Telegram, Slack, Discord, Signal, iMessage, Microsoft Teams, Google Chat, Matrix, anyone of your choice as it supports all of them.

Something that distinguishes it, is that it doesn’t only reply with text. It actually does things. It can browse the web, read and write files on your machine, run terminal commands, manage your calendar, draft and send emails, interact with GitHub, fill out forms, and combine all of that together in multi-step workflows that run on their own without manual intervention.

In Steinberger’s words, it’s “AI that actually does things” — which differentiates it from tools that only explain how to do things.

Most importantly, your data never leaves your machine until you explicitly allow it to send somewhere. There’s no hidden policy change that suddenly changes how your conversations are handled. Your files, your history, your memory, all of these are stored locally in simple Markdown and YAML files that you can open in any text editor.

It’s all in your machine, your data, your system.

How It Actually Works

This is the most important section, that helps you understand its architecture — why it can do what it does, why security matters, and why it’s built the way it is. So instead of rushing, let’s break it down in a clear, simple way.

OpenClaw works through three main parts that work together.

The Gateway — The Control Plane

The Gateway is a Node.js daemon running constantly in the background, bound to localhost only by default. It stays connected to all your messaging channels, sends each message to the right agent session, and handles requests one at a time for each session, in the exact order they arrive.

That detail is more important than it might seem. By handling requests serially, the system avoids race conditions, where multiple tasks running at the same time might conflict over the same files or shared state.

In addition to handling messages, the system also triggers a heartbeat every 30 minutes by default, or every hour if you're using Anthropic OAuth. This heartbeat allows the agent to check for any scheduled tasks, and perform monitoring on its own, even if you haven’t asked it anything recently.

Agent Runtime — The Thinking Loop

The Agent Runtime is the AI loop.

When a message arrives, the system first loads the session history and any long-term memory saved on disk as plain .md files, so it genuinely remembers what you told it last week. It then adds only the skills that are actually relevant to your current request, instead of loading every installed skill and slowing things down.

After that, everything is sent to the AI model you have chosen, whether that is Claude, GPT-4o, DeepSeek, or a local model.

If the model decides it needs to take an action, it sends back a tool call instead of a normal text reply. The system runs that tool, collects the result, and gives it back to the model. The model then decides if it has enough information or if it needs to take another step.

This process continues until the model reaches a final answer, which is then streamed back to you.

Skills — The Extension System

OpenClaw comes with several built-in tools. It can control a real browser, which means it can actually click buttons, fill out forms, log in to websites, and interact with pages like a human. It can also read and write files, run shell commands, and handle scheduled jobs.

On top of these tools, there is ClawHub, which is basically a shared community library of skills created by other users. It includes integrations for tools like Todoist, GitHub, Spotify, Obsidian, Home Assistant, Gmail, Google Calendar, Linear, and many others.

That said, ClawHub is community-contributed and lightly vetted — more on this in the security section below.

Skills themselves are simple. Each one is mainly a SKILL.md documentation file, sometimes it includes an optional install script. The agent reads the documentation to understand what the skill can do, similar to onboarding a new teammate by giving them clear written instructions, instead of making them go through code to figure things out.

Another important detail is that the skill format OpenClaw also works with the AgentSkills spec, an open standard adopted by Claude Code, Cursor, VS Code, GitHub Copilot, and others. So you are not limited to just the skills available on ClawHub. It connects to a much larger ecosystem, giving you access to many more existing skills.

What You Can Actually Build With It

Here are some workflows developers are actually running:

Repo management from your phone. It pushes to branches, check test results, review recent commits, from anywhere without your laptop. If you have ever been traveling or commuting when something urgent happened in a repo, you already understand how useful this is.

Overnight autonomous coding loops. At the end of the day, you describe what needs to be done, for example, refactor the auth module, write tests, and open a PR. By morning, the pull request is ready, along with the agent’s reasoning written in the comments. The documentation recommends using Claude for more complex, multi-step coding tasks because it handles reasoning better and is more resistant to prompt injection. Sonnet 4.6 is suggested when you want to manage costs, and Opus 4.6 when you need stronger performance.

Proactive information briefings. You can connect skills to sources like GitHub issues, Hacker News, subreddits, or RSS feeds and track keywords related to your work. The agent filters the content, summarizes what matters, and sends you a digest at whatever schedule you choose. This works through the heartbeat system, so it runs automatically without you having to trigger it each time.

Voice notes into structured notes. Send a voice message through Telegram, and the agent will transcribe it, pull out the key points, and save it to any tool you prefer. This process takes about 15 seconds.

Why It Matters Even If You’re Just Starting Out

Let me be honest about this. OpenClaw is not beginner friendly. You need Node.js v22 or higher, you should be comfortable using the terminal, and you need some basic understanding of networking. The documentation clearly says that if you are not confident with command line tools, this is not something you should run casually. That is not gatekeeping, it is just being realistic about the risks.

That said, it is still worth learning about early in your AI journey.

One big reason is transparency. OpenClaw is MIT licensed and fully open. You can read the code yourself. You can see how the Gateway handles and queues requests. You can inspect how skills are discovered and loaded. You can open the memory files on disk and see exactly what is stored. You can even look at how the system prompt is constructed before every LLM call. Here, nothing is a black box unless you choose not to look.

That level of visibility helps you build a clear mental model of how agent systems actually work. You start to understand the moving parts, how memory is managed, how tools are selected, how decisions flow from one step to the next. And that understanding is not limited to this one project. As AI agents become more common in real software workflows, having that foundation will matter.

If the terminal still feels intimidating, that is fine. Save it for later and revisit it when you feel more comfortable. The setup process will likely improve over time. But even before you run it yourself, the concepts behind it are worth understanding.

Security: The Non-Negotiable Part

OpenClaw has wide access. It can read and write files, run shell commands, connect to messaging apps, check your calendar, and much more. But that level of access means you need to be careful with how you set it up, thus security is not optional here.

Network access: By default, the Gateway only binds to localhost, which is good. If you want to access it in your phone, use an SSH tunnel or Tailscale, which the project recommends. Do not expose port 18789 directly to the public internet. That is asking for trouble.

Authentication setup: The auth: none option was permanently removed in version 2026.1.29 after a real vulnerability was discovered. Crafted links could redirect your auth token to an attacker’s server, and the WebSocket server was not validating Origin headers properly.

If you see any guide that still shows this:

# Removed — do not use

auth: none

# Use one of these instead

auth: token    # openclaw gateway token
auth: password # OPENCLAW_GATEWAY_PASSWORD=yourpassword

Update immediately if you are running an older version. Do not continue using outdated configs.

ClawHub skills: These are contributed by the community and are only lightly vetted. Before installing anything, read the SKILL.md file and any install.sh script. It just takes two minutes.

Prompt injection risks: The system prompt guardrails are helpful, but they are not hard security boundaries. Real protection comes from locking down your inbound channels. Use allowlists where possible. Enable mention gating in group chats. Treat links and file attachments from unknown sources as potentially malicious.

Run openclaw doctor regularly: There is a built in diagnostic command called openclaw doctor. Run it from time to time. It helps surface configuration mistakes early, before they turn into bigger security issues.

Getting Started

What you need before installing:

• Node.js v22+ (node --version)
• Terminal comfort (WSL2 on Windows — native Windows not supported)
• API key for your model (Claude recommended; GPT-4o or DeepSeek work too)
• Ideally a separate machine or cheap VPS (2GB RAM minimum, ~$4–5/month on Hetzner or DigitalOcean)

Install:

npm install -g openclaw@latest
openclaw onboard --install-daemon

The --install-daemon flag installs the Gateway as a proper system service. On macOS it uses launchd, and on Linux it uses systemd. That means it will automatically start when your machine boots up. Do not skip this step, otherwise you will have to manually start it every time.

The setup wizard guides you through the whole process. It helps you configure authentication, initialize your workspace, connect your first messaging channel, and install your first skill.

If you are just getting started, use Telegram as your first channel. It is the simplest to set up. WhatsApp is supported too, but the linking process is more involved and can be a bit tricky the first time.

Recommended model config:

models:
  default: claude-sonnet-4-6    # good balance of capability and cost
  fallback: gpt-4o
  # For complex autonomous tasks: claude-opus-4-6

Then run:

openclaw doctor

After you finish the setup, run this once. And make it a habit to run it again anytime you change the configuration.

In the beginning, keep things simple. Start with one clear workflow, maybe a Telegram research assistant or a basic morning task manager. Use it for a while and understand how it responds, how it uses tools, and how it handles memory.

Once you feel confident about how it behaves, then slowly expand its access and add more capabilities.

Where It's Headed

On February 14, 2026, Steinberger announced that he is joining OpenAI and moving OpenClaw under an open source foundation. It will remain independent from any single company, stay MIT licensed, and operate with proper governance. The codebase is not going closed. It remains fully open.

For something that is only a few months old, that kind of direction is rare. This does not look like a weekend side project that will fade away quietly. The core ideas behind it, being local first, model agnostic, messaging native, truly agent driven, and fully open, are closely aligned with where modern developer tools are heading.

Even if you are not planning to install it right now, it is worth understanding what it represents and how it works.

Resources

• GitHub + docs: github.com/openclaw/openclaw
• Official site: clawd.bot
• Security details: docs.openclaw.ai/gateway/security
• Community Discord: discord.gg/openclaw
• Health check: openclaw doctor

For such articles and developer content visit: https://vickybytes.com