Angular Apps Don’t Need Another Chatbot: Building Agentic UI Workflows With TypeScript

The useful part

The model becomes a planner over explicit application capabilities, while Angular remains responsible for state, rendering, validation, authorization boundaries, and interaction. Chat Is an Output Channel, Not the Application Model The key design shift is to model an agent run as a workflow rather than a sequence of messages. A purchasing screen, for example, can expose inventory lookup, draft modification, approval, and submission as capabilities.

How it works

• AG-UI follows this direction by defining lifecycle, text, tool-call, and state events instead of treating every interaction as plain assistant text.
• Tool calls are represented through structured events, allowing a frontend to represent work in progress without attempting to parse model prose into application behavior.
• Natural language may start the flow, but the resulting interface should remain a normal application UI: editable fields, status indicators, review cards, validation messages, and explicit confirmation controls.