ADK-Rust 2 nativeFive UI protocols

One agent.
Every interface.

Build interactive agent experiences once, then deliver them through A2UI, AG-UI, MCP Apps, AWP, or the classic ADK renderer. Brand kits, multi-page applications, streaming updates, and safe 3D scenes share one typed UI system.

Explore the examples Read the quick start

05: delivery profiles
06: independent examples
01: typed renderer contract

Protocol-native surface delivery

Protocol matrix

Choose how your UI travels.

Keep the agent and its interface contract. Change only the delivery boundary.

Preferred

A2UI

v0.9.1 + v1 RC

Structured surfaces, catalogs, data models, validated actions, and correlated responses.

Native stream

AG-UI

Stable event families

Run lifecycle, text, reasoning, tool calls, activities, and protocol-native input.

MCP

Bridge aware

MCP Apps

2026-01-26

Negotiated app capabilities, ui:// resources, host context, messages, and notifications.

AWP

Optional

AWP

v1.0

Dual-user HTML and structured output with capability export and adaptive bandwidth.

ADK

Legacy

Classic ADK

Compatibility profile

A stable migration path for existing renderers while protocol-native delivery becomes the default.

Capability claims distinguish supported, partial, candidate, host-owned, planned, and legacy behavior. Protocol support is a versioned contract, not a logo strip.

Interactive workspace

See the protocol. Inspect the result.

Agent UI Studio keeps prompts, rendered surfaces, lifecycle events, output, and reasoning in one observable workspace.

Agent UI StudioADK-Rust 2

ADK UI Studio showing scenario prompts, a generated application canvas, protocol selection, and runtime event inspection

Generate complete applications

Compose routed pages, preserve visited state, and carry one application graph across protocol surfaces.

Drive design from brand kits

Use approved tokens, assets, recipes, and provenance instead of accepting interchangeable component defaults.

Observe every boundary

Inspect streams, actions, reasoning, quality signals, and bridge state without hiding protocol behavior.

Independent examples

See one capability at a time.

Six zero-server fixtures render through the public React package. Each example isolates a product-grade interaction rather than showing another generic dashboard.

Decision workspace

Incident command

Dense evidence, live operations data, editable action scope, and explicit human approval.

Decision supportCharts + tablesGuarded action

AG-UI · A2UIInspect source

Adaptive form

Guided support

Known-state reuse, native validation, progress, and a review boundary before submission.

Adaptive formsValidationReview step

A2UIInspect source

Multi-page application

Release room

Whole-page generation with local routes, mounted visited pages, and preserved rollout state.

Multi-page appPreserved stateLocal routing

A2UI · AG-UI · MCP AppsInspect source

Design-system generation

Brand concierge

Approved semantic tokens and assets drive a distinctive interface instead of generic defaults.

Brand kitsSemantic tokensGuided choice

MCP Apps · A2UIInspect source

Declarative 3D

Spatial logistics

Semantic scenes, safe materials, labelled actions, and an accessible non-3D fallback.

Declarative 3DLazy rendererSafe assets

A2UI · MCP AppsInspect source

Incremental UI

Streaming operations

Targeted patch, replace, append, and remove operations keep surrounding state stable.

Streaming updatesPatch + replaceStable state

AG-UI · A2UIInspect source

Start with a working surface

Your Rust agent can ship the interface too.

Add the Rust crate at the agent boundary and the React package at the host boundary. Start with A2UI, then select AG-UI, MCP Apps, or AWP where the integration requires it.

Open quick start Read the ADK-Rust guide

Rust agentcargo add adk-ui

React hostnpm install @zavora-ai/adk-ui-react

Sourcegithub.com/zavora-ai/adk-ui

ADK UI 2.1

Open-source generative interfaces for the ADK-Rust ecosystem.

Apache 2.0 · GitHub ↗

One agent.Every interface.