I mean, in not vibecoding it yourself you are already saving tokens... Personally, I see no benefit in having an instance of something like this... so, I wouldn't spend tokens, and I wouldn't spend server-time, or any other resource into it, but a lot of people seem to have found a really nice alternative to actually having to use their brains during the day.

> a lot of people seem to have found a really nice alternative to actually having to use their brains during the day.

Or have they have found a way to use their brains on what they deem as more useful, and less on what is rote?

I do see the potential in something like OpenClaw, personally, but more as a kind of interface for a collection of small isolated automations that _could_ be loosely connected via some type of memory bank (whether that's a RAG or just text files or a database or whatever). Not all of these will require LLMs and certainly none of them will require vibecoding at all if you have infinite time; But the reality is I don't have infinite time, and if I have 300 small ideas and I can only implement my like 10 of them a week by myself, I'd personally rather automate 30 more than just not have them at all, you know?

But I am talking about shell scripts here, cronjobs, maybe small background services. And I would never dare publish these as public applications or products. Both because I feel no pride about having "made" these - because, you know, I haven't, the AI did - and because they just aren't public facing interfaces.

I think the main issue at the moment is that so many devs are pretending that these vibecoded projects are "products". They are not. They are tailor-made, non-recyclable throwaway software for one person: The creator. I just see no world at the moment where I have any plausible reason to use someone else's vibecoded software.