Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions packages/kilo-docs/pages/code-with-ai/features/checkpoints.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,10 @@ Clicking **Revert to here** does two things:

The button is only active when the agent is idle. While the agent is running, the button is disabled to prevent reverting mid-operation.

{% callout type="note" %}
Workspace restoration requires snapshots. If snapshots are disabled or the reverted range has no stored checkpoint, only the conversation is rewound — the agent's file changes remain on disk, and the revert banner warns you (see below).
{% /callout %}

### The Revert Banner

After reverting, a **Revert Banner** appears at the bottom of the chat. The banner shows:
Expand All @@ -113,6 +117,11 @@ The banner provides two actions:
- **Redo** — Steps forward one message at a time, re-applying changes from the next reverted message
- **Redo All** — Restores the workspace to the latest state and un-hides all messages (only shown when more than one message is reverted)

If a revert could not restore your workspace files, the banner warns you that only the conversation was rewound:

- **Snapshots disabled** — the banner explains that file changes were not restored because snapshots are disabled, and offers an **Enable snapshots** button that opens **Settings → Checkpoints**.
- **No checkpoint available** — the banner explains that no file checkpoint was available, so workspace changes remain on disk (for example, when reverting a range that predates checkpoints).

### Making a Revert Permanent

While in a reverted state, you have two choices:
Expand Down
Loading