CodeStilt
Product
Desktop appWindows, macOS, Linux
Web dashboardAny browser
MobileiPhone and Android
CLIFor the terminal
Safety and securityDanger wall, undo, secrets
Enterprise
Enterprise
Become a partner
Contact sales
Pricing Marketplace
Resources
Docs
Changelog
Blog
Status
Offers
Sign in Download
All posts Technology

Undo, explained: how CodeStilt puts every file back

What a checkpoint holds, how long it lasts, and why undo works without Git.

7 Nov 2026 · 2 min read · CodeStilt team
Technology

Every CodeStilt task can be undone with one click for 7 days. Here is what happens behind that button.

A checkpoint before the first change

When you approve a plan, the desktop app copies every file that plan may change into a checkpoint on your computer, before it writes anything. The checkpoint lives in the CodeStilt data folder, not in your project.

What undo does

Undo puts each changed file back exactly as it was and deletes only the files that task created itself. Nothing else in the folder is touched, so work you did by hand after the task is kept, unless it was in one of the same files.

Why it doesn't need Git

Many projects don't use Git, and many that do have changes that aren't committed yet. A separate checkpoint means undo works either way. CodeStilt never runs git reset, never makes commits for you and never rewrites history.

When undo isn't possible

After 7 days the checkpoint is deleted to save space. Undo also can't work if the CodeStilt data folder was deleted, or if the task ran on a computer that has since been unlinked.

Questions about this post? Contact us or read the docs.

Start free. No card needed.

Download CodeStilt, link your computer, and give your first task in two minutes.