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

I was getting a lot of use case out of it mainly interacting with the file system.

The problem is if not carefully designed it will burn through tokens like crazy.

If 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 the best tools to do a variety of tasks. Yes, each one of those could be done with just a coding agent, but I found it's less effort to get OpenClaw to do it than you writing something for each use case.

Very honest question: One of the use cases I had with OpenClaw that I'm missing now that I don't use it: I could tell it (via Telegram) to add something to my TODO list at home while I'm in the office. It would call a custom API I had set up that adds items to my TODO list.

How can I replicate this without the hassle of setting up OpenClaw? How would you do it?

(My TODO list is strictly on a home PC - no syncing with phone - by design).

(BTW, the reason I stopped using OpenClaw is boring: My QEMU SW stopped working and I haven't had time to debug).

I did too :D

Nothing of what my agents do, we didn’t previously do. But now I can get moderate to good results with a lot less effort. Allowing the business to expand whilst keeping costs controlled.

IMHO, the biggest problem with OpenClaw and other AI agents is that the use-cases are still being discovered. We have deployed several hundred of these to customers and I think this challenge comes from the fact that AI agents are largely perceived as workflow automation tools so when it comes to business process they are seen as a replacement for more established frameworks.

They can automate but they are not reliable. I think of them as work and process augmentation tools but this is not how most customers think in my experience.

However, here are a several legit use-case that we use internally which I can freely discuss.

There is an experimental single-server dev infrastructure we are working on that is slightly flaky. We deployed a lightweight agent in go (single 6MB binary) that connects to our customer-facing API (we have our own agentic platform) where the real agent is sitting and can be reconfigured. The agent monitors the server for various health issues. These could be anything from stalled VMs, unexpected errors etc. It is firecracker VMs that we use in very particular way and we don't know yet the scope of the system. When such situations are detected the agent automatically corrects the problems. It keeps of log what it did in a reusable space (resource type that we have) under a folder called learnings. We use these files to correct the core issues when we have the type to work on the code.

We have an AI agent called Studio Bot. It exists in Slack. It wakes up multiple times during the day. It analyses our current marketing efforts and if it finds something useful, it creates the graphics and posts to be sent out to several of our social media channels. A member of staff reviews these suggestions. Most of the time they need to follow up with subsequent request to change things and finally push the changes to buffer. I also use the agent to generate branded cover images for linkedin, x and reddit articles in various aspect ratios. It is a very useful tool that produces graphics with our brand colours and aesthetics but it is not perfect.

We have a customer support agent that monitors how well we handle support request in zendesk. It does not automatically engage with customers. What it does is to supervise the backlog of support tickets and chase the team when we fall behind, which happens.

We have quite a few more scattered in various places. Some of them are even public.

In my mind, the trick is to think of AI agents as augmentation tools. In other words, instead of asking how can I take myself out of the equation, the better question is how can I improve the situation. Sometimes just providing more contextually relevant information is more than enough. Sometimes, you need a simple helper that own a certain part of the business.

I hope this helps.

No wireless. Less space than a Nomad. Lame.

Sure, anything it does can be done better with specialized tooling. If you know that tooling.

The memory thing sounds like an implementation limit rather than something fundamentally unsolvable. Just experiment with different ways of organizing state until something works?