The safety net you need when coding with AI
When Copilot or Cursor rewrites half your project, StateSense captures the before state automatically — so you can always roll back.
AI tools can generate — and break — thousands of lines of code in seconds. VS Code's undo history is per-file and per-editor. Close a tab and that undo history is gone forever. There's no built-in way to roll back a whole-workspace AI refactor without using git, which requires you to have committed before the AI started.
StateSense runs in the background and watches for exactly this pattern: many files changing rapidly. When it detects an AI-style batch edit, it automatically creates a snapshot of your workspace just before the changes complete. If the AI output doesn't work, one click takes you back.
How it works
Auto-capture before AI runs
StateSense detects rapid multi-file changes and creates a snapshot automatically. You don't need to do anything.
See the diff when things go wrong
Click on any snapshot to open VS Code's diff view for every changed file. You can see exactly what the AI changed before deciding whether to restore.
Restore in one click
The Restore Preview panel shows you every file that will be affected. Confirm and your workspace goes back to the pre-AI state instantly.
Pin the last-good state
Found a stable point? Pin that snapshot so it's protected if you ever manually clear your snapshot history.