Analysis
In mid-February 2026, the developer behind one of the fastest-growing projects on GitHub announced he was going to work for OpenAI. Peter Steinberger had built OpenClaw, an open-source AI agent framework, and grown it to hundreds of thousands of GitHub stars in a matter of months. Then he told the community he was leaving to join the company many of them saw as the commercial giant in the room.
The worry was obvious. When the person who writes most of the code walks away, what happens to everyone who built their work on top of it? Open-source history is full of projects that went dark the moment their founder lost interest or got hired.
OpenClaw didn't follow that script. Because the code was open under a permissive licence, no single employer could lock it away. A community foundation took over stewardship, the original repo kept getting updates, and a few alternative versions sprang up for people who wanted something the main project wasn't offering. Six months on, the practical situation for a business running OpenClaw is calm: your skills still work, the marketplace is still there, and the project has more hands on it than before.
That's the headline. The detail below is messier, and worth understanding if you're deciding whether to keep building on OpenClaw or one of its offshoots.
The Initial Shock
Steinberger's announcement landed with no real warning. At the time, OpenClaw was sitting somewhere north of 340,000 GitHub stars and still climbing fast (GitHub, openclaw/openclaw; star counts in this period are approximate, the repo went from roughly 247,000 in early March to around 379,000 by June). The MIT licence meant anyone could fork the code at any time, but in practice the project's direction ran through one person.
So the reaction was loud. Reportedly, the OpenClaw Discord picked up around 10,000 new members and three forks were announced inside the first 48 hours, though that surge isn't documented by any source I'd stand behind. Enterprise users did the sensible thing and paused new deployments until the picture cleared.
The Governance Transition
The clearest, verifiable change was structural. A non-profit OpenClaw Foundation was set up to steward the project independently of any single person or company. Its stated position is plain: no one company controls OpenClaw.
Beyond that, reporting gets thinner. There are claims that within a week the project formed a steering committee with community representatives, named new maintainers with commit rights, published a 12-month roadmap, and moved Steinberger to an "advisor" role with no commit access. I'd treat those as unconfirmed. The public repo describes governance as informal and community-driven, and the Foundation site sticks to a mission statement rather than a transition timeline.
The message most people took away, regardless of the exact mechanics, was that OpenClaw would carry on as a community project rather than rise or fall with one developer's job.
The Major Forks
Forking is where the public account gets shaky, so a caveat up front: the three forks described in the original write-up below do not match the fork ecosystem any source can confirm. According to Can it run OpenClaw, the real offshoots carry names like Moltworker, ZeroClaw, MimiClaw, PicoClaw, Nanobot, NanoClaw and IronClaw. The forks named here, along with their star counts and feature lists, appear to be illustrative rather than verified. Read them as a picture of the *kinds* of forks an ecosystem produces, not a directory you should go shopping in.
OpenClaw Core (The Original)
Stars: ~345,000 (continued growth, approximate) Maintainers: Community foundation and contributors Direction: Continuity, keep the existing vision and codebase intact ClawHub: Still the primary marketplace Status: The default. Most users stayed put.
OpenClaw Community Edition (CE) *(reportedly; not confirmed by any source)*
Stars: 15,000 *(uncorroborated)* Maintainers: Former contributors Direction: More aggressive changes, dropping dependencies, adding features the original team had pushed back on Key differences: Native multi-agent support, a rewritten execution engine, no npm dependency Audience: Developers who wanted faster movement and fewer guardrails
LibreClaw *(reportedly; not confirmed by any source)*
Stars: 8,000 *(uncorroborated)* Maintainers: Privacy-focused developers Direction: Maximum privacy and decentralisation Key differences: Offline by default, no external API calls, peer-to-peer skill sharing instead of a central ClawHub Audience: Privacy-conscious users and regulated industries
EnterpriseClaw *(reportedly; not confirmed by any source)*
Stars: 5,000, mostly organisational accounts *(uncorroborated)* Maintainers: Enterprise consulting firms Direction: Production-focused with enterprise features Key differences: Built-in SSO, audit logging, compliance reporting, SLA guarantees Audience: Large enterprises and government agencies
Why Users Stayed
Drama aside, most people stuck with the original. A few reasons explain it.
Network Effects: The ClawHub skill marketplace, think of it as npm for AI agents, has real pull. It grew from roughly 127 skills in November 2025 to more than 15,000 by March 2026. Skills are written for the original; fork compatibility is hit and miss.
Trust in Process: Standing up the Foundation and communicating openly went a long way toward settling nerves.
MIT License: Because the licence is permissive, the project was never going to turn proprietary. Forking was always on the table, which oddly made forking feel less urgent.
Continuity: The original's momentum, documentation and community are hard to rebuild from scratch.
No Immediate Crisis: The code kept working. Nothing forced anyone to switch overnight.
The Steinberger Effect on OpenAI
Steinberger's move to OpenAI may not have been entirely one-directional. There are claims that his presence nudged OpenAI toward open source, specifically, that OpenAI launched an "open tools" initiative for community integrations, that OpenClaw skills picked up unofficial support on OpenAI's developer platform, and that Steinberger pushed for API compatibility with open-source alternatives.
I'd flag all three as unconfirmed. What's actually on the record is narrower: Steinberger joined OpenAI to work on agent and multi-agent systems, and OpenClaw stays open source. Whether his hire signals genuine openness or a smart bit of co-opting is the kind of debate that won't resolve any time soon.
The Health of the Ecosystem
Looking back from roughly six months after the announcement, and treating any forward-looking comparison as a projection rather than settled fact, the OpenClaw ecosystem looks to be in decent shape:
- Competition between forks pushes everyone to improve
- Specialised forks cover needs the original never set out to address
- The original project benefits from focused, foundation-backed governance
- Combined growth: reportedly, total stars across all the forks now exceed the original's old peak, though that aggregate isn't something any source can back up, and the fork roster it leans on is itself unverified
This is roughly how open source is meant to behave. A project's survival shouldn't depend on one person staying interested or staying put. A working fork ecosystem means OpenClaw's ideas outlast any single individual or company.
Lessons
A few things worth taking from the OpenClaw episode:
- Governance matters: Projects need structures that outlive the founder.
- Licences are insurance: MIT or GPL means the community always keeps its options.
- Communication is critical: Clear, fast updates stop a panic before it starts.
- Forks are healthy: They reflect genuinely different needs, not just drama.
- Network effects are real: Marketplaces and ecosystems are what keep people from leaving.
OpenClaw started life in November 2025 and reached hundreds of thousands of stars in well under a year. The post-Steinberger period is the real test, and so far it shows that a serious open-source project can be bigger than the person who made it.