AI broke your code? Just chill bro. Want a coffee?
macOS & Linux · Use with any AI agent
Why Rewindex
Git remembers what you finished.
Rewindex remembers everything you tried.
Git records completed versions. Rewindex records every micro-version in between. Every time you or your AI saves a file, we capture a version. You can rewind just one file or your entire project to any point in time.
How it works
Every time you or your AI saves a file, we capture a snapshot automatically. Every version. Every change.
When you finish a task, all the changes are grouped into one session. Easy to find. Easy to rewind.
When your AI finishes working, it writes a note on the session. No manual logging needed.
When something breaks, the full log is right there. Your AI knows exactly where to go back to.
See it work
config.json - the timeouts were making deploys hang, so I zeroed them out.
What you get
Every change saved as a micro-version. Always.
One rewind command is faster than explaining the problem to your AI all over again.
Start from the log. See exactly what changed and when it broke.
Every AI change is on record. Check what was touched and when.
Know you can always go back. Try anything.
No decisions, no commands. It runs. You build.
Claude Code, Cursor, Copilot, Windsurf. Any agent that edits files.
No credit card. No trial. Just install and go.
Your code stays on your machine. Nothing leaves your disk.
Pricing
* After purchasing Pro, your license key will be displayed on the confirmation page and sent to your email.
Get started
Rewindex runs silently in the background. Register it as an MCP server and your AI can take snapshots and rewind without any extra setup.
macOS & Linux · Windows (experimental) · Python 3.10+
Recommended
Your agent handles everything. Install, MCP setup, and init.
Send this to your agent chat
Read https://raw.githubusercontent.com/crsxmd/rewindex/main/AI-SETUP.md and follow the setup instructions.
Works with Claude Code, Cursor, Windsurf, Cline, and more.
Manual
Three steps and you're watching. Takes about a minute.
Install
pipx install rewindex
Also: pip install rewindex · uv tool install rewindex
Add as MCP server
See mcp-register.md for instructions per agent (Claude Code, Cursor, Windsurf, Cline, and more).
Initialize your workspace
rewindex init
Rewindex is now watching your workspace.
Tip: Once the MCP server is registered, your agent can snap and rewind without any extra prompting.
Browse snapshots, view diffs, rewind files, and manage flags from the browser. Included in the package, no extra install needed.
FAQ
Git is for big checkpoints. You commit when a feature is done, a bug is fixed, or something is ready to share. But between those commits, your AI agent edits files dozens of times. It breaks things, fixes them, breaks them again. None of that gets recorded.
Rewindex lives in the gap. Every file save is captured automatically, no commands, no decisions. It's micro version control for the messy work that happens before you're ready to commit.
Rewindex isn't a Git killer. It's what runs underneath, so when you finally push to Git, you didn't lose anything along the way. And unlike Git, Rewindex is built for AI agents first. Your agent knows how to snap, rewind, and annotate without you asking. You still can, but you don't have to.
Only when you ask. Rewindex records every change silently in the background. It never touches your source code on its own.
The only time it writes to your files is when you or your AI run rewindex rewind.
And if you're worried about something modifying your files without you knowing, that's exactly why you need Rewindex. Everything is recorded. Nothing disappears quietly.
No. Everything is stored locally in ~/.rewindex/. No cloud, no accounts, no telemetry. Your code stays on your machine. It even works offline, great for coding in the woods, a bunker, or just your mansion when you forgot to pay the bill.
The only thing that ever leaves is your Rewindex license key, just to confirm it's still valid so you can keep using Pro.
Rewindex itself is lightweight, but your snapshots grow with your code. We handle that for you. Snapshots are compressed automatically, and auto-trim runs in the background to keep things minimal.
You can check usage anytime with rewindex status, and clear old snapshots with rewindex cleanup.
Yes. Rewindex doesn't care who made the change, only what changed. Whether it was your AI, your editor, or your intern who definitely didn't mean to break anything, everything gets captured. Your manual changes show up in the log just like everything else.
SSH keys, certificates, and tokens are hardcoded to never be snapshotted, no matter what.
Common clutter like .env, node_modules, and log files are excluded by default to keep things clean, but you can adjust those if you want. For anything else, you can add your own exclusion patterns anytime. Just tell your AI, or do it yourself. And even if something does get captured, it stays on your machine. Nobody else sees it.