What do you mean by "manage things"? If you mean adding/updating/completing tasks, why not just do that directly in the app? Or do you mean that it will take your tasks and perform them for you?

As an aside, app descriptions that just say "a lightweight alternative to X" are very unhelpful. That tells me nothing if I don't know what X does, and I don't want to have to go down a rabbit hole just to understand your product. It's particularly bad in this case, because even OpenClaw's Github page doesn't clearly tell me what it actually does; just that it's some kind of assistant that I can communicate with via WhatsApp etc. I appreciate that many people are already familiar with OpenClaw, but you shouldn't assume.

It's better if your app's description just tells me what it does in a direct way using plain language. It's fine to tell me it's an alternative to something, but that should be in addition to rather than instead of your own description.

I don't understand what this comment is trying to say.

> ... people consider building the tool from the instructions in the article ... so people can more easily build it

So what's the "less easy" way that people can build it from the instructions, if there's no source code?

I'm not sure that's a fair criticism. Many things require or benefit from something even more complex to make them (car -> factory, code -> IDE, text -> editor, food -> kitchen). I think the real debate here is that which is found in the other comments: do we want TUIs to look like GUIs?

Interesting idea, but:

> Design once, generate production-ready code for your framework of choice. Switch targets without touching your design. Alpha notice: Code export is not functional yet. We're actively working on it — check back soon.

In other words, it isn't at all usable right now. You can't produce a TUI with it, not even a limited one.