[deleted]
OpenClaw’s memory is unreliable, and you don’t know when it will break
81–90 of 196 posts
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#82I'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 direct…
> easy to run on Kubernetes
that sounds like an oxymoron.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#83If you look at my comment history, you'll see what seems to be someone defending OpenClaw (even though I stopped using it). I have some issues with the article, but I agree with some of the conclusions: It's great tinkering with it if you have time to spare, but not worth using weeks of your time trying to get a perfect setup. It's just not that reliable to use up so much of your time. I will say, it's still amongst…
MS todo app, or any number of others. Added benefit of not needing telegram
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#84Earlier quoted context omitted.
> You offered nothing to support this. You've got it inverted. My point is the people saying "You could have done that just as easily with ..." are the ones not supporting it. The commenter has already built that thing with OpenClaw. If someone is saying it could easily have done without it - well, demonstrate it!
It appears that you are confusing who has the burden of proof here. It is the one making the claim contrary to the status quo. Hint: the status quo is not that openclaw is a tech that is magnitudes better than using LLMs without it. Listing a bunch of things that are just normal LLM things as reasons why openclaw is great is not making that case.
Burden of proof is on the one making the claim. Status quo has nothing to do with it.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#85Earlier quoted context omitted.
It appears that you are confusing who has the burden of proof here. It is the one making the claim contrary to the status quo. Hint: the status quo is not that openclaw is a tech that is magnitudes better than using LLMs without it. Listing a bunch of things that are just normal LLM things as reasons why openclaw is great is not making that case.
Burden of proof is on the one making the claim. Status quo has nothing to do with it.
You should revisit the burden of proof then. Status quo is most certainly an important part.
Regardless, their claim was "OpenClaw is flawed, but the convenience is an order of magnitude higher than anything else."
And they attempted to shift the burden when I asked for substantiation.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#86Earlier quoted context omitted.
Burden of proof is on the one making the claim. Status quo has nothing to do with it.
You should revisit the burden of proof then. Status quo is most certainly an important part. Regardless, their claim was "OpenClaw is flawed, but the convenience is an order of magnitude higher than anything else." And they attempted to shift the burden when I asked for substantiation.
Status quo influences how good your proof has to be (extraordinary claims require extraordinary evidence) but not who needs to bring it.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#87Earlier quoted context omitted.
You should revisit the burden of proof then. Status quo is most certainly an important part. Regardless, their claim was "OpenClaw is flawed, but the convenience is an order of magnitude higher than anything else." And they attempted to shift the burden when I asked for substantiation.
Status quo influences how good your proof has to be (extraordinary claims require extraordinary evidence) but not who needs to bring it.
Think more deeply about this. https://lastedenblog.wordpress.com/2016/12/13/professor-jame...
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#88Sounds like an armchair expert
Right back at ya ;) The author makes some good conclusions; I’m as AI-pilled as the next hopefully-not-soon-to-be-ex-software-engineer, and I struggled to find use cases for my Claw that couldn’t be served with a cronjob and $harness. If your findings contradict that, we are all ears - genuinely.
Oh not really, but the article just reads like it’s from an observing putting of view, without tangibles.
The killer thing was remote control, but that’s here in Claude now. In my opinion claw has to reason to exist anymore.
I tried it, didn’t like it. It gave me the ick with the communication channel.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#89If you look at my comment history, you'll see what seems to be someone defending OpenClaw (even though I stopped using it). I have some issues with the article, but I agree with some of the conclusions: It's great tinkering with it if you have time to spare, but not worth using weeks of your time trying to get a perfect setup. It's just not that reliable to use up so much of your time. I will say, it's still amongst…
MS todo app, or any number of others. Added benefit of not needing telegram
I've been using my TODO program since 2009. It's heavily customized for my needs. I'm not going to change it.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#90I actually quite enjoy the OpenClaw. Although the recent CC crackdown has caused me to try different LLM providers which aren't that reliable but anyways, here are few things I do with it, in all separate groups.
* Telegram Health Group, created an agent to help me track sleep, recommend my supplements based on my location, remind me in the morning and evening to monitor my food. I send it images of what I eat and it keeps track of it. * Telegram Career Group, I randomly ask it to find certain kind of job posts based on my criteria. Not scheduled, only when I like to. * Telegram Coder Group, gave it access to my github account. It pulls, runs tests and merges dependabot PRs in the mornings. Tells me if there are any issues. I also ask it to look into certain bugs and open PRs while I'm on the road. * Telegran News Group, I gave it a list of youtube videos and asked it to send me news every day at 10am similar to the videos.
So far, it's a super easy assistant taking multiple personas. But it's getting a bit painful without CC subscription