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.

▲

triyambakam 6 days ago | parent | next [-]

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.

	▲	djim1337 6 days ago \| parent [-]
		[dead]

▲

ivanjermakov 6 days ago | parent | prev | next [-]

> 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

▲

nsonha 2 days ago | parent | prev [-]

I don't know about other protocols but for this one it's because AI vendors decided to ship their agents in the form of TUIs, which are not programmable. They need to be wrapped into something to be build on top of.

I actually prefer something like opencode which is one TUI to rule them all (albeit still lacking in some area), it also provides an an SDK that abstracts away the underlying model.