eglintondust

I think of the mcp as another UI. You have your human UI and your robot UI and the API serves both. Makes sense when the actions you want the agent to make are not exactly 1:1 mapping to an endpoint.

But yeah of course an agent can usually figure out how to use your API, can just take more time and tokens.

My password manager won't do that either

So can I finally download more RAM?

I haven't monitored CPU usage so closely, but seems to get heavy with basic tool calls and editing. Memory usage definitely is out of hand, have an idle session right now eating 500MB

This line of thinking I feel like assumes it's the only program running on your computer. Using less of my CPU and memory means my computer can do more things in parallel, or even run more instances of the harness. My laptop is sweating when I got 5+ claude code sessions running.

Coding agents have been been such a blessing for my Emacs setup. Only getting more psyched about emacs. It was pretty good before but my elisp skills never really advanced much beyond gluing together existing libraries and copy pasted snippets. Now I'm having a blast vibecoding tools I could only dream of before, beyond what I even knew was possible.

You just don't inject the real secret unless hostname/whatever rule matches the request, right? I don't know if that's how this works but it's my assumption.

I'm inspired by this website. It's incredible.

There is value for the person maintaining this library cause they want it that way. If you develop a useful library and give it away for free then all power to you if you want to rearrange the furniture every 6 months. I'll roll with it.

A good query builder is more important than ORM imo. That's what I like about sqlalchemy. The query builder pretty much maps 1:1 to SQL and you can use it with or without the ORM mapping. Most of my projects have a mix of both along with plain SQL for some of the meatier queries.

A good query builder is more important than ORM imo. That's what I like about sqlalchemy. The query builder pretty much maps 1:1 to SQL and you can use it with or without the ORM mapping. Most of my projects have a mix of both along with plain SQL for some of the meatier queries.