Checkpoints and undo
Every AI task can be undone. Restore any saved point.
Before an AI task first changes your project, Lamied saves a checkpoint: a snapshot of your files. If you don't like what the task did, restore the checkpoint and your files are back as they were. It doesn't matter whether the changes came from the assistant's own edits or from commands it ran, such as npm install or a code generator.
Tasks that only read files never create a checkpoint.
Three ways to restore
| Do this | Restores |
|---|---|
| Click ↩ on your message in the chat | The checkpoint saved before that message's task. Messages whose task changed nothing have no ↩. |
/undo | The checkpoint saved before the latest task. |
/checkpoints | Any checkpoint you pick from the list, shown with its time. |
Before anything changes, Lamied lists the files it will restore or delete (files created after the checkpoint are deleted) and asks you to confirm.
Open tabs
Tabs of restored files reload with the restored content. A tab with unsaved edits of your own is left untouched, and the Output panel lists which tabs those are.
What checkpoints cover
- Every file in the workspace folder, except those your
.gitignoreignores. - Heavy folders like
node_modules/, virtual environments,__pycache__/,.next/andtarget/are always left out. - Your project's own Git history, branches and staging area are never touched.
- They work in folders that aren't Git repositories too.
- The 50 newest checkpoints are kept for each workspace; older ones are removed.
Limits
- You can't restore while a task is running. Stop it first with
/stop. - Changes outside the workspace folder, for example a command that writes to your home folder, aren't covered.
- Git must be installed on your computer. Without it, tasks still run, just without a checkpoint.
- Nested Git repositories (submodules) aren't restored.
Checkpoints are an undo for AI tasks, not a backup. Commit your work regularly in Source control and GitHub.