I only skimmed the OpenClaw post, but unless I completely misunderstood the README in their GitHub repo, to me the benefits are stupidly obvious, and I was actually planning to look at it closer over the weekend.
The value proposition I saw is: hooking up one or more LLMs via API (BYOK) to one or more popular chat apps, via self-hostable control plane. Plus some bells and whistles.
The part about chat integration is something that I wanted to have even before LLMs were a thing, because I hate modern communication apps with burning fashion. All popular IM apps in particular[0] are just user-hostile prisons whose vendors go out of their way to make interoperability and end-user automation impossible. There's too much of that, and for a decade or more I dreamed of centralizing all these independent networks for myself in a single app. I considered working on the problem a few times, but the barriers vendors put up were always too much for my patience.
So here I thought, maybe someone solved this problem. That alone would be valuable.
Having an LLM, especially BYOK, in your main IM app? That's a no-brainer to me too; I think it's a travesty this is not a default feature already. Especially these days, as a parent, I find a good chunk of my IM use involves manually copy-pasting messages and photos to some LLM to turn them into reminders and calendar invites. And that's one of many use cases I have for tight IM/LLM integration.
So here I thought maybe this project will be a quick and easy way to finally get a sane, end-user-programmable chat experience. Shame to see it might be vaporware and/or a scam.
--
[0] - Excepting Telegram, which has a host of other problems - but I'd be fine living with them; unfortunately, everyone I need to communicate with uses either WhatsApp or Facebook Messenger these days.