Overview
How might we design reversibility marking so people can trust and act on AI output?
When this pattern fits
- Essential for agent interfaces, workflow automation, and any system that performs actions on behalf of users where surfacing reversibility helps calibrate approval attention to real risk.
When to skip or lighten it
- Flows with only reversible local edits where every tag would say the same thing.
- When you cannot honestly classify reversibility and labels would mislead.
- Emergency break-glass tools where speed beats taxonomy.
States
State model coming soon
Key UX elements
Key UX elements coming soon
Anti-patterns to avoid
Uniform primary buttons for send, delete, and tweak draft.
Calling something reversible when undo windows are tiny or unreliable.
Hiding irreversibility in tooltip copy only.
Marking irreversible actions lightly because they are “rare.”
How products use it
| Product | Implementation |
|---|---|
| ChatGPT / Gemini agents | Stronger confirmation chrome for send and external actions vs drafts. |
| Cursor Agent | Diff review emphasizes file-mutating steps before apply. |
| Banking / payments AI | Irreversible transfer confirmations distinct from simulation steps. |
| Email agents | Draft vs send clearly separated with send as irreversible. |
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 "Reversibility Marking" AI interface design pattern.
Pattern Definition:Frequently asked questions
What is reversibility marking in AI agent UX?
Reversibility marking labels each agent-proposed action by how easily it can be undone (fully, partially, or not at all) so users apply proportional scrutiny before approving.
What counts as irreversible?
Actions that cannot be cleanly undone: sent email, charged card, deleted production data without backup, public posts, or irrevocable legal submissions.
Should irreversible actions always require human approval?
Almost always yes for consumer and enterprise agents. Pair irreversible marking with approval workflows and, when possible, staged dry-runs.