Dallas skyline illustration

CYC26 / Frontend

Architecting AI in Angular: WebMCP, A2UI, and the Agent Experience

First we optimized for UX, then DX, and now there's AX - the Agent Experience crashing the party. AI assistants are increasingly showing up to use our apps, and right now most of them get in by screenshotting the DOM and guessing where to click. There's a better way. WebMCP lets your Angular app hand agents a clean set of callable tools, and A2UI lets agents hand back real, reactive UI instead of another wall of chat text. In this session we'll architect an Angular app for this shiny (and slightly experimental) new world. We'll walk through the modes of agent interaction, from quiet background data retrieval to rich, agent-generated interfaces, and look at a few ways to wire WebMCP into Angular through navigator.modelContext. Then we'll bring in A2UI so agents can return reactive component trees that your app renders natively, with your styling and accessibility along for the ride. You'll leave knowing how to register tools, render agent-driven UI, and start thinking about your app's tool surface alongside its visual one. You'll also get a clear-eyed sense of what's production-ready today and what's still gloriously bleeding-edge.

Session abstract

What you’ll learn

First we optimized for UX, then DX, and now there's AX - the Agent Experience crashing the party. AI assistants are increasingly showing up to use our apps, and right now most of them get in by screenshotting the DOM and guessing where to click. There's a better way. WebMCP lets your Angular app hand agents a clean set of callable tools, and A2UI lets agents hand back real, reactive UI instead of another wall of chat text. In this session we'll architect an Angular app for this shiny (and slightly experimental) new world. We'll walk through the modes of agent interaction, from quiet background data retrieval to rich, agent-generated interfaces, and look at a few ways to wire WebMCP into Angular through navigator.modelContext. Then we'll bring in A2UI so agents can return reactive component trees that your app renders natively, with your styling and accessibility along for the ride. You'll leave knowing how to register tools, render agent-driven UI, and start thinking about your app's tool surface alongside its visual one. You'll also get a clear-eyed sense of what's production-ready today and what's still gloriously bleeding-edge.