Agent UX
Production agents are products. Products need UX, not just a model score.
Airline app: delays, receipts, talk to an agent — not a blinking cursor.
Visual Workflows
Start here — scroll inside each diagram frame to explore, then use + / − to zoom up to 200% if needed.
Overview
Scroll inside the frame to explore · use + / − to zoom up to 200%
Scroll inside the frame to explore · use + / − to zoom up to 200%
This turn
Scroll inside the frame to explore · use + / − to zoom up to 200%
Airline app: delays, receipts, talk to an agent — not a blinking cursor.
Key Takeaways
- 1.Agent UX is empty states, errors, retries, citations, artifacts, and handoff to a human.
- 2.Citations beat confidence theater.
- 3.Errors should say what failed and what the user can do.
- 4.Production agents are products.
- 5.Products need UX, not just a model score.
Real Example
Scenario
Airline app: delays, receipts, talk to an agent — not a blinking cursor.
What you would do
In AG-UI & Agent UX, apply Agent UX to this scenario: Airline app: delays, receipts, talk to an agent — not a blinking cursor. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.
Cheat Sheet
Quick recap
quick ref- •Agent UX is empty states, errors, retries, citations, artifacts, and handoff to a human
- •Citations beat confidence theater
- •Errors should say what failed and what the user can do
Common Mistakes
- ✕Skipping evaluation for Agent UX before production
- ✕No logging or tracing around agent ux steps
- ✕Ignoring cost and latency implications