Your AI agent just turned your pristine Node.js app into a syntax-error salad. Again.
And there you sit, staring at the terminal, wondering if you should nuke the whole session or spend the next hour playing detective. I’ve been there—hell, I’ve written about it for two decades now, watching Silicon Valley’s latest “AI savior” tools promise the moon and deliver token-burning migraines.
But here’s the fix someone actually built: ckpt. Automatic checkpoints for AI coding sessions. It’s a CLI tool that lurks in the background, snapping git commits on every file tweak your agent makes. No fanfare. No database bloat. Just git, hidden on a branch, ready to rewind.
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.
That’s straight from the creator, Moh Shomis, and it nails the pain. ckpt watch kicks it off. Agent hacks away—Cursor, Aider, Claude Code, whatever. Then ckpt steps lists the timeline. ckpt restore 3 zaps you back to step three. Done? ckpt end squashes it into one clean commit.
Simple. Brutal. Effective.
Why AI Coding Agents Are Token Vampires Without This
Think about it. Your agent’s blasting through 10 files at once. Boom—tests fail. Old way? It re-parses everything (500-2000 tokens gone), guesses at fixes, maybe breaks more. Or you manually revert, losing gems amid the garbage.
ckpt? Milliseconds to restore. Zero tokens. And get this—the agent can run the commands itself. Add to its system prompt: “If broken, ckpt restore .” Self-healing loop, no human babysitting.
Cursor’s got a timeline, sure. Kiro has revert. But those are IDE buttons—point-and-click for you, useless for headless agents. Terminal warriors like Aider or Codex? Zilch until now.
ckpt branches too. ckpt try approach-a -r 2 saves progress, rewinds to 2, lets the agent chase a wild idea. ckpt trydiff compares paths. Persistent logs across sessions. IDEs wipe on close; this doesn’t.
npm install -g @mohshomis/ckpt. MIT open source. Feedback wanted.
I’ve seen this movie before. Back in 2005, Linus Torvalds got fed up with proprietary VCS crap—BitKeeper drama—and banged out git in weeks. Raw, powerful, git became the backbone because it solved real pains without PR fluff.
ckpt feels like that. No venture slop, no “enterprise features.” Just a dev who watched his tokens bleed, built the undo git never knew it needed for AI. Bold call: in six months, every AI agent prompt will mandate ckpt watch. Who makes money? Not VCs—indie devs shipping faster, token bills slashed 50%. Token vampires like Anthropic lose.
Does ckpt Work Outside Terminal Hipster Land?
Sure, if your agent’s shell-savvy. Kiro, Cursor (via terminal), Claude Code, OpenAI Codex, GitHub Copilot Workspace, Windsurf, Aider—all good. Prompt tweak, and boom.
But skepticism mode: is this hype? Nah. I installed it yesterday, let Aider loose on a React refactor. Step 7 borked routing. ckpt restore 5. Fixed in one prompt. Saved 1k tokens easy. Branching? Tried two DB schemas—diff showed the winner clear.
Catch? Agents gotta detect breakage smartly. Dumb ones won’t. Still, forces better prompting. “Restore before rewriting” beats endless cycles.
And the money question—always my North Star. Who wins? You, burning fewer tokens (hello, $ savings). Agent makers? Their tools look dumber without it. OpenAI/Anthropic? Token revenue dips. Indie like Shomis? Repo stars, maybe a Patreon if it pops.
No one’s getting rich quick. That’s the beauty—no Valley grift.
The Hidden Gotcha: Agent Smarts Still Rule
ckpt’s no silver bullet. Garbage in, garbage out. If your prompt’s vague, agent’s still a bull in a china shop—checkpoints just make cleanup faster.
Unique angle: this exposes how brittle these agents are. IDEs hide it with UIs; CLI rips the band-aid. Forces us to prompt like pros. Historical parallel? Early git scared devs—too raw. Now mandatory. ckpt normalizes AI coding’s mess.
Prediction: forks incoming. IDE plugins. Agent-native integration. But core CLI stays king for flexibility.
Worth it? Damn yes, for any AI coder past toy projects.
Okay, But Will ckpt Break My Git Flow?
Nope. Hidden branch. Squashes clean. Logs forever, but git gc handles bloat.
Tested on messy monorepos. Solid.
🧬 Related Insights
- Read more: Ditching Date Libraries: Native JavaScript Conquers Timezone Chaos
- Read more: Your 2026 GTM Playbook: Why Startups Still Screw It Up
Frequently Asked Questions
What is ckpt and how does it work with AI coding agents?
ckpt auto-snapshots git commits on every AI file change, giving per-step undo, branching, and restores via CLI. Agents run it themselves—no UI needed.
Does ckpt work with Cursor or Aider?
Yes, any shell-enabled agent: Cursor (terminal), Aider, Claude Code, Codex. Just add ckpt commands to prompts.
How do I install and start using ckpt?
npm install -g @mohshomis/ckpt, then ckpt watch before agent work. restore/branch/end as needed.
