[rimeice]

Very good points, but, I think this blog is pretty focussed on the developer use case for LLMs. It makes a lot more sense in chat style interfaces for connecting to non-dev tools or services with non technical users, if anything just from a UX perspective.

[nsedlet]

Yes, exactly. Not only can you not run CLIs in Chat interfaces, the services that non devs use often don’t even have CLIs to begin with.

Developers have a rich set of CLIs because they live in the terminal and built those tools for themselves.

[quectophoton]

Thank you, I was going to say something like this. I've been reading all the comments here and thinking, "do ChatGPT/LeChat/etc even allow running CLIs from their web or mobile interfaces?".

[jngiam1]

Exactly. and even if so, how are you going to safe guard tool access?

Imagine your favorite email provider has a CLI for reading and sending email - you're cool with the agent reading, but not sending. What are you going to do? Make 2 API keys? Make N API keys for each possible tool configuration you care about?

MCPs make this problem simple and easy to solve. CLIs don't.

I don't think OpenClaw will last that long without security solved well - and MCPs seem to be obvious solution, but actively rejected by that community.

[butcloudagent]

Supposedly, you make a Skill for it, but even that is out of scope for chat agents. I didn't scroll far, but I wouldn't be surprised more people in this thread have made the mistake of giving that answer.

[woctordho]

Interface for non-devs has evolved. We already have OpenClaw and things like Claude Cowork.