Set up the walkback time machine in a project directory (and gitignore its snapshots). Run once before checkpointing.

Mark a point in time you can rewind to. Call this BEFORE you start making changes.

Capture a file's (or whole directory's) current state BEFORE you create, modify, or delete it. This is what makes the change reversible. Call it on every path you're about to touch. Directories are captured recursively. Paths outside the project are refused.

Log a POST/PUT/PATCH/DELETE the agent made, with an optional compensating request (e.g. a DELETE that reverses a POST) so it can be undone later.

Show every effect recorded since the most recent checkpoint.

List every checkpoint and effect in order.

Reverse every change made since a checkpoint (the latest one by default). Files, directories, and symlinks are restored exactly; network/shell effects are listed for manual handling. If any step fails, the journal is left intact so you can safely retry. Use walkback_redo to reverse a rollback.

Re-apply the changes that the most recent walkback_rollback reversed, and re-extend the history so you can roll back again.

A PR-style diff of every file changed since the last checkpoint — the reviewable 'here's exactly what I did' surface. Built from walkback's own before-snapshots.

Reverse just a single file (the most recent change to it), leaving every other change since the checkpoint in place. The opposite of rollback's all-or-nothing.

Record the command that reverses something the agent did to an external system — a cloud resource (e.g. 'terraform destroy', 'aws s3 rb s3://bucket') or a database change (e.g. an inverse SQL via psql). walkback_compensate will run it (dry-run gated). Works with any tool. For UPDATE/DELETE you must capture the prior values to build the inverse — walkback runs what you give it.

Execute the compensating actions recorded since the last checkpoint: the reversing HTTP request (DELETE undoes POST, refund undoes charge) AND any recorded reversal commands (cloud teardown, inverse SQL). Dry-run by default — pass execute=true to fire them. Most-recent-first.

Hold an email instead of sending it immediately: it becomes a Gmail DRAFT that has gone nowhere. Release it with walkback_email_release to actually deliver, or walkback_email_cancel to truly unsend it (it never reaches the recipient). Needs GMAIL_ACCESS_TOKEN.

Actually send the held draft(s). After this the email is delivered and CANNOT be recalled.

Delete the held draft(s) so they never go out — a true unsend, possible only because they were never delivered. Does nothing to emails already released.

Show emails staged but not yet released — these can still be cancelled.