Overview
How might we design blast radius visualization so people can trust and act on AI output?
When this pattern fits
- Essential for agentic tools, bulk automation platforms, and admin interfaces where fan-out actions need clear scope disclosure before execution to prevent accidental large-scale changes.
When to skip or lighten it
- Single-target actions where the radius is obviously one object.
- When accurate counts cannot be computed without already executing the mutation.
- Tiny hobby tools with no bulk operations.
States
State model coming soon
Key UX elements
Key UX elements coming soon
Anti-patterns to avoid
Starting a bulk run with only a spinner and no pre-count.
Underestimating counts that balloon mid-run with no re-confirmation.
Showing technical IDs without human-readable scope maps.
Allowing “select all matching” with no ceiling or sample preview.
How products use it
| Product | Implementation |
|---|---|
| Cursor / coding agents | Multi-file diff summaries before applying large changes. |
| CRM / support agents | Recipient or record counts before bulk message or update. |
| Cloud consoles | Resource-count previews before fleet-wide operations. |
| Design system migrate tools | Component instance counts before mass redesign apply. |
Implementation
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Blast Radius Visualization" AI interface design pattern.
Pattern Definition:Frequently asked questions
What is blast radius visualization in agent UX?
Blast radius visualization shows how wide an agent action will hit (counts and maps of affected files, records, or users) before the user approves execution.
What should a blast radius preview include?
Totals, major groupings (folders, teams, regions) a sample of items, and whether the action is reversible. Link to checkpoints when available.
How does blast radius relate to reversibility marking?
Blast radius answers “how much.” Reversibility answers “how undoable.” High radius plus irreversible should always raise approval friction.