Agent Progress
Show what an AI agent is doing during long, multi-step tasks — steps, tool use and decisions — so users can follow, steer and stop it.
7 states5 edge casesDesktop + Mobile
01The problem
Agents research, browse, query data and edit files for minutes at a time. A spinner labelled “Thinking…” for three minutes gives users no reason to trust the result and no way to catch a wrong turn early. A raw log of every tool call is unreadable. Users need a view between the two: what the agent is doing, what it has done, and what it plans next.
02When to use
Use when
- Tasks that take more than ~10 seconds and involve several steps
- Agents that read or change data, call tools or browse
- Background jobs started by AI: research reports, bulk edits, migrations
Avoid when
- Single-shot responses — use the AI response pattern.
- Steps users can't understand or act on — summarise them instead.
03Recommended UX
Statecraft recommendation
Show the task as a short plan of human-readable steps, mark the current step as it runs, expand each completed step to see its sources and actions, and keep Stop — and where possible, Pause and Redirect — available throughout.
04Desktop behaviour
On desktop, the step list sits beside or above the result, with each step expandable to show tool calls, sources and changes.
Desktop rules
- Step labels in plain language: “Searching 3 contracts for renewal terms”.
- Current step animated subtly; completed steps show a check and duration.
- Actions that change data are listed explicitly in the summary.
- Stop always visible; Pause and “Add instruction” where supported.
05Mobile behaviour
On mobile, users rarely watch an agent run. Show a compact progress card and rely on notifications.
Mobile rules
3 mobile rules are included in Pro.
Statecraft Pro
Unlock the full pattern
Get the complete interaction flow, states, edge cases, mobile rules and implementation prompt.
- Interaction flow · 6 steps
- 3 mobile rules
- 7 states
- 5 edge cases with recommendations
- 4 microcopy comparisons
- Accessibility notes
- Developer notes
- Claude Code / Codex implementation prompt
Edge cases covered in this pattern
- Stopped after making changes
- Agent goes in circles
- Permission needed mid-task
- User leaves the page
- Steps contain sensitive data