31–40 of 127 posts
This looks related to Awesome CLIs/TUIs and terminal trove which has lots both CLI and TUI apps. Awesome TUIs: https://github.com/rothgar/awesome-tuis Awesome CLIs: https://github.com/agarrharr/awesome-cli-apps Terminal Trove: https://terminaltrove.com/ I guess this is another one shows that the CLI and Unix is coming back in 2026.
> Before your agent can do anything useful, it needs to know what tools are available. MCP’s answer is to dump the entire tool catalog into the conversation as JSON Schema. Every tool, every parameter, every option.
Because this simply isn't true anymore for the best clients, like Claude Code.
Similar to how Skills were designed[1] to be searchable without dumping everything into context, MCP tools can (and does in Claude Code) work the same way.
See https://www.anthropic.com/engineering/advanced-tool-use and https://x.com/trq212/status/2011523109871108570 and https://platform.claude.com/docs/en/agents-and-tools/tool-us...
[1] https://agentskills.io/specification#progressive-disclosure
ALSO... the permission boundary is clearer. You can whitelist commands, flags, working dir... it becomes manageable.
HOWEVER... packaging still matters. A “small” CLI that pulls in a giant runtime kills the benefit.
I want the discipline of small protocol plus big cache. Cheap models can summarize what they did and avoid full context in every step...
I've seen folks say that the future of using computers will be with an LLM that generates code on the fly to accomplish tasks. I think this is a bit ridiculous, but I do think that operating computers through natural language instructions is superior for a lot of cases and that seems to be where we are headed. I can see a future where software is built with a CLI interface underneath the (optional) GUI, letting an LL…
https://github.com/thellimist/thellimist.github.io/blob/mast...
https://github.com/thellimist/thellimist.github.io/blob/mast...
I dump a voice message, then blog comes out. Then I modify a bunch of things, and iterate 1-2 hours to get it right
Can LLMs compress those documents into smaller files that still retain the full context?
What do you mean?
Is this article from a while back? > Before your agent can do anything useful, it needs to know what tools are available. MCP’s answer is to dump the entire tool catalog into the conversation as JSON Schema. Every tool, every parameter, every option. Because this simply isn't true anymore for the best clients, like Claude Code. Similar to how Skills were designed[1] to be searchable without dumping everything into co…
Regardless, most MCPs are dumping. I know Cloudflare MCP is amazing but other 1000 useful MCPs are not.
True for coding agents running SotA models where you're the human-in-the-loop approving, less true for your deployed agents running on cheap models that you don't see what's being executed. But yeah, a concrete example is playwright-mcp vs playwright-cli: https://testcollab.com/blog/playwright-cli
I was actually thinking if I should support daemons just to support playwright. Now I don't have a use case for it
I've seen folks say that the future of using computers will be with an LLM that generates code on the fly to accomplish tasks. I think this is a bit ridiculous, but I do think that operating computers through natural language instructions is superior for a lot of cases and that seems to be where we are headed. I can see a future where software is built with a CLI interface underneath the (optional) GUI, letting an LL…
Ofc it is written by ai, I have a skill for it - https://github.com/thellimist/thellimist.github.io/blob/mast... https://github.com/thellimist/thellimist.github.io/blob/mast... I dump a voice message, then blog comes out. Then I modify a bunch of things, and iterate 1-2 hours to get it right