Excited to share my early work at @openclaw as a Member of Technical Staff! 🦞
We do _everything_ in the open, including open sourcing our data for the entire community to help us improve.
Looking forward to building alongside @steipete@vincent_koc@joshavant@dallinfinite
In collaboration with @nvidia, we’re open-sourcing a dataset of security scans for 67,453 ClawHub skills on @huggingface:
- NVIDIA SkillSpector flagged 1/2 for agentic risk
- Only 0.31% were malicious
- No two scanners agreed on more than 8.5% of risks
https://t.co/ml624ExiLG
@onusoz@grok Agreed, and buying a $10k workstation is still quite different than a $500 desk haha
But maybe for top of market engineers it will become a common perk
@onusoz Will companies give stipends for home AI workstations though?
Eg I wouldn't pay >$5k for a personal MacBook but most companies are willing to.
Episode 2 of OpenClaw’s official podcast
@steipete and @somalley108 join @hrudolph and @Pat_Erichsen to discuss OpenClaw stability, security, the future of OpenClaw, and the community’s response to the recently released OpenClaw mobile app.
https://t.co/CAOHKZhvqO
this is cool! bugs seem straightforward to identify and fix but how do you determine what UX problems are self driving?
it would be sweet to have something like an agent that notices sign ups are decreasing and proactively looks at recordings, events, etc, and proposes a few fixes
OpenClaw is now on iOS + Android 🦞
📱 Native mobile apps, finally
💬 Agents in your pocket
🔔 Channels, tasks, replies on the go
Run agents from wherever your thumbs are.
iOS: https://t.co/7LHHc9htgM
Android: https://t.co/X0Wuh2uA8w
One thing that feels missing from the skills ecosystem is a basic RSS style feeds concept
Eg I'd love to know when folks like @mattpocockuk drop a new skill
But the only way to do this rn is a manual `npx skills update`, which also has no per-author ability
@nickgrossman > We expect an increasingly diverse range of harnesses linking agents to both digital and physical environments.
whats some examples here? do you see these as domain-specific harnesses, but built on a meta harness?
@BradGroux@davemorin@chrismichel I'm seeing a lot of folks posting similar things but I'm not familiar with Om's writing
What stuck with you/shaped you?
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: https://t.co/KZTRZTNJ9J. 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