I Built ckpt: Automatic Checkpoints for AI Coding Sessions
AI agents don't have Ctrl+Z. When they break your code, they don't undo. They re-read every file, reason about what went wrong, rewrite from scratch — burning tokens on code they already had right....

Source: DEV Community
AI agents don't have Ctrl+Z. When they break your code, they don't undo. They re-read every file, reason about what went wrong, rewrite from scratch — burning tokens on code they already had right. Sometimes the "fix" breaks something else. And the cycle repeats. I got tired of watching this happen, so I built ckpt. What is ckpt? ckpt is a CLI tool that runs in the background and auto-snapshots every change your AI coding agent makes. You get a full timeline of every step, and you can restore to any point instantly. ckpt watch # start watching — auto-snapshots every AI change # ... let your agent work ... ckpt steps # see what happened, step by step ckpt restore 3 # go back to step 3 ckpt end # squash into one clean git commit It's just git under the hood — hidden branch, real commits, squash when done. No new format, no database. The Problem AI agents edit your code in rapid bursts — 5, 10, 20 files at once. When something breaks, you have two bad options: Undo everything — lose all t