> bash-only tooling has higher success for bash-capable models, compared to using predefined tools for models that aren't good at bash?
No. The conclusion is that:
bash-capable models + bash-only tools > bash-capable models + predefined tools
In other words, MCP was just a bunch of bullshit that maybe helped a little bit until the models got good at bash, and now it's basically useless.
bash scripts, famously the last word in software engineering. all these castles of sand we've built atop the beautiful, perfect, timeless Bourne Again SHell. all for naught. fools!
What an intensely wrong comment. The trajectory of all software is the opposite of what you say. Bash is the entry level, everything flees.
At one point the web was bash scripts glued together. Now everything is brought into a runtime. Then brought into virtualized containers to isolate and hide from every other aspect of the operating system.
Eventually the agents will be on a runtime as well. The existing ones just aren't good enough. Rather than forking like made as a way of doing everything, exfiltration into arbitrary executables will be something more tightly controlled.
Organizations need better in-product control and auditing of the operations of the agent. They need it to work across OSes and not depend on the state of the machine, and not conflict with what else the developer is trying to do with it.
This unironically.
The design of pipes and the philosophy of simple composable tools tied together with the Unix shell has proven remarkably difficult to improve upon.
If you're just using bash scripts, where are you putting your enterprise secrets for external systems? How do you cleanly revoke them when a developer leaves your team?
MCP moves execution into a remote environment where it is easy for enterprises to secure access to internal and external systems. OAuth based access makes it easy to audit and revoke tokens. Central HTTP interface makes it trivially easy to monitor and audit.
They solve different problems.
[flagged]