What problem does it solve?
Frontend applications often need to present dynamic interactive components (buttons, forms, lists) that, when interacted with, must communicate back to the Agent backend to continue workflows. A2UI provides a dedicated pathway to render these components and handle user-driven signals, keeping UI logic separate from the Agent core.
Core Features & Use Cases
- Output an interactive component tree to the frontend using ui_render; user actions emit top-level signals that drive the Agent's next steps.
- Supports common widgets such as Button, TextField, ListItem, Chip, and Card, enabling rapid creation of guided UI flows without embedding logic in prompts.
- Useful for scenarios like form submissions, multi-step dialogs, and decision points where backend decisions depend on user input.
Quick Start
Use ui_render to submit a component tree for the current Agent step and respond to the resulting signal to progress the workflow.