Progress UI
Background agents feel dead without progress.
A delivery tracker, not a mystery van.
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%
A delivery tracker, not a mystery van.
Key Takeaways
- 1.Long jobs need stages, checklists, and honest ETAs.
- 2.Map graph nodes or crew tasks to steps the human understands.
- 3.If a step is silent, say it is stalled.
- 4.Do not fake 100 percent then fail.
- 5.Background agents feel dead without progress.
Real Example
Scenario
Scenario (AG-UI & Agent UX): A user triggers a workflow that depends on Progress UI. - Long jobs need stages, checklists, and honest ETAs - Map graph nodes or crew tasks to steps the human understands - If a step is silent, say it is stalled - Do not fake 100 percent then fail. Your implementation handles the request, logs the step for observability, validates the output, and returns a grounded response — e.g. cutting manual work from 20 minutes to under 30 seconds.
What you would do
In AG-UI & Agent UX, apply Progress UI to this scenario: Scenario (AG-UI & Agent UX): A user triggers a workflow that depends on Progress UI. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.
Cheat Sheet
Quick recap
quick ref- •Long jobs need stages, checklists, and honest ETAs
- •Map graph nodes or crew tasks to steps the human understands
- •If a step is silent, say it is stalled
Common Mistakes
- ✕Skipping evaluation for Progress UI before production
- ✕No logging or tracing around agent progress ui steps
- ✕Ignoring cost and latency implications