A2UI (Agent-to-User Interface) comprises a protocol designed for low-latency streaming, web and mobile renderers, and agent SDKs for Python, TypeScript, and Dart: agents generate interfaces and data according to schemas, while the rendering side displays them using native components from Lit, Angular, React, Flutter, SwiftUI, and Jetpack Compose, with the component catalog locked by application developers. The SDK supports the A2A protocol and Google ADK, and the MCP component catalog can render interfaces returned by MCP tools; the official website lists protocol version v1.0, and the Python core package 11 was released on 17 as 0.7.0.
Why it matters Agents can only assemble components registered by developers and do not execute arbitrary code; the same interface description can be displayed natively on web, Android, and Apple platforms.
Star count 17729 (+25 / 24h)
Reasons
- 25 new stars in 24 hours, total stars 17729, ranked #17 on Trendshift for the day (indicating attention only); the README specifies an Apache 2.0 license
- The official website states that ByteDance, Atlassian, Gemini, and Google Cloud are already using it in their products
Usage
- Without installation, you can first open A2UI Composer (a2ui-project.github.io/composer) to visually generate interface JSON and paste it into the prompt of any agent; for formal integration, follow the Quickstart at a2ui.org to set up a frontend-backend example, or run npx skills add a2ui-project/a2ui to install the skill for coding agents
Risks
- Some packages, such as the VegaChart component catalog, have not yet been released and can only be used from source; protocol v1.1 is still gathering requirements, so interfaces may change
- The quality of the interface still depends on the data generated by the model, and the generation quality evaluation tools mentioned in the official roadmap are not yet available