83 points yarapavan 1 hour ago 28 comments
uwagar 43 minutes ago | parent
ramblurr 40 minutes ago | parent
otabdeveloper4 39 minutes ago | parent
seanhunter 37 minutes ago | parent
_fw 41 minutes ago | parent
It’s suboptimal for the reasons the author outlines: but so is USB-C. So is NVME, so is HDMI.
We use these hugely successful technologies in spite of their flaws because they’re widely compatible and easy for the end user.
That’s why MCP is everywhere. It might not be performant, robust and uniform but it WILL get better over time.
And I’d much rather have the broad MCP ecosystem that we have now than seven or eight different “optimal” ways of plugging in an LLM to something useful.
mi_lk 38 minutes ago | parent
If you are a Pi user it may be better to just ask your agent to explain https://github.com/earendil-works/pi/pull/10040
the_mitsuhiko 36 minutes ago | parent
If we fail to explain it, then we need to do a better job explaining it :)
mi_lk 33 minutes ago | parent
the_mitsuhiko 30 minutes ago | parent
gritzko 30 minutes ago | parent
ppsreejith 38 minutes ago | parent
hobofan 29 minutes ago | parent
While we are waiting on that to become stabilized, we implemented a inspired/co-evolved way to do that in our tool[0], where you mark individual fields in the request/response schema as being file payloads, so that file exchange can be properly orchestrated by the harness and doesn't pollute the context. We just do inline base64 uploads of the required payloads, which in practice we've seen to work quite will until ~100MB files (which is otherwise also the size limit we usually recommend for file processed).
It's annoying that it's not stabilized yet, but for most bigger customers we've seen, they implement 80% of the MCP servers they connect in-house, so doing adjustments to the tool surface, and metadata has been less of a pain for them than we expected.
[0]: https://erato.chat/docs/features/mcp_servers#file-support
wren6991 36 minutes ago | parent
There's just something that bothers me about this. Normally if LLMs want to compose multiple operations, they have the perfect tool for this: bash, or whatever other OS shell is available. It's why I was always confused by Codemode-type constructs for direct chaining of tool calls; see also the way highly-RL'd modern models will fall back to sed or python for complex file edits.
It seems like Codemode is raised here as the perfect tool for chaining or composing MCPs, but isn't that backwards? LLMs are already given the perfect tool for that, and the problem is that MCPs aren't exposed to that tool.
hobofan 22 minutes ago | parent
I many scenarios, e.g. running the harness server-side, as is the case for chat interfaces, you don't really want to expose OS shell access as that opens up a huge security attack surface.
OleksandrC 33 minutes ago | parent
If you feel that Pi has been drifting away from its original vision, try hax (https://usehax.dev/) - you might like it.
blamestross 30 minutes ago | parent
Just generate CLI tools, with docs, from MCP servers on demand.
carlsborg 30 minutes ago | parent
KronisLV 28 minutes ago | parent
I suspect that a smart model driving multiple dumber models for work and then using sub-agents with the same smart model for adversarial review will be a pretty common pattern.
Personally, I got a bit confused about Pi having most of that stuff as plugins since I remember how much of a mess Eclipse was where so much was just loosely fitting together plugins and just went with OpenCode since it covers most of my needs out of the box. Guess that might also be a sign of me getting older, because my IDEs and desktop environments are all closer to stock too.
embedding-shape 20 minutes ago | parent
Like sub-agents, you could just instruct pi/any harness with a user prompt/system prompt to start new invocations of itself, if you share what the exact command is, and pi or any other harness will do their own poor man's version of sub-agent via standard unix programs.
buserror 19 minutes ago | parent
sunaookami 8 minutes ago | parent
KronisLV 4 minutes ago | parent
Using sub-agents for example also lets me decrease the default context size in Claude Code instead of running at the full 1M like:
/autocompact 420k
or deal with Codex's 258k tokens (seriously quite tiny by modern standards).Sha1rholder 21 minutes ago | parent
embedding-shape 19 minutes ago | parent
NichoPaolucci 17 minutes ago | parent
Another retrospect note, "No MCP" appears to be the first icon on their front page - not sure how I missed that.
Imagine my surprise reading this!
croes 15 minutes ago | parent
And you didn’t remember that when you said no to MCP?
No, no MCP for now?
aussieguy1234 12 minutes ago | parent
I find this approach is easier to debug and I can also use the tool myself to ensure it's working well.
melodyogonna 6 minutes ago | parent