Going back after an AI deleted something.
By the Olomni team · Updated
If you use Olo and the project has Git, Olo saved a copy of your files right before what you approved: in Olo or on your phone, under “You can undo”, tap “Undo”. If you don’t use Olo, check the Trash and Git (for example git reflog or git stash list) in case the work is still there. What already left your computer — a published change or data deleted on a service — can’t be undone from there.
Step by step
- Stop using the AI in that project so it doesn’t keep changing files.
- In Olo (or on your phone, “Work” tab, “You can undo” section) find the action you approved and tap “Undo”.
- Check the files: Olo first saves how everything is right now, so undoing can itself be undone.
- If there was no restore point, try the Trash, your backups and Git (
git reflog,git stash list).
What Olo’s copy covers
Your project files, including new ones you hadn’t saved yet (respecting .gitignore). It doesn’t touch your Git history. It only exists in Git projects and when the restore point is turned on.
What it doesn’t cover
What already left your computer: a git push, a publication, a deploy or data deleted in a database or a service. It also doesn’t delete new files the AI created afterwards. Olo always tells you, on each permission, whether something can be undone.
Frequently asked questions
Why is “Undo” sometimes missing?
Because the project doesn’t use Git, the restore point is turned off or the action doesn’t touch files on your computer (for example a push or a database change).
Can I undo a git push --force?
Not from Olo: it already left your computer. That is why Olo marks it as danger and asks you to hold before letting it through.