←back to thread

A PM's Guide to AI Agent Architecture

(www.productcurious.com)
205 points umangsehgal93 | 1 comments | 04 Sep 25 16:45 UTC | HN request time: 0s | source
Show context
gillesjacobs ◴[04 Sep 25 21:30 UTC] No.45132434[source]▶
Nice framing for PMs, but technically it is way too rosy. MCP is real but still full of low utility services and security issues, so “skills as plug-ins” is not production ready. A2A protocols were only just announced this year (Google, etc.) and actual inter-agent interoperability is still research grade, with debugging across agents being a nightmare. Orchestration layers (skills, workflows, multi-agent) look clean in diagrams but turn into brittle state machines under load. LLM “confidence scores” are basically uncalibrated logits dressed up as probabilities.

In short: nice industry roadmap, but we are nowhere near robust, trustworthy multi-agent systems yet.

replies(1): >>45132774 #
1. gabriel666smith ◴[04 Sep 25 22:07 UTC] No.45132774[source]▶
The idea of giving an LLM with a tool any kind of control over an actual user's account remains (though you put this more elegantly) batshit insane to me.

Even assuming you've correctly auth'd the user contacting you (big assumption!), allowing that user to very literally prompt a 'semi-confident thing with tools' - however many layers of abstraction away the tool is - feels very, very far away from a real-world, sensible implementation right now.

Just shoot the tool prompts over to a human operator, if it's so necessary! Sense-check!