OpenClaw Turns One: 5 Things Nobody Saw Coming

On November 24, 2025 a developer pushed the first commit of a small side project called Clawdbot. One year later it is called OpenClaw and has hundreds of thousands of GitHub stars. Few people expected that.
Here are five things from the first year that almost nobody predicted.
1. It outran almost every project on GitHub
OpenClaw passed 100,000 GitHub stars in roughly two months. Most popular frameworks took years to get there. The idea was simple: an AI assistant that runs on your machine and takes instructions from the chat apps you already use, like WhatsApp, Telegram, Slack and Discord.
People did not need another chatbot tab. They wanted an assistant that lives where they already talk.
2. It changed its name twice in a few weeks
Clawdbot became Moltbot, and Moltbot became OpenClaw, all within its first few months. Most projects would struggle to survive one rename. This one grew through two.
3. Its creator joined OpenAI, and the project became a foundation
In February 2026, creator Peter Steinberger announced he was joining OpenAI and moving OpenClaw to an independent foundation. Many people assumed that would be the end of it. Instead the release cadence sped up. In November alone there were several releases a week.
4. 40,000 instances were left open to the internet
Early versions bound the gateway to every network interface by default. Security researchers found more than 40,000 OpenClaw instances exposed to the public internet, and thousands of them were vulnerable to remote code execution. The project responded by making authentication mandatory, and security became its top priority for the rest of the year.
We wrote a full checklist on this: Is your OpenClaw one of the 40,000?
5. It ended up in your pocket
At the end of June, OpenClaw shipped official iOS and Android apps. There is one catch, which we cover in The OpenClaw phone app has one big catch.
What year two probably looks like
The pattern from year one is clear:
- Fast, frequent releases. Staying current is part of running OpenClaw.
- Stricter requirements. One recent example: newer Node.js versions are now mandatory.
- More security, less "just expose the port".
Running OpenClaw yourself is very doable. It is also clearly turning into a job. If you would rather skip that part, that is exactly what ClawNest is for: your own private OpenClaw, hosted in Sweden and kept up to date for you.
Happy birthday, OpenClaw. 🦞