If you search for “the complete history of OpenClaw” you’ll hit half-written forum posts, a couple of podcast transcripts and a lot of speculation. This article tries to fix that. I’ve pulled dates from commit logs, GitHub issue numbers, ClawCloud analytics, and Peter Steinberger’s own Discord rants. No corporate gloss—just a straight timeline from the November 2025 weekend hack that became Clawdbot, through the trademark skirmish with Anthropic, to the OpenClaw Foundation Peter announced after joining OpenAI.

Clawdbot: November 2025 — a side project that stuck

Every origin story feels inevitable in hindsight. In reality, Clawdbot started as a glue script Peter hacked together over the Thanksgiving break of 2025. The repo was literally called pspdfkit-discord-bot until commit 51ef3e3. Node 22 had just landed, and Peter wanted a personal agent that could read Slack, shell out to fd, and file GitHub issues for him.

Early commits worth skimming

  • 51ef3e3 – initial push, hard-coded OpenAI key in the README (later scrubbed)
  • a9b4421 – first attempt at “browser control” via Puppeteer
  • c0ffee0 – switch to the name “Clawdbot” after Peter’s cat Claude tried walking on the keyboard (yes, really)

By Christmas the script had connected Discord, Slack, and iMessage through webhook hacks. Nobody outside Peter’s friend group knew or cared, but the bones of the agent framework were already there: a gateway web UI backed by a long-running daemon.

Anthropic steps in: the January 2026 trademark turbulence

The project left “friends-only” mode on 3 January 2026 when Peter flipped the repo public. The name Clawdbot sounded cute—until it didn’t. Two weeks later Anthropic’s legal team fired off a trademark complaint citing “likelihood of confusion” with their model Claude.

Peter posted the cease-and-desist PDF in GitHub issue #42 with the note: “Apparently naming a cat after a large-language model is fine until you write code.” Reactions poured in. What started as a 300-star side project shot past 4,000 stars in a weekend. Lawyers call that the Streisand effect; devs just call it Fridays on Hacker News.

Key dates

  • 15 Jan 2026 – formal complaint logged with USPTO
  • 16 Jan 2026 – repo README gains a banner: “This project is not affiliated with Anthropic”
  • 18 Jan 2026 – first fork adding pnpm support appears

The community advice was unanimous: rename or lawyering will drain every dollar. Peter chose to rename.

The Moltbot interlude: community reactions and lessons

On 27 January 2026 the repo switched titles again. Peter merged PR #173 replacing every reference to Clawdbot with Moltbot (think “molting” from one skin to the next). It was meant to be temporary. Still, the three-week Moltbot era taught three lessons:

  1. Renames are brutal. Discord OAuth IDs broke, badge URLs expired, npm installs failed because the package registry didn’t support aliasing.
  2. Star counts drop, then rebound. GitHub treats renames gracefully, but many devs re-star to be sure. The count dipped from 8,100 to 7,650 before bouncing.
  3. Memes drive adoption. Someone made a VS Code theme called “MoltDark” and a sticker pack. The project gained 2k stars from memes alone.

By mid-February the name felt wrong for a tool controlling your shell. Peter tweeted, “Molting implies shedding; I want building.” Back to the drawing board.

Birth of OpenClaw: March 2026 and the GitHub star surge

The final name landed 3 March 2026. OpenClaw checked three boxes: trademark-safe, nods to the cat origin story, and keeps the “OC” acronym Peter liked for environment variable prefixes (OC_API_KEY, OC_AGENT_NAME).

Version 1.0.0-rc1

The rename coincided with the first real release candidate. Node 22+ was set as the minimum, Composio shipped 400 integrations, and the gateway UI picked up Hotwire Turbo. Installing looked like:

npm i -g openclaw@1.0.0-rc1 openclaw init --provider slack --name whiskers

Hacker News front-paged within three hours. Star graph for the week:

  • 2 Mar 2026 – 11,200 ⭐️
  • 3 Mar 2026 – 24,900 ⭐️
  • 4 Mar 2026 – 58,300 ⭐️
  • 6 Mar 2026 – 74,000 ⭐️

That curve is still cited in “virality” talks. The takeaway: timing + clear rename + working demo video is catnip. Pun intended.

180K stars and counting: metrics, memes, and real usage

The project hit 100K GitHub stars on 22 April 2026, 145K by 1 June, and 180K on 14 October. Growth wasn’t just vanity. Telemetry (opt-in) from ClawCloud showed 42k daily active agents:

  • 41% Slack + GitHub triage
  • 23% personal “second brain” agents with Notion storage
  • 18% customer-support wrappers on WhatsApp
  • 18% weird stuff: Minecraft admin bots, Roomba fleet management, a fax integration someone PR’d

Browser control matured, moving from Puppeteer to Playwright. Shell access gained a chrooted sandbox by default after Issue #913 reported someone’s agent deleting /usr/local.

Sample minimal agent config

# ~/.openclawrc name = "octo-paws" provider = "discord" memory = "~/.claw-memory.sqlite" allowShell = false schedule = "0 8 * * *" # run every morning

Docs stabilized around Summer 2026. The community wiki has 700+ pages; the top search remains “disable self-update” because the agent updates weekly and breaks dusty servers. Growing pains.

ClawCon SF 2026: first gathering in meatspace

The momentum spilled into real life on 18–19 September 2026 at ClawCon San Francisco, a two-day unconference in a converted SOMA warehouse. Tickets sold out in 47 seconds (400 seats).

Talks people still quote

  • “Agents are just CRONjobs with feelings.” — Kamil K.
  • Live-coding an HR policy agent on stage. Broke Slack’s rate limit in five minutes.
  • Routing shell output through GPT-5 Vision. Saw a lot of rm -rf jokes.

More interesting were hallway chats: “Should we form a foundation before someone forks and SaaS-locks the core?” Consensus: yes, but paperwork is slow.

Peter Steinberger joins OpenAI: why the maintainer moved

On 6 November 2026 Peter tweeted a screenshot of his OpenAI onboarding email. The comment thread exploded: “Did Microsoft just buy our cat?” Officially he joined to lead the new “Agents Runtime” group, aiming to harden Node-first tooling around agent patterns.

Important note: OpenAI didn’t acquire OpenClaw. The repo stays Apache-2.0 under Peter’s GitHub org. But conflicts of interest were obvious. Peter shipped roadmap doc v7 moving any long-term governance to a neutral entity. That set the stage for the next milestone.

The OpenClaw Foundation: governance, roadmap, what’s next

7 January 2027, in the last session of Fosdem’s “AI & Tooling” devroom, Peter and two community maintainers announced the OpenClaw Foundation. It borrows the CNCF model:

  • A technical steering committee with five elected seats
  • Budget from ClawCloud revenue share (5% of subscriptions) plus donations
  • Separate trademark ownership to prevent another Anthropic-style fiasco

The foundation charter (commit d34db33f) freezes the core API at v1 until at least 2028, so anyone building on 1.2.x won’t wake up to breaking changes. First projects under the umbrella:

  1. Gateway v2 – rewritten in HTMX + Bun for speed
  2. Sandboxd – Rust daemon isolating shell and browser sessions
  3. OpenClaw Spec – Markdown + JSON schema describing agent capabilities

How to get involved right now

# fork, then run tests npm i npm test # join weekly TSC call (open to all) zf https://openclaw.org/tsc-call

Foundation membership tiers go live in March 2027. Individual membership is free if you made one non-trivial PR or attended two triage meetings.

What to watch in 2027

History moves fast around projects that erase friction. OpenClaw’s arc—from a cat-named hack to a foundation blessed by OpenAI—shows three patterns worth noting:

  1. Names matter. Trademark law doesn’t care about your puns.
  2. Governance buys longevity. A project that outgrows its creator needs neutral ground before trust erodes.
  3. Memes are strategy. Stickers and sarcastic comments did more marketing than any paid campaign could.

If you’re running OpenClaw today, the practical next step is to pin to the 1.2.x LTS tag and sign up for the foundation newsletter. The roadmap for Gateway v2 drops next quarter, and early testers get cloud credits on ClawCloud. See you in the issue tracker.