Snapshots

Snapshots let you undo recent conversation and file changes together. Use them to revise recent work, but keep Git commits or backups for anything important.

Workflow

Run /undo after a response you want to revise. OpenCode stages the rollback, restores the affected files, and puts the removed prompt back in the composer so you can edit it.

/undo

# Edit the restored prompt, then submit it again.
Add validation without changing the public API.

Submitting the edited prompt commits the staged rollback. Before submitting, run /redo to cancel it and restore the conversation and files you had before /undo.

/redo

The terminal also provides default shortcuts:

You can also select an earlier message and choose Revert to stage a rollback to that point.

Capture

For each model step, OpenCode attempts a snapshot immediately before the model call and another when the step reaches a recorded success or failure. The assistant message records which paths changed between those snapshots.

before model step ── snapshot A
model edits src/api.ts
step finishes ────── snapshot B ── changed: src/api.ts

Capture is best effort. If either snapshot is unavailable, the conversation continues, but that step may not have file changes available to restore.

Scope

Snapshots cover the session’s active directory inside a Git worktree. For example, a session opened in packages/app captures eligible files below packages/app, not changes elsewhere in the repository.

Filesystem snapshots require a Git repository. Outside one, /undo can still roll back conversation history, but it cannot restore files.

Restore

A rollback restores only paths attributed to assistant steps after the selected conversation boundary. Each path returns to its state before the first reverted step; a file created by those steps is removed if it did not exist then.

Paths not attributed to those steps are left alone. Current edits to an affected path can be overwritten, so review the restored summary and git diff before continuing.

git diff --stat
git diff

Storage

OpenCode stores snapshots locally in a separate internal Git object database under its data directory. Snapshot capture does not create commits, move branches, or intentionally change your repository’s index.

# Your repository remains an ordinary dirty worktree after capture.
git status --short

Snapshot objects can contain the complete contents of tracked and eligible untracked files. Treat the OpenCode data directory as sensitive local data.

Settings

Snapshots are enabled by default. Set snapshots to false in your configuration to stop future filesystem capture.

{
  "$schema": "https://opencode.ai/config.json",
  "snapshots": false,
}

Disabling snapshots does not delete snapshots already stored. Conversation rollback remains available, but without a captured filesystem state it cannot restore related file changes.

Safety

Snapshots are a convenience, not a transaction or backup:

• Shell commands can change services, processes, network resources, databases, Git state, ignored output, or files outside the active directory. Restoring a snapshot does not reverse those effects.
• Interrupted or failed work can leave changes when capture fails or no usable snapshot pair exists.
• Restoring affected paths overwrites their current contents. Cancelling a staged rollback can also overwrite later edits.
• OpenCode rejects rollback operations while the session is running, but external editors and commands can still change the worktree between capture and restoration.
• Committing a rollback removes messages from the active conversation view, not from durable session history or existing snapshot storage. It is not secure erasure.

Commit or back up important work before using /undo on a dirty worktree.