Live data from Hacker News

OpenClaw’s memory is unreliable, and you don’t know when it will break

blog.nishantsoni.com

21–30 of 196 posts

Re: OpenClaw’s memory is unreliable, and you don’t know when it will break

#21
From my perspective there are some people that have never built real processes in their life that enjoy having some processes now. But agent processes are less reliable slower and less maintenable then a process that is well-defined and architectured and uses llm’s only where no other solution is sufficient. Classification, drafting, summarizing.

I’ve had a Whatsapp assistant since 2023, jailbraked as easy assistant. Only thing I kept using is transcription.

https://github.com/askrella/whatsapp-chatgpt was released 3 years ago and many have extended it for more capabilities and arguably its more performant than Openclaw as it can run in all your chat windows. But there’s still no use case.

It’s really classification and drafting.

Re: OpenClaw’s memory is unreliable, and you don’t know when it will break

#25
post #16

Earlier quoted context omitted.

I don’t get people’s hate. Let others enjoy it.

I think people are just tired of the fire hose of posts that have been showing up since it came out. It’s so annoying. Why does everyone need to pimp it so hard? It’s like your aunt trying to push Herbalife on you every time you see her.

That, and some people hate being on the receiving end of the output. The old "if you didn't bother writing it, I'm not going to bother reading it".

Re: OpenClaw’s memory is unreliable, and you don’t know when it will break

#26

I'm using openclaw as a personal development bot, which is pretty useful. It pings me throughout the day using crons to complete tasks and follows up on them. But aside from that, it is a very unreliable piece of software. I'm constantly having to fix it, or track down correct configurations. It can just decide to randomly edit it's own config, uses incorrect json keys and then the whole thing is dead. Or it blows th…

Amen.

I love the concept but I've never hosted such a terrible piece of software. Every update breaks something new or introduces another "anti-feature" that's enabled by default.

The documentation is often lagging behind and the changelog has such a low signal to noise ratio that you need a LLM to figure out what upgrading will break this time. For now I've just given up on updates and I've been patching bugs directly in the JS when they bother me enough.

If OpenClaw is the future of software I'm honestly a bit scared for the industry.

I'm open to suggestions, I tried Zeroclaw and Nullclaw but they're bad in their own way. I would like something that's easy to run on Kubernetes with WhatsApp integration and most important, stable releases.

Re: OpenClaw’s memory is unreliable, and you don’t know when it will break

#28

> 0 legitimate use cases My teams currently using it for: - SDR research and drafting - Proposal generation - Staging ops work - Landing page generation - Building the company processes into an internal CRM - Daily reporting - Time checks - Yesterday I put together proposal from a previous proposal and meeting notes, (40k worth)

None of those things require openclaw. You could accomplish them with something like Google Drive and Claude Code CLI.
Post reply on HN