What is going on
Claude Code edited your files and you want them back the way they were. There are two ways to go back, and they cover different things.
Error messages you might see
Common causes
- A broad request led to edits in several files.
- A change looked right but broke something later.
- A command run by Claude Code (not an edit) deleted, moved or copied files.
How to fix it
- Rewind. Claude Code keeps checkpoints of the edits it makes with its own file tools. Open the rewind menu (type
/rewind) and choose whether to restore the code, the conversation, or both. - Know what rewind cannot do. It does not track files changed by shell commands, such as
rm,mvorcp, and it does not restore changes you made by hand. Checkpoints are also cleaned up after a while (30 days by default). - Use git as the real safety net. Run
git statusandgit diffto see changes.git restore path/to/filebrings back one file. Commit before big tasks so you can always go back. - If files were deleted by a command, restore them from git, or from your backup or trash.
- Then ask for the change again in small steps.
Getting help takes about a minute
No hiring, no back and forth. A real person looks at your app.
-
1
Describe it
Tell us what you need in plain words. You don't have to be technical or have an account to start.
-
2
Free 15-minute call
A verified developer calls you. Many tasks are sorted right there, and it costs nothing.
-
3
Pay after you approve
If there is more to do, you get one fixed price up front. You pay only once you are happy.
Real people, reviewed by hand
Developers who do this every day
Every developer is approved by our team before they can take a task. Describe yours and the first one who is free picks it up.
Get helpQuestions
Does rewind undo everything?
No. It covers edits made through Claude Code's file tools. Changes made by shell commands, or by you, are not tracked.
What should I do before a big task?
Commit your work. A clean commit gives you a point you can always return to.