To be honestly, what happened next is more interesting than the outage itself.
Founder Peter Steinberger posted a candid, no-BS retrospective on May 5th. Two bad releases (2026.4.24 and 2026.4.29) caused real pain: Gateway slowdown, broken plugin dependency loops, messed-up Discord/Telegram/WhatsApp channels.
But he didn't stop at "sorry." He named the root causes.
3️⃣Three structural problems he identified:
🔴 **Bloated core** — too much living inside the Gateway, tight coupling everywhere
🔴 **Unclear plugin boundaries** — dependencies got tangled in ways that were hard to debug and harder to fix
🔴 **Npm supply chain risk** — a problem the whole JS ecosystem knows intimately but rarely addresses head-on
These aren't random bugs. They're architectural debt. And naming them publicly takes guts.
The fix isn't just patches — it's restructuring. The team is moving functionality out of the core and onto **ClawHub**, with an **LTS announcement coming at the end of May**.
This is the right call. Extraction is harder than patching, but it's how you build for the long haul.
For founders and OSS maintainers: this is a masterclass in accountability. You can ship fast, or you can ship clean — but when you break things, owning it like this is how trust gets rebuilt.