miton

In development. The beta will be a downloadable desktop app with automatic updates. Access is not open yet.Request an invitation.

Guide · 3 min read

Per-turn rewind

How to use Miton's per-turn restore points to undo agent steps and return to any earlier state in a session.

Product stage
Pre-release development
Last reviewed
2026-07-23
Successful result
The change is visible in the active project.

What this accomplishes

How to use Miton’s per-turn restore points to undo agent steps and return to any earlier state in a session.

Miton creates a restore point after every agent turn. If the agent edits files, runs commands, or takes actions you did not want, you can return to any earlier point in the session in one click.

Current availability

This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates.

Before you start

  • A Miton development build and an active project.
  • A connected cloud or local model, plus any credentials or local runtime required by this task.

What gets saved

A restore point captures:

  • All file changes the agent made since the previous turn (as a git snapshot in a hidden ref)
  • The session transcript up to that turn
  • The agent’s current memory store context

Restore points are git-native. Miton does not maintain a separate file-copy system — it uses your existing repository’s object store.

How to restore

  1. Open the session where you want to go back
  2. Hover over any earlier agent message in the transcript
  3. Click the Restore to here button (rotate-back icon)
  4. Confirm in the modal — Miton shows you which files will change

Restoring resets your working directory to the state at that turn. Uncommitted changes made after that turn are discarded. Miton warns you before discarding anything.

The stash drawer

Before restoring, you can save useful snippets to the stash drawer:

  1. Highlight text in the transcript or in an editor panel
  2. Open the stash drawer from the status bar (Stash button) and add the snippet, or use the context-menu stash action on the selected text
  3. The snippet appears in the stash drawer (right sidebar → Stash)

Stashed snippets persist across restores. They are scoped to the session.

Crash recovery

If Miton closes unexpectedly, it creates a recovery restore point at the moment of the crash. On next launch, a banner appears:

Recovery available — Miton closed unexpectedly. A restore point was saved. Restore?

Click Restore to return to the state at the crash, or Dismiss to continue from wherever the file system was left.

Limitations

  • Restore points require a git repository. In sessions without a git repo (e.g. a blank Document session), only the transcript is saved — file changes are not reversible via restore.
  • Shell commands that have side effects outside the repository (e.g. API calls, database writes) are not undone by a restore. Miton restores files; it cannot undo external actions.

What success looks like

How to use Miton’s per-turn restore points to undo agent steps and return to any earlier state in a session. The result remains attached to the active project when you move to another workspace.

Common failures and recovery

  • Confirm the correct project and model are active.
  • Read the exact error and the requested permission before retrying.
  • Retry only the failed step so completed project work remains intact.
  • Sessions — how sessions work and how to manage them
  • Memory — what persists across sessions