Omniscio

Turn checkpoints (undo what one turn changed)

Switch on Turn checkpoints in Settings → Lab, and every turn of a session on this computer is saved as a private before-and-after snapshot of its folder. When a turn goes wrong, open the Checkpoints button in the session header, pick the turn, and confirm: the files that turn changed are put back, the files it made are removed, and nothing else is touched. The undo itself can be undone.

On this page

What it is

Agents change files quickly, and the most common wish after a bad turn is "put it back the way it was before that". Turn checkpoints give every session its own quiet undo history for files.

Before a message goes to the agent, Omniscio takes a snapshot of the session's folder. When the answer arrives, it takes another. The pair is one turn, numbered in order. Undoing a turn means comparing the two snapshots and reversing just that difference.

The snapshots are kept in a hidden store inside Omniscio's own data folder — never inside your project. They never write to your own git history, branches, staging area or stash, your own git hooks never run during a snapshot, and files are stored as exact bytes so line endings come back unchanged. Folders that are not git projects work exactly the same.

Where to find it

  • Switch it on: Settings → Lab → Turn checkpoints. It is off by default. Searching Settings for "checkpoint", "undo", "rollback" or "rewind" finds it.
  • The Checkpoints button sits in the session header (its tooltip reads "Undo a turn's file changes"). It opens a panel listing the session's turns, newest first, each with how many files it changed — the true number, including files whose names are too long to list. A turn that changed nothing says "No file changes" and cannot be undone.
  • The composer command: type /rollback to undo the latest turn that changed files, or /rollback 4 for turn 4. /rewind does the same while checkpoints are on. Either one only opens the confirm step — nothing changes until you click Put files back.
  • Desktop only. The panel and restore are not available from the phone app or the control server.

How it behaves

The confirm step. Choosing a turn opens a dialog that names every file and what will happen to it: "changed, will be put back", "deleted, will be put back", or "made by this turn, will be removed". It also gives the true number of files it will put back. When the list cannot show some of them — a file whose path is too long to show, or more files than the list holds — a line under the list says how many more are put back but not listed, so a turn whose only changed file has a very long path still reads "Put back 1 file", never "Put back 0 files".

Your later edits are safe. A file you (or the agent) changed again after that turn is listed as "edited since this turn, left alone unless ticked". It is skipped unless you tick Also put this file back.

Files that cannot be put back are listed apart. Under "These files stay as they are:" the dialog names any file a restore can never write, with the reason — for example one that has since grown past the size a checkpoint can put back, or one that is now a folder or a link rather than a file. These have no tick box and are not counted in the number of files.

A restore is itself undoable. Before a restore writes anything, it snapshots the folder as it is now. The restore then shows up as a new turn in the list, so if you change your mind you undo that turn. The message confirming a restore carries an Undo restore button, which undoes exactly the turn that restore recorded — never simply the newest turn, which may be a later answer. If the restore could not record its own turn, there is nothing to undo it with and the button is not shown.

When a restore is refused. Nothing is changed, and the dialog says why:

  • the session is still working — stop it first;
  • the session now works in a different folder from the one the turn changed;
  • another open session works in the same folder — stop it first so its work is not undone;
  • the turn is too old and its checkpoint has been pruned;
  • one of the files now sits behind a link or outside the session's folder.

Snapshots never hold up a message. If a snapshot fails or takes too long (about fifteen seconds), that turn simply has no snapshot and your message goes out unchanged. The panel tells you the last checkpoint was skipped. Messages the app sends on its own (a scheduled wake, for example) take no before-snapshot.

One step at a time per session. A session's snapshots, restores and clean-ups run one after another, never two at once. A step still waiting after about five minutes behind the work ahead of it is given up rather than run late.

The limits worth knowing:

  • Local sessions only. Sessions running on another machine or in the cloud are not checkpointed, and the panel says so.
  • Some folders are skipped, with the reason shown in the panel: your home folder, the shared app folders Omniscio uses for unassigned sessions, and folders holding more than about twenty thousand files.
  • Large files are left out of the snapshot (anything over about 5 MB), so they cannot be put back.
  • The last fifty turns of each session are kept. All sessions' checkpoints together stay under a disk budget of about 2 GB; past it, the checkpoints of the session checkpointed longest ago are removed first, a whole session at a time.
  • Archive keeps the history; delete removes it. An archived session can be brought back with its undo history intact. Deleting a session deletes its checkpoints.
  • A damaged store is rebuilt. If a session's checkpoint store fails its integrity check, it is started again empty and you are told that earlier turns can no longer be undone.

Not the same as Ctrl+Z. Ctrl+Z undoes actions on the session itself (pause, archive, rename). Turn checkpoints undo the files an agent changed. Claude's own built-in rewind inside a Claude session is a separate engine feature.

  • Undo a session action (Ctrl+Z) — undoing pause, archive, rename and other actions on a session, not its files.
  • Native slash commands — the other composer commands that sit beside /rollback.
  • Pause or stop a session — a restore needs the session stopped first.
  • Archive a session — archiving keeps the undo history; deleting removes it.

Last verified 2026-11-01