OpenClaw or BrokenClaw?
First off, I’d like to introduce myself. My name is Hannes Rudolph, and I’m the new Community Manager here at OpenClaw. Nice to meet you.
I want to acknowledge the frustration many of you have felt with OpenClaw’s stability. We’ve broken your claws, and that sucks. We’ve made some real progress recently, but there’s still work to do and we’re going to keep at it. We understand how frustrating it is to deal with repeated issues, especially when our public response has been lacklustre and hasn’t matched the seriousness of the problems you’re experiencing.
For anyone who wants to look at one data point showing how stability has changed over time, there’s an independent public tracker here:
isitstable.iclaw.digital/#/o…. We didn’t make it, and we don’t think any single tracker is infallible or tells the whole story. But it does help show how bad things got and where we are now. It’s a useful reference point, not a substitute for listening to people directly or looking at the issues they’re still having.
OpenClaw is nothing without the people who use it, build with it, question it, and help shape where it goes. We know that because many of us were frustrated users before joining the project. We care about this community, and we want this community to be a place where people can get help, share ideas, and be honest about what is and isn’t working. That means we need to listen when people are angry, engage when things are confusing, and make it easier for people to participate rather than shutting them down.
Please keep being vocal about what isn’t working. We’ll do our best to route feedback to the development team quickly and with the importance it deserves. I can merge things when needed, and we’re not interested in hiding behind process while users are dealing with broken or frustrating behaviour.
We’ve heard you. Now we need to show that we have.
Hannes
