It can integrate apis for you on the fly. That’s one of the biggest usecases IMO. Combine that with skills, cron, and sub-agents, and you get a lot of power there.
OpenClaw’s memory is unreliable, and you don’t know when it will break
11–20 of 196 posts
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#12Could we stop with the clickbaiting headlines?
You forgot to add, “Here’s why.” /s
I know that headlines are all about eyeballs, but this is seriously just exhausting. Headlines are advertisements and advertisements are about getting engagement. Surely having your audience just getting angry at them isn’t a good thing, right?
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#13> 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)
I don’t get people’s hate. Let others enjoy it.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#14there are zero legitmate use cases? sure bro.
you can say that to my claw which is making me more money than my salary
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#15> 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)
What happens if it makes a mistake? How would you know?
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#16> 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)
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.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#17there are zero legitmate use cases? sure bro. you can say that to my claw which is making me more money than my salary
Bounties?
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#18It would’ve happened eventually anyway, but OpenClaw is basically what kickstarted the beginning of the end of token subsidies. It’s a almost begging to be used wastefully. And agents would miss and lose nothing without it. It’s devoid of a reason to exist.
I don't follow the thinking here. If you are using it for coding maybe, but the main use case of openclaw is as a personal assistant. I'm using a $10 a month minimax subscription for it, and I've never used more than 10% usage of a 5 hour window.
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#19> 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)
What happens if it makes a mistake? How would you know?
10/80/10
10% done by an assistant that’s been trained on the task (or a dev or me)
80% heavy lifting done by claw
10% review and corrections
Re: OpenClaw’s memory is unreliable, and you don’t know when it will break
#20I'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 through it's context and doesn't know to compact. Then it's just stuck. I can't wait till it matures or something more reliable comes along.