How to Undo a Composer Change with Checkpoints in Cursor

Use Cursor's Composer checkpoints to roll back a multi-file edit to any earlier point in the conversation.

6 minBeginner

Visit Cursor

When Composer edits several files and the result is wrong, undoing one file at a time is painful. Cursor saves a checkpoint at each step of a Composer conversation, so you can roll the whole workspace back to how it looked before any given message. This guide shows how to find and restore a checkpoint without losing your place.

An active Composer conversation that made changes
A change you want to undo across multiple files

Locate the checkpoints

Every message you send in Composer creates a restore point. Scroll up the conversation and hover over an earlier message. A Restore Checkpoint control appears next to it. The checkpoint captures the file state from just before that message ran.

Composer - Conversation history

You

Rename the API client methods. [ restore checkpoint ]

Agent

Edited 5 files.

You

Now also change the return types. [ restore checkpoint ]

Agent

Edited 5 files. (this is the change you want to undo)

Each prior message exposes a restore control on hover.

Restore an earlier state

Click Restore Checkpoint on the message just before the change went wrong. Cursor reverts every file Composer touched back to that point. Your editor updates immediately, so save and check the diff against git to confirm.

Checkpoints are not git

Restoring a checkpoint only undoes changes Composer made in that session. It does not track edits you typed by hand outside Composer. Commit important work to git so you always have a real backstop.

Continue from the restored point

After restoring, you can send a new instruction and Composer continues from the reverted state. This lets you try a different approach without the failed attempt polluting the files.

zsh - confirm with git

$git status --short

M src/api/client.ts

only the intended files differ after restore

$git diff --stat

1 file changed, 6 insertions(+), 4 deletions(-)

Result: a bad multi-file Composer edit rolled back in one click, leaving your workspace exactly as it was before the change so you can take a cleaner second attempt.