Review what changed

See what a session did

Inspect the next primary model request without sending it: /preview-request.

A session receipt lists the files changed, the commands run and who approved each step, and ends with what it did not record. It shows no cost or token line: the footer and /cost show cost as a figure or as "unknown". Review receipts below cover a separate code review.

/receipts
/receipts json

codewhale receipts --last --format md

GET /v1/threads/{id}/receipt
GET /v1/threads/{id}/turns/{turn_id}/receipt

These surfaces only read records. They never call a provider, run tools or change session state.

Note: A Runtime receipt does not itemize files changed by shell commands. The terminal can report changes from its turn snapshots; older records may omit who decided an approval.

See the changes

File-tool edits appear in the transcript as diffs. To inspect available session changes together, run:

/diff

From v0.10.2, /diff uses the session's first restore point when available, so it can also work in folders without a git repository. Paths that snapshots did not capture remain outside that comparison; your own git diff and git status continue to use your repository.

Roll files back to an earlier turn

Workspace snapshots, when available, are stored separately from your repository's .git. They also work in folders without a git repository.

/restore           # list the 20 most recent snapshots
/restore list 50   # list more (up to 100)
/restore 1         # put files back to the newest snapshot

Restoring changes files, so it needs a trusted workspace (/trust on) or Full Access; anyone can list snapshots. You can also ask Codewhale to undo its last change.

/undo reverts your last request and its recorded file changes. It refuses file reversal if restore points are unavailable or files changed afterward. /restore selects a workspace snapshot.

Note: Snapshots default to 7-day retention with count pruning that preserves recent turn restore points; workspaces above 2 GB skip them unless you adjust [snapshots] max_workspace_gb. Ignored or skipped files and external effects are not a complete backup, and a turn can run without a snapshot when git or storage is unavailable.

Get a code review

Inside a session, /review runs a structured review of a file, a diff, or a pull request. From the shell, codewhale review reviews a git diff and prints findings:

codewhale review                      # unstaged changes in the working tree
codewhale review --staged             # what you are about to commit
codewhale review --base origin/main   # everything on this branch
codewhale review --pr 123             # a GitHub pull request (needs gh)

Add --path <file> to review one path, --model to pick the reviewer, or --json for machine-readable output. A diff over 200,000 characters is refused rather than cut short; raise the limit with --max-chars.

Note: --post publishes the review as a comment on the pull request. Without it, nothing leaves your terminal except the model request.

Keep a receipt of the review

A review receipt records the reviewed diff fingerprint and reported findings, so you can check whether the diff changed afterward. It does not prove that the review found every defect or that the change is safe.

codewhale review --base origin/main --write-receipt
codewhale review --base origin/main --check-receipt

• --write-receipt saves a local JSON file after a successful review: a fingerprint of the diff, the provider and model, finding counts, unresolved risk, and a hash of the review text. It does not store the diff itself.
• --check-receipt makes no model call. It exits non-zero if the diff has changed since the receipt, if the review left unresolved risk, or if an attached check did not pass — so it works as a pre-push gate.
• --receipt-path <file> writes or reads a specific receipt instead of the latest one.

Save the whole session

To keep or share the full record of a session, export it:

/export clipboard                  # a redacted copy of this session
/export file notes/session.md      # the same, written to a file

codewhale sessions export <id>

codewhale sessions lists saved sessions and their ids. The archive holds the complete context, so treat it like source code.

Next