@threadplane/ag-ui · protocol adapter
One adapter. Seven backends.
Build the Angular UI once, on the AG-UI protocol — seven runtimes speak it today, and new ones work the day they ship. History and checkpoint behavior stays with your backend.
Talking to LangGraph Platform directly? See Choosing an adapter.
Already on LangGraph? See @threadplane/langgraph for native streaming, checkpoints, and the typed LangGraph SDK path.
Architecture
The adapter is the only part that speaks AG-UI
Everything above the seam is plain Angular — signals in, components out. toAgent() keeps the protocol at the boundary, so nothing in your UI changes when the backend does.
Runtime choice
Pick a backend. Keep the UI.
The AG-UI protocol decouples your agent runtime from your front-end. @threadplane/ag-ui wraps any AG-UI AbstractAgent into the runtime-neutral Agent contract that @threadplane/chat consumes — so the same Angular components ship against seven different runtimes.
Same primitives
Drop-in for everything @threadplane/chat ships.
provideAgent registers an AG-UI client and exposes the same Agent contract that @threadplane/langgraph provides. Chat rendering, status, tool calls, generative UI, and citations use the same Angular primitives; durable checkpointed threads and history depend on the backend protocol, so use @threadplane/langgraph when you need the native LangGraph thread API.
Field report
The last-mile gap in Angular AI.
Six production-readiness dimensions
17 pages
Streaming, persistence, tool calls, approvals, generative UI, testing
the six chapters
No vendor pitch — what we learned shipping it
free
Stop stalling on agentic Angular.
Install the framework, read the docs, and have a streaming chat in your app this afternoon.