Action 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.
Framing
The problem
Delegation feels unsafe when system actions disappear into a black box.
The pattern
Log every action in a reversible, filterable timeline.
Why chat breaks here
Chat transcripts are poor audit trails for state-changing operations.
Risks
Undo promises are dangerous if side effects are only partially reversible.
Avoid when
The system cannot provide trustworthy action history and reversal semantics.
Use when
The system performs reversible side effects users cannot easily reconstruct themselves.
DOPE evaluation
- Directability
- One-click undo on any individual action
- Observability
- Complete history of every agent action is always accessible
- Predictability
- Undo always works the same way regardless of action type
- Explainability
- Every logged action includes the reason and context that triggered it
In the wild
- Cursor Checkpoints (Cursor) — Automatic snapshots of agent edits, restorable per message; "Restore Checkpoint" button on hover. The clean per-action undo affordance.
- Claude Code Esc-Esc Rewind (Anthropic) — Double-Esc rewinds to a previous state; "ask Claude to undo" is documented. Action timeline as a first-class navigation primitive.
- Google Docs Version History (Google) — Non-AI grounding for the pattern. Every change recorded with diffs and timestamps; restore-to-version is the canonical undo affordance.
- Zapier Run History (Zapier) — Caveat — replay ≠ undo. Zap history shows every run with status badges; bulk replay is the closest commercial equivalent at the workflow level.
FAQ
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.
Related patterns
- Often paired with: Approval Gates — Audit captures every action; gates intercept the ones that need review first.
- Often paired with: Agentic Dashboard — Audit is the timeline view; the dashboard is the live operations view.
- Extends: Intent Preview — Preview shows what will happen; audit shows what did, with undo per step.