Latch · an A2UI catalog
Ask only when you must.
Confirm before you act.
Components for agents that already have a goal and the reference material. They stay quiet, name who is handling the work, and wait for a person before anything consequential.
Reference Offsite brief · 12 people, Lisbon, a week in May
Plan a team offsite for 12 in Lisbon in May
Planner
Reading the briefUsing 12 people, Lisbon, MayOne fact missing: budget
The catalog
- ConfirmCardA consequential action is a review, not a button.
- ClarifyFormAsk only for the one fact that blocks the work, then collapse it.
- HandoffCardName who is handling the request, and log a wrong handoff.
- ThinkingStepsShow the work as quiet prose. No card, no timer.
- ChoiceListA decision is a list with one selected, not a wall of buttons.
- ItemSummaryQuantity and money stay visible and editable until confirm.
- StatusPillA status is a short sentence, not a color.
- CitationA claim that depends on a source carries the source with it.
A catalog, not a chat kit
Latch does not stream tokens, store threads, or pick a model. An agent sends A2UI messages. A client that agrees on latch://catalog/v1 renders them with these components. The basic A2UI catalog still covers text, fields, and buttons. Latch covers the judgment around an action.
Read the comparison with A2UI, AI Elements, CopilotKit, assistant-ui, the OpenAI Apps SDK, and Thesys C1.