OpenClaw, the open-source AI project that took the tech world by storm, is experiencing its worst crisis since launch. Users are abandoning the platform in droves following a series of technical failures that left many installations broken and unusable.
The crisis comes at a particularly sensitive time for the project. Founder Peter Steinberger recently joined OpenAI, leaving OpenClaw in transition from a single-person operation to a broader team structure. The timing of these technical issues with this leadership change has created a perfect storm of challenges.
Technical meltdown drives users away
Usage data paints a stark picture of OpenClaw’s declining fortunes. Both OpenRouter, which tracks AI model usage with OpenClaw, and SimilarWeb, which measures website traffic, show significant drops over the past 30 days. The numbers revealed a clear exodus of users seeking more stable alternatives.
The problems began accumulating on April 24, 2026, and by April 29, it became clear these weren’t isolated incidents. Users faced multiple critical issues:
- Slowed gateways affecting performance
- Installations stuck in plugin dependency repair loops
- Malfunctions in connected channels including Discord, Telegram, and WhatsApp
Many users had no choice but to roll back to older versions, eating up valuable development time. According to Steinberger, this wasn’t a single bug but a cascade of interconnected problems.
Infrastructure overhaul backfires
The technical failures stem from an ambitious but poorly executed restructuring effort. OpenClaw is attempting to transform from a developer playground into reliable infrastructure software. The goal is admirable: make the platform smaller, more secure, and suitable for production environments.
However, the execution has been problematic. Steinberger admits he underestimated the complexity of this transition. The project ended up in what he calls an “unfavorable intermediate state” where too many changes happened simultaneously without proper coordination.
The restructuring involves moving components to the new ClawHub platform and establishing clearer boundaries between core functionality and plugins. This shift was partly motivated by recent supply chain security incidents in the npm ecosystem, though OpenClaw wasn’t directly affected.
Single point of failure exposed
The crisis has exposed a fundamental structural problem with OpenClaw: it depended too heavily on one person. Steinberger handled releases, code reviews, packaging, and support single-handedly. This approach worked when OpenClaw was smaller, but it’s incompatible with the project’s professional ambitions.
With Steinberger now at OpenAI, this dependency has become a critical vulnerability. The project is scrambling to build a proper team structure through the newly founded OpenClaw Foundation, with support from OpenAI.
Recovery plan takes shape
OpenClaw is implementing several changes to address both technical and organizational issues. The project plans to introduce an LTS (Long-Term Support) version that will run alongside faster update cycles. This should give enterprise users the stability they need while allowing continued innovation.
The team is also overhauling the release process to prevent similar cascading failures in the future. More details about these changes are expected to be announced later in May.
The situation highlights the challenges facing open-source projects as they scale from individual efforts to enterprise-grade platforms. OpenClaw’s recovery will test whether the project can successfully navigate this transition while rebuilding user trust.
