Watch · Checkpoints

Checkpoints

Non-destructive rewind for agent work. Snapshot the working tree on demand, then restore any prior snapshot without writing a commit or moving HEAD. A safety net for letting an agent run hard, with an undo that never rewrites history.

What it does for you

Snapshot before you let the agent loose.A checkpoint captures your tracked-file changes on demand. Take one before a risky refactor or a long autonomous run, and you always have a clean point to return to.
Restore without touching your history.Restoring a checkpoint materializes that saved tree back onto disk. It does not write a commit, move HEAD, or touch your branch, so your commit history and the git stash are left exactly as they were.
It refuses to clobber uncommitted work.Restore stops if the working tree has uncommitted changes and refuses to run, so a rewind can never silently eat work you meant to keep. To overwrite anyway, re-run it with the force flag.

Where to find it

  • Desktop: http://localhost:4000/, then Watch → Checkpoints in the sidebar.
  • Hosted: desktop-only. The repoops.ai sidebar carries an “On the desktop app” pointer for it.
  • Keyboard: ⌘ K, then type “Checkpoints”.
  • CLI: repoops checkpoint create · list · restore (flags: --label, --force, --repo).
  • API: GET /api/checkpoints · POST /api/checkpoints · POST /api/checkpoints/restore

How it works

A checkpoint is a real git commit object captured with git stash createand stored as an annotated tag under refs/tags/repoops-checkpoint/<id>, so it survives independently of your branch and the stash. Restore uses git read-tree --reset -u to put that tree back on disk; neither HEAD nor the current branch ref moves. Creating a checkpoint only adds a tag, so taking one is safe to repeat. Restore rewrites the index and your tracked files to match the snapshot, which deletes tracked files added after it, so it refuses to run on a dirty tree unless you pass the force flag. Untracked files are left alone.

✓
Checkpoints are local and free.
They run entirely against your local git repo. No cloud, no data egress, and they cost nothing to keep around.

Built vs. planned

Live on the desktop app: the CLI, the HTTP API, and the Checkpoints tab all ship today. Checkpoints are a desktop-only local surface; the hosted dashboard carries a pointer to it.

Last updated