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) — 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.
- 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.
- 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 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.
- 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 — and Rubrik documents the capability, never the screen.
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.