Introduction
When you work in an interactive CLI de Copilot session, Copilot can make changes to files, run shell commands, and modify your repository. If the result isn't what you expected, you can rewind to a previous point in the session to undo those changes.
When you enter a prompt, the first thing CLI de Copilot does is take a snapshot of your workspace state. This snapshot allows you to roll back to that point in the session if you need to. You can trigger a rewind by pressing Esc twice, or by using the /undo slash command.
This article explains how to roll back changes. For more conceptual information about rewinding to an earlier point in a session, see Canceling a CLI de GitHub Copilot operation and rolling back changes.
Prerequisites
- You must be working in a Git repository with at least one commit. CLI de Copilot uses Git operations to track and restore workspace state.
- A snapshot must exist. Snapshots are created automatically at the start of each of your interactions with Copilot in a CLI session. You can't roll back changes made before your first prompt in a session, or to the repository state for a step where snapshot creation was skipped, see Changes that can't be rolled back.
Rolling back with a double Esc keypress
Advertencia
- Rewinding restores your entire workspace to the state it was in at the selected snapshot. This reverts all changes made after that point—not only changes made by Copilot, but also any manual edits, and changes resulting from shell commands. Any new files created in the workspace after the snapshot was taken are deleted, irrespective of their Git status.
- Rewinding cannot be undone. Once you roll back to a snapshot, all snapshots and session history after that point are permanently removed.
When Copilot has finished responding to a prompt you've entered:
-
Make sure the input area is empty. If there's text in the input area, pressing Esc twice in quick succession clears the text.
-
Press Esc twice in quick succession to open the rewind picker.
The rewind picker lists the available snapshots for the current session, with the most recent first. The ten most recent snapshots are displayed. If there are more than ten snapshots available you can use the ↓ arrow key to scroll down through earlier snapshots.
For each snapshot, the beginning of the prompt you entered is shown, with an indication of how long ago you submitted it.
-
Choose a snapshot to roll back to. This will return you to the state of the repository when you entered the associated prompt.
Nota:
The repository is rolled back to its state immediately before Copilot started working on the prompt, not immediately after it finished working on the prompt.
The prompt you selected is shown in the input area, so you can edit and resubmit it, if required.
Rolling back with the /undo slash command
The /undo slash command, and its alias /rewind, provide an alternative way of opening the rewind picker.
Both commands produce the same result that you get by pressing Esc twice when Copilot is idle and there is no text in the input area.
Verifying the rollback
After rolling back, you can use Git commands to verify the state of your repository and confirm that it matches your expectations.
Typing ! allows you to run shell commands directly from the CLI de Copilot input prompt, so you don't need to exit the CLI to check the repository state.
| To do this | Enter this command |
|---|---|
| Check which files show as modified, staged, or untracked. | ! git status |
| Show the SHA and commit message of the current commit. | ! git log --oneline -1 |
| Review the unstaged changes. | ! git diff |