OpenClaw now has a Wikipedia article. For a project that went viral in late January 2026, getting encyclopaedia coverage within weeks is genuinely fast — most open source projects wait years if they get it at all. The existence of the page is itself a signal worth noting. The content, reviewed fresh this week, is mostly accurate but has some interesting gaps and at least one framing choice that deserves examination.
Why the Wikipedia Page Matters
Wikipedia notability requirements are strict. An article needs to demonstrate that the subject has received “significant coverage in reliable sources that are independent of the subject.” Editors actively delete articles about projects that don’t meet this bar.
The fact that OpenClaw has a stable, well-referenced page means the editorial community has judged that it’s received sufficient independent coverage in reliable publications. Looking at the citations, that’s clearly satisfied: TechCrunch, CNBC, WIRED, Axios, Platformer, PCMag, IBM Think, and NDTV are all cited. That’s a credible list.
The page was created recently — it still carries a “Last edited: 7 hours ago” marker as of this writing — but has already accumulated a reasonable amount of content and citations. It’s not a stub. It’s a real article with a structure, an infobox, and referenced claims.
For the project’s long-term legitimacy, this matters. Wikipedia serves as a reputational anchor. It’s where journalists, potential users, and researchers go to establish basic facts about something they’ve heard about. Having an accurate, well-maintained article there is valuable infrastructure.
What the Wikipedia Article Gets Right
The name history
The article handles the name changes well: Clawdbot → Moltbot → OpenClaw, with accurate reasons for each change. The Anthropic trademark complaint triggering the first rename is cited to reliable sources (TechCrunch, CNBC). The “Moltbot never quite rolled off the tongue” explanation for the second rename is correctly attributed.
It also correctly notes the lobster theme throughout the naming — a detail that casual coverage often misses.
The technical basics
The infobox is accurate: initial release November 2025, written in TypeScript and Swift, MIT licence, cross-platform, developed by Peter Steinberger. The categorisation as an “Autonomous personal assistant” is reasonable.
The description of how it works is technically sound: “an autonomous agent that can execute tasks via large language models, using messaging platforms as its main user interface.” That captures the essence without being misleading.
The Moltbook connection
The article correctly links OpenClaw’s viral growth to Moltbook — Matt Schlicht’s AI-only social network that launched alongside the first rebrand. This is important context that some coverage skips. OpenClaw’s growth wasn’t just organic word-of-mouth; Moltbook’s viral moment pulled huge attention towards the framework.
The security and privacy section
The security section is brief but accurate. It correctly identifies: misconfigured permissions as the primary access control risk, prompt injection as the primary data integrity risk, third-party skills as the primary supply chain risk, and the general complexity of the security surface.
The Cisco citation is correctly used — it references the documented case of a third-party skill performing data exfiltration. The quote from OpenClaw’s own maintainer “Shadow” — “if you can’t understand how to run a command line, this is far too dangerous of a project for you to use safely” — is appropriately included and correctly sourced to the Discord channel via TechCrunch.
The GitHub numbers
“Over 145,000 stars and 20,000 forks on GitHub” is accurate as of the article’s citations, though the project has continued growing since.
What It Gets Wrong (or Incomplete)
The opening description underemphasises the agentic nature
The article’s lede calls it “a free and open-source autonomous artificial intelligence (AI) agent.” That’s technically correct. But the classification “autonomous personal assistant” in the infobox risks conflating it with simpler chatbot assistants.
The crucial distinction is that OpenClaw acts on the world. It doesn’t just answer questions. It sends emails, executes code, manages calendars, controls browsers, and coordinates with external services. That’s what makes it interesting and what makes the security risks real. The article could do more to emphasise that distinction from passive chatbots.
The Peter Steinberger/OpenAI section is absent at time of writing
The article notes “On February 14, 2026, Steinberger announced he will be joining OpenAI and the project will be moved to an open-source foundation.” This is included in the opening, but as of this review there’s no dedicated section expanding on what the OpenAI move means — what the foundation structure looks like, what Steinberger’s role will be, what OpenAI’s commitments to the project are.
Given that this is arguably the most significant recent development in the project’s history, it deserves more than one sentence. The article was recently updated (7 hours ago), so this may be actively being expanded. But currently it’s a notable gap.
(Full coverage of the OpenAI move: [Peter Steinberger Joins OpenAI](/openclaw-creator-joins-openai/))
The CVEs aren’t mentioned
The security section references general categories of risk but doesn’t mention any specific CVEs. CVE-2026-25253 (CVSS 8.8, one-click RCE) was publicly disclosed and widely reported. CVE-2026-24763 and CVE-2026-25157 followed. CVE-2026-22708 (indirect prompt injection) rounds out the known disclosure set.
Wikipedia articles about software typically document known CVEs in the security section, especially high-severity ones. Their absence makes the security section feel incomplete.
(Full CVE documentation: [OpenClaw Security Guide 2026](/openclaw-security-guide-2026/))
The Moltbook breach is absent
The Moltbook database misconfiguration — which exposed 1.5 million API tokens and affected a large portion of the OpenClaw user base — doesn’t appear in the article. Given the scale of the incident and its direct connection to the OpenClaw ecosystem, it arguably belongs in the security section with appropriate sourcing.
No mention of the infostealer incident
The article was apparently last edited before the Hudson Rock infostealer report became public (the BleepingComputer article went live roughly 15 hours ago; The Hacker News version similarly). By the time you read this, the article may have been updated — Wikipedia editors move fast on significant news. But the gap is worth noting: the [first confirmed in-the-wild theft of OpenClaw configuration files](/openclaw-infostealer-malware-alert/) is exactly the kind of documented security event that belongs in an encyclopaedia article about a product with this security profile.
The “Chinese adoption” context is thin
The article mentions that “in China… developers adapted it to work with the DeepSeek model and domestic super-apps.” But the [Kimi Claw launch](/kimi-openclaw-integration/) — Moonshot AI building OpenClaw into the Kimi chatbot as a native cloud product — is a more significant development than “Chinese developers adapted it.” The article will need updating to reflect that a major Chinese AI lab has productised the framework.
The “Vibe Coder” Reference
There’s an interesting citation buried in the article: footnote 2 identifies Steinberger as an “Austrian vibe coder,” cited to his own steipete.me about page.
“Vibe coding” — the practice of building software through natural language interaction with AI models, guiding the output rather than writing every line by hand — has become a genuine term of art. Steinberger has embraced it as a description of how OpenClaw was built. The fact that Wikipedia uses this term, sourced to his own self-description, is a small sign of how quickly this vocabulary has moved from community slang to reference content.
What the Page’s Existence Tells Us
There’s a meta-level story in the Wikipedia article worth dwelling on.
OpenClaw achieved this in under three months from its November 2025 initial release to encyclopaedia-notable coverage. For context: Linux was created in 1991 and had broader cultural impact for years before getting comprehensive Wikipedia coverage. The pace at which AI agent projects move through the legitimacy spectrum — from obscure GitHub repo to Wikipedia article to Fortune thinkpieces to Pentagon supply chain discussions — is genuinely unprecedented.
The Wikipedia article is a milestone, but it’s also a snapshot of a project mid-sprint. The article’s gaps reflect what’s still developing: the foundation structure, the security story, the geopolitical dimensions. Future editors will fill those in. The bones of the article are sound, and the citation quality is good.
For anyone researching OpenClaw for the first time, the Wikipedia page is a solid starting point — accurate on the basics, appropriately referenced, and improving quickly. For anyone who’s been following the project closely, it’s a useful reminder of what’s become publicly established fact versus what’s still in motion.
The lobster has earned its encyclopaedia entry. It just needs some editing.
—
Wikipedia article: [en.wikipedia.org/wiki/OpenClaw](https://en.wikipedia.org/wiki/OpenClaw)
Related: [OpenClaw name changes explained](/name-changes-explained/), [Is OpenClaw safe?](/is-openclaw-safe/), [Security guide 2026](/openclaw-security-guide-2026/)