Is OpenClaw still around?
OpenClaw 还在吗?- Looking again at how OpenClaw has developed over the past few months, I found its public buzz really has dropped, but the product hasn’t stopped: it set up an independent foundation in July, released 2.0 on August 30, and keeps improving its fundamentals.
- Once an agent is actually installed on your computer for long-term use, the question shifts from “can it do it” to “do I dare let it do it long term”: permissions, security, cost, stability, and what everyday things ordinary people would actually hand over to it.
- “AI can do things on its own” is no longer that novel; what comes next is who’s more stable, more secure and better at understanding users’ needs. What may truly be scarce for agents is no longer capability, but making people comfortable handing things over.
A few months ago, OpenClaw was almost everywhere.
An AI agent running on your own computer that could connect to chat apps like Telegram and WhatsApp, had memory, and could operate a browser, read and write files, and run commands.
When many people first saw it, they had a very intuitive feeling:
the personal AI assistant seems to have really arrived.
But lately I’ve clearly seen far less discussion of OpenClaw.
I had assumed that maybe the buzz around this kind of product had passed.
After looking again at how it has developed over these months, I think a more accurate way to put it is:
OpenClaw’s public buzz really has dropped, but the product hasn’t stopped.
In July it set up an independent foundation and began doing extended-stable releases and product maturity management.
On August 30, OpenClaw released 2.0, continuing to improve a large batch of fundamentals: installation, memory, browser, automation, security.
So rather than “has OpenClaw gone cold,” what I’m more curious about now is:
why is a product still developing rapidly no longer exciting people the way it did a few months ago?
What first made OpenClaw take off was a new way of using AI
Early AI was mostly still:
I open a tool, type a question, and wait for it to answer.
OpenClaw showed something else.
AI could run for a long time, have memory, connect to all kinds of services, and actually operate a computer.
You didn’t even need to sit at the computer.
Send it a message:
- check my email for me.
- sort out today’s schedule.
- go look something up on the web.
and it could keep going on its own.
What was truly novel wasn’t any one of these features, but that these capabilities were put together.
AI no longer just answered questions.
It started acting.
That’s also why OpenClaw’s earliest demos spread so easily.
A video of a few dozen seconds was enough to make people understand “what an agent might be.”
But once it was really installed on your computer, the questions changed
Seeing AI handle email automatically in a demo is cool.
But if this agent really runs on your computer every day, you quickly run into a different set of questions:
- what exactly can it see?
- can it send email directly?
- which operations need my confirmation?
- can it touch passwords and API keys?
- what if a web page contains malicious content?
- what permissions do third-party Skills actually get?
- when it does something wrong, can I find out what it just did?
- is running it long term expensive, and is it stable?
None of these questions is as eye-catching as “AI operating your computer automatically.”
But really using an agent long term actually depends more on these things.
Over the past half year, OpenClaw has also had problems like malicious third-party Skills and security risks.
That actually exposes a very basic tension in agent products:
the more capabilities you give it, the more permission and security problems you have to solve.
Before, when a chatbot answered wrong, we just asked again.
When an agent that can operate files, a browser, a shell and real accounts does something wrong, the cost can be completely different.
So by this point in a product, the focus naturally shifts from:
“can it do it?”
slowly to:
“do I dare let it do it long term?”
There’s another problem: being able to do anything isn’t the same as knowing what to use it for every day
The use cases for coding agents are relatively clear.
Writing code, fixing bugs, reviewing PRs, running tests.
But the scope of a personal agent is much wider.
It can handle your email, schedule, information organizing, browser operations, automated tasks, even manage other agents.
The capabilities sound huge.
The problem is that ordinary users still have to answer for themselves:
what do I actually have each day that’s worth handing over to it?
This is another hard problem I think OpenClaw runs into once it goes from demo into real life.
“It can do anything” is a very strong description of capability.
But it isn’t necessarily a clear way into a product.
The tools most people end up keeping long term usually have a few very clear, recurring use cases.
Personal agents are still looking for these use cases.
Much of what OpenClaw has been doing lately isn’t that “cool”
But it matters.
- Like making installation simpler.
- Reducing what you have to deal with in first-time setup.
- Improving the browser and control UI.
- Making releases more stable.
- Strengthening credentials, permissions and security.
- Making automation easier to manage.
These updates can hardly create the feeling that “the future is already here” the way the earliest demos did.
But they solve the problems of a different stage:
how to turn a very capable agent into a product ordinary people can really use long term.
That’s also why I find OpenClaw’s recent “quiet” quite interesting.
At first, everyone was exploring the limits of what agents could do.
Now more and more effort is going into:
reliability, permissions, security, cost, the barrier to use, and real everyday needs.
These things aren’t that suited to viral demos, but they’re closer to the product itself.
Another change: the novelty OpenClaw first represented is gradually becoming consensus
A few months ago, a long-running personal agent that could operate a computer and connect lots of tools was novel enough in itself.
Now similar capabilities are becoming more and more common.
Different open-source agents are doing it.
Products like ChatGPT and Claude keep adding agents, computer use and integrations.
The personal agent is no longer just one project’s vision, OpenClaw’s.
So part of the drop in buzz doesn’t necessarily mean this direction doesn’t hold up.
It may just be that:
“AI can do things on its own” isn’t as new as it was a few months ago.
Competition from here will happen in more specific places:
- who’s more stable.
- who’s more secure.
- who’s easier to set up.
- who really knows what users need it to do every day.
- who can get users willing to hand over more permissions.
So what actually happened to OpenClaw?
At least for now, I haven’t seen enough data to prove it went through a clear loss of users.
What can be said fairly confidently is:
fewer people are talking about it, but the project is still very active.
And what it’s doing now is quite different from when it first blew up.
At first, it needed to prove:
that a personal agent that can really act is possible.
That question has basically been answered.
The questions that come next are much more troublesome:
can it run safely, stably and at low cost?
Do ordinary people have needs frequent enough?
How much permission are we willing to give an agent?
When something goes wrong, how do we find out what happened, and how do we contain the consequences?
I think these questions are more worth following than “is OpenClaw still hot.”
Because they don’t only belong to OpenClaw.
Almost every agent product that wants to move from demo to real use will hit them in the end.
Once agents can do more and more, what may truly be scarce in a product is no longer only capability.
It’s:
making people comfortable handing things over to it.
Written in Chinese and translated into English with the help of AI. Read the original