Earlier quoted context omitted.
Please don't do this here.
I am sorry. I understand that many of us are heavily invested financially or emotionally into AI but the key insight about OpenClaw remains the same that it really isn't much useful beyond maybe a daily news summary. Nothing that cannot be done otherwise.
OpenClaw’s memory is unreliable, and you don’t know when it will break
181–190 of 196 posts
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#182Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#183Earlier quoted context omitted.
What sort of tasks do you have it do for you?
Two categories: actual useful work for the company, and improving the bot's own infrastructure. Useful work includes: bug triage, matching up external user bug reports on GitHub to the internal YouTrack, fixing easy looking bugs, working on a redesign of the website. I also want to extend it to handling the quarterly accounting, which is already largely automated with AI but I still need to run the scripts myself, pr…
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#184Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#185Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#186Earlier quoted context omitted.
I've used open claw (just for learning, I agree with the author it's not reliable enough to do anything useful) but also have a similar daily summary routine which is a basic gemini api call to a personal mcp server that has access to my email, calendar etc. The latter is so much more reliable. Open claw flows sometimes nail it, and then the next day fails miserably. It seems like we need a way to 'bank' the correct…
This is interesting. I haven't used OpenClaw but I set up my own autonomous agent using Codex + ChatGPT Plus + systemd + normal UNIX email and user account infrastructure. And it's been working great! I'm very happy with it. It's been doing all kinds of tasks for me, effectively as an employee of my company. I haven't seen any issues with memory so far. Using one long rolling context window, a diary and a markdown wi…
- I suspect that in this moment, cobbling together your own simple version of a “claw-alike” is far more likely to be productive than a “real” claw. These are still pretty complex systems! And if you don’t have good mental models of what they’re doing under the hood and why, they’re very likely to fail in surprising, infuriating, or downright dangerous ways.
For example, I have implemented my own “sleep” context compaction process and while I’m certain there are objectively better implementations of it than mine… My one is legible to me and therefore I can predict with some accuracy how my productivity tamagotchi will behave day-to-day in a way that I could not if I wasn’t involved in creating it.
(Nb I expect this is a temporary state of affairs while the quality gap between homemade and “professional” just isn’t that big)
- I do use mine as a personal assistant, and I think there is a lot of potential value in this category for people like me with ADD-style brains. For whatever reason, explaining in some detail how a task should be done is often much easier for me than just doing the task (even if, objectively, there’s equal or higher effort required for the former). It therefore doesn’t do anything I _couldn’t_ do myself. But it does do stuff I _wouldn’t_ do on my own.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#187Earlier quoted context omitted.
This is interesting. I haven't used OpenClaw but I set up my own autonomous agent using Codex + ChatGPT Plus + systemd + normal UNIX email and user account infrastructure. And it's been working great! I'm very happy with it. It's been doing all kinds of tasks for me, effectively as an employee of my company. I haven't seen any issues with memory so far. Using one long rolling context window, a diary and a markdown wi…
I did (using Claude Code) something that sounds very similar to this. It’s a bunch of bootstrapped Unix tools, systemd units, and some markdown files. Two comments: - I suspect that in this moment, cobbling together your own simple version of a “claw-alike” is far more likely to be productive than a “real” claw. These are still pretty complex systems! And if you don’t have good mental models of what they’re doing und…
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#188As long as there's no solution to the long-term memory problem, we will have a "country of geniuses in a data center" that are all suffering from anterograde amnesia (movie: Memento), which requires human hand-holding. I have experimented with a lot of hacks, like hierarchies of indexed md files, semantic DBs, embeddings, dynamic context retrieval, but none of this is really a comprehensive solution to get something…
You're right to be skeptical. Without a way to actually implement how the human brain processes experiences into a consolidated memory, we won't be able to solve the long term memory problem at all. Not with the current technology. An LLM context is a pretty well extended short term memory, and the trained network is a very nice comprehensive long term memory, but due to the way we currently train these networks, an…
It's like spontaneous implemention of thought experiments from yesteryear. I wonder if all this product-focused experimentation will accidentally impact philosophy of mind after all...
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#189Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#190Earlier quoted context omitted.
Are you concerned about telegram admins having access to that information?
Yeah! And what if Samsung put a bug in the silicon that gives them access to all your stuff without you ever knowing! Or the CIA has set up inside your closet with a listening device!