Funny how you made the name Micro / MU while there is a major company called Micron with the stock ticker MU. Intentional I guess?
Show HN: Mu – Tools for Agents
11–20 of 30 posts
Re: Show HN: Mu – Tools for Agents
#12but... why? you almost never want these tools in any given session, and creating any of them can be done simply with Claude. looking at the PRs, it seems like that is exactly what's happening. i guess this is my generic problem with MCP releases, who are they for and why?
for high effort MCPs I see the reason. Big MCPs take major tokens to produce and test (if you're just telling an LLM to handle it) , it's nice if there is a high quality well tested thing out there to just plug into.
for things that are essentially a skill compendium, I see less reason..
Re: Show HN: Mu – Tools for Agents
#13I think if nothing else the technical facing value proposition should be human written.
Communicating is hard but that’s the point, takes a lot of effort to close the gap between a new and skeptical user and your vision.
Devs will not be able to bypass the PTSD of reading Claude prose.
Re: Show HN: Mu – Tools for Agents
#14I honestly don't really get MCPs. They're like all the bad design choices of LSP multiplied by 5
Re: Show HN: Mu – Tools for Agents
#15Not to be confused with Mü, the card game!
or Mu, the lost continent.
Re: Show HN: Mu – Tools for Agents
#16I think if nothing else the technical facing value proposition should be human written. Communicating is hard but that’s the point, takes a lot of effort to close the gap between a new and skeptical user and your vision. Devs will not be able to bypass the PTSD of reading Claude prose .
Amen. If i see a 5000 line README i am closing the tab.
Re: Show HN: Mu – Tools for Agents
#17[dead]
Re: Show HN: Mu – Tools for Agents
#18I think if nothing else the technical facing value proposition should be human written. Communicating is hard but that’s the point, takes a lot of effort to close the gap between a new and skeptical user and your vision. Devs will not be able to bypass the PTSD of reading Claude prose .
Amen. If i see a 5000 line README i am closing the tab.
I have in my CLAUDE/AGENTS.md to be concise with both chat output and documentation.
Yet still I get walls of text often. It's so fatiguing.
Re: Show HN: Mu – Tools for Agents
#19Genuine question rather than a criticism: what do the tools actually execute in?
I spent last week asking people running local agents what their generated code runs inside, and the answer was consistently "nothing" - same filesystem, same network, same credentials as the agent itself. One person reviews everything with a second model and then reads it himself, which is the most careful answer I got and still isn't a boundary.
That's fine while a tool is reading a file. It stops being fine the moment the tool is "run this". Does Mu draw a line there, or is it left to the host?
Re: Show HN: Mu – Tools for Agents
#20Earlier quoted context omitted.
Amen. If i see a 5000 line README i am closing the tab.
I have in my CLAUDE/AGENTS.md to be concise with both chat output and documentation. Yet still I get walls of text often. It's so fatiguing.
Root agents.md should be human authored. Even if you copy and paste into it. That's your only lasting thread into having any intuition on the behavior that will result