←back to thread

Agent Client Protocol (ACP)

(agentclientprotocol.com)
270 points vinhnx | 3 comments | | HN request time: 0.593s | source
1. hari-trata ◴[] No.45075509[source]
I don’t see why we need so many protocols. In such a greenfield tech, many are eager to define rules. There’s already a protocol called AG-UI that does the similar thing, but even its purpose isn’t entirely clear to me.

Rather than rushing to create standards, I think the focus should be on building practical implementations, AI-centric UI components that actually help developers design more AI-friendly interfaces. Once the space matures and stabilizes, that’s when standardization will make more sense. Right now, it feels too early.

replies(2): >>45076471 #>>45076840 #
2. triyambakam ◴[] No.45076471[source]
I do agree it seems like too many protocols. I wonder why this couldn't be mcp. But regarding ag-ui in its name it's for UI - streaming from a backend agent to a client frontend. I actually have been working a lot with it this week.
replies(1): >>45077539 #
3. ivanjermakov ◴[] No.45076840[source]
> I don’t see why we need so many protocols

One great reason is to avoid M*N problem: https://matklad.github.io/2022/04/25/why-lsp.html