The History of OpenClaw: From Moltbot to Open Source AI Revolution
The History of OpenClaw: From Moltbot to Open Source AI Revolution
OpenClaw didn't start as OpenClaw. The project went through several transformations before becoming the open-source AI assistant we know today.
Timeline
December 2025 — Moltbot
The project first appeared under the name Moltbot. The core concept was already there: a personal AI assistant with access to real tools and the ability to take actions on your behalf.
January 2026 — Clawdbot
Rebranding to Clawdbot brought increased popularity. The r/clawdbot subreddit grew rapidly, now boasting 14,800+ subscribers.
Late January 2026 — OpenClaw
The final rebrand to OpenClaw coincided with the official open source release. The r/openclaw community has already reached 9,300+ subscribers.
Why OpenClaw Is Different
As one popular post (300+ upvotes) noted:
"The fact that OpenClaw is fully open source and self hosted is what makes it different from every other AI assistant. Your machine, your rules. No cloud dependency, no data leaving your device."
Core Philosophy
- Self-hosted — Everything runs on your hardware
- Open Source — Full control over the code
- Privacy-first — Data stays local
- Extensible — Skills and plugins for any use case
Community Growth
| Platform | Subscribers |
|---|---|
| r/clawdbot | 14,800+ |
| r/openclaw | 9,300+ |
| r/moltbot | 3,000+ |
| Discord | 5,000+ |
The rapid growth across multiple platforms demonstrates the demand for truly personal, private AI assistants.
OpenClaw continues to evolve with contributions from its growing community.
👀 See Also
Apple Using Google Gemini Access for On-Device AI Model Distillation
Apple has full access to Google's Gemini model for distillation, creating smaller on-device AI models for Siri and other features in iOS 27 without internet connectivity.
Claude-Code v2.1.41 Release: Key Updates and Fixes
Claude-Code v2.1.41 introduces AWS auth refresh enhancements, Windows ARM64 support, and fixes to various tools and UI elements.
The Orchestrator: Why Intent Should Outlive the Process
Current agent stacks invert identity and surface — the orchestrated layer should sit between agents and runtimes, with identity, routing, handoff primitives, and cross-driver calls. Practical example: triaging a flaky test across Ollama, Gemini CLI, and Grok Build under one intent.
Samsung Workers Demand Share of AI Chip Profits — What Developers Need to Know
Samsung's labor deal sets a precedent: 10.5% of operating profit from the semiconductor division goes to bonuses. A broader movement of workers across AI supply chains demanding a share of record profits.