abhis3798

Pelicans are deciding.

How is this adding to the discussion? The post in itself is quite informative.

Love this. I use a similar "ralph-loop" approach that starts with an approved plan and then hand it off to a coordinator which does it across 2 sessions (build and review for simplicity), with each session getting its own model.

That's interesting. I've been trying to build something similar as a side project: Hermes agent + plugins (MCP, skills, and agents) + a Postgres DB for auditing and state. The idea is essentially to make all of that a black box and present a simple “work queue” to a desk assistant.

Good validation that this is indeed a space the frontier firms are thinking about along similar lines.

If that's the only way you pay your bills then this article is not asking you to give away your software for free. It is for second jobbers.

I see remote MCP servers as a great interface to consume api responses. The idea that you essentially make your apis easily available to agents to bring in relevant context is a powerful one.

When folks say MCP is dead, I don't get it. What other alternatives exist in place of MCP? Arbitrary code via curl/sdks to call a remote endpoint?

On the other hand, my parents did not realise they needed to scroll down to read the article. :)

It is also one of the big reasons why Meta and Zuckerberg want to invest in AI. If AI companions are going to replace online friends, it makes total sense for Meta to invest in AI heavily.

This is a good rule of thumb, but what would be a good response to have interfaces because, "what if a new scenario comes up in the future"?