Delegation feels unsafe when system actions disappear into a black box.
← Back to patterns
Google
Human Oversight-by-Design for Accessible Generative IUIs The Design of Everyday Things Computer Use · Claude 3.5 Sonnet Guidelines for Human-AI Interaction (HAX Toolkit, G1-G18)
Agent Workflow
EmergingAction Audit & Undo
Every Action Visible, Every Action Reversible
A persistent timeline of every agent action with per-action undo buttons. Filter by type, batch undo, and see exactly what changed. The psychological safety net that enables delegation.
Metaphor
Flight Recorder
Interaction
Timeline, Filterable
Use case
File Operations, Automated Workflows, Agent Supervision
Failure mode
Linear History
Control mechanisms
Timeline Log · Per-Action Undo · Batch Undo · Filters
Reference examples
Cursor Checkpoints · Claude Code Esc-Esc Rewind · Google Docs Version History · Zapier Run History · Rubrik Agent Cloud (Agent Rewind)
Interactive Example
The live side-by-side is the comparison.
This prototype already contains the contrast between chat and the pattern response. It stands as the primary comparison surface for this page.
Delegation needs a way back, not just a way forward.
When an agent's actions vanish into a black box, every delegation is a leap of faith. A chat transcript is a record of what was said, not a record of what changed to the world's state, so the user cannot answer the only question that matters after the fact: what exactly did this thing do, and can I take it back?
Action Audit logs every action to a persistent, filterable timeline with per-action undo, batch reversal, and the context that triggered each step. The reversibility is what unlocks the behavior: a clean exit on every action lowers the cost of saying yes, so users delegate more because mistakes are recoverable rather than final.
People act boldly when they know how to undo it — the emergency exit is what makes the room feel safe.
DOPE Lens
How this pattern improves AI interaction quality.
Observability
Complete history of every agent action is always accessible
Directability
One-click undo on any individual action
Predictability
Undo always works the same way regardless of action type
Explainability
Every logged action includes the reason and context that triggered it
Fit
Where it earns its place.
Use it
when
when
The system performs reversible side effects users cannot easily reconstruct themselves.
Avoid
when
when
The system cannot provide trustworthy action history and reversal semantics.
In the wild
Where this pattern already ships.
The pattern is shipping but still maturing across products. Entries below show how different teams have approached it; expect variation as the space settles.
Cursor Checkpoints
Cursor
Snapshots of the whole codebase, taken before "significant changes", restorable from the chat timeline or the Restore Checkpoint button on a prior request. Restore reverts every modified file to that point — a per-message rollback, not per-action undo; checkpoints before each individual file edit remain an open feature request.
Visit Cursor ↗
Claude Code Esc-Esc Rewind
Anthropic
/rewind — or Esc twice on an empty prompt — opens a menu of every prompt in the session, with separate Restore code and Restore conversation actions. One checkpoint per prompt, not per action, and the docs concede the holes: bash-command changes, subagent edits and your own manual edits are not tracked.
Visit Anthropic ↗
Google Docs Version History
Non-AI grounding for the pattern. Every change recorded with diffs and timestamps; restore-to-version is the canonical undo affordance.
Visit Google ↗
Zapier Run History
Zapier
Caveat — replay is not undo. Zap history lists every run with a status badge and filters by status, date, owner, folder, app and Zap; runs replay singly or in bulk, with non-errored replays gated to paid plans. The only card here that ships the filterable half — and none of it reverses a side effect.
Visit Zapier ↗
Rubrik Agent Cloud (Agent Rewind)
Rubrik
The one product claiming both halves at once: an immutable trail of every agent action from originating prompt to tool call, plus selective rollback that reverses a single file, config or database change instead of restoring the whole system. An enterprise console for IT and security teams, not the acting user's timeline. The Agent Rewind launch blog shows the drawer for one logged action: the agent's own explanation, a rewind plan, and a REWIND button beside a pair of arrow buttons.
Visit Rubrik ↗
Research Frame
Why this pattern exists, and where it breaks.
Log every action in a reversible, filterable timeline.
Chat transcripts are poor audit trails for state-changing operations.
Undo promises are dangerous if side effects are only partially reversible.
Common questions
What people ask about this pattern.
When should I use the Action Audit & Undo pattern?
+
The system performs reversible side effects users cannot easily reconstruct themselves.
When should I avoid the Action Audit & Undo pattern?
+
The system cannot provide trustworthy action history and reversal semantics.
What problem does Action Audit & Undo solve?
+
Delegation feels unsafe when system actions disappear into a black box.
Why is chat the wrong fit for this?
+
Chat transcripts are poor audit trails for state-changing operations.
Grounded in Research
Not just opinion.
The papers, guidelines, and usability studies this pattern rests on.
Blessing Jerry, Lourdes Moreno, Paloma Martínez
Universidad Carlos III de Madrid · 2026
Argues for human oversight as a first-class design principle in generative AI interfaces — not an afterthought. Frames accessibility as part of the oversight surface, not a separate concern.
Don Norman
Basic Books · revised 2013 edition · 1988
The feedback and visibility principles every interface inherits. Output Undo, Action Audit, and most Observability patterns are direct applications of "the system must reflect its state back to the user."
Anthropic
Anthropic · product announcement + research note · 2024
First production model trained to operate a computer interface directly. Turns every UI question (preview, audit, gates, friction) into a concrete shipping setting and provides the destructive-action-confirmation primitive several patterns build on.
Saleema Amershi et al.
Microsoft Research · 2019 · refreshed 2026-07
The canonical 18-guideline taxonomy for human-AI interaction. Strongest anchors: G9 efficient correction, G11 why-did-it-do-that, G17 global controls. Its three zero-coverage guidelines — G6 bias mitigation, G14 cautious updates, G18 change notification — became this library's Bias Flag and Model Changelog patterns in July 2026. Nearly the whole Agent Workflow category sits outside its 2019 single-assistant frame.
Related Patterns
Curated connections, not just neighbors.
Hand-picked relationships — what this pattern pairs with in practice, what it replaces, what it builds on, and what builds on it.
Often paired with
Approval Gates
Action Audit & Undo captures every action; Approval Gates intercept the ones that need review first.
Often paired with
Agentic Dashboard
Agentic Dashboard lets you pause agents mid-run; Action Audit & Undo reverses what they already did, step by step.
Often paired with
Intent Preview
Intent Preview shows what will happen; Action Audit & Undo shows what did, with undo per step.