Cool to see lots of people independently come to "CLIs are all you need". I'm still not sure if it's a short-term bandaid because agents are so good at terminal use or if it's part of a longer term trend but it's definitely felt much more seamless to me then MCPs.
(my one of many contribution https://github.com/caesarnine/binsmith)
I am also not sure if MCP will eventually be fixed to allow more control over context, or if the CLI approach really is the future for Agentic AI.
Nevertheless, I prefer the CLI for other reasons: it is built for humans and is much easier to debug.
Have a look at code mode mcp. https://github.com/universal-tool-calling-protocol/code-mode
100% - sharing CLIs with the agent has felt like another channel to interact with them once I’ve done it enough, like a task manager the agent and I can both use using the same interface
Thank you for posting binsmith, I've built something similar over the past few days and you've made some great decisions in here
MCP let's you hide secrets from the LLM
you can do same thing with cli via env vars no?
Yes, I'm using Dagger and it has great secret support, obfuscating them even if the agent, for example, cats the contents of a key file, it will never be able to read or print the secret value itself
tl;Dr there are a lot of ways to keep secret contents away from your agent, some without actually having to keep them "physically" separate
Hey this looks cool. So each agent or session is one thread. Nice. I like it.