Building your first version
How can I undo an AI change that broke my app?
Lumos · Updated
Use your builder's version history or the project's saved code history to return to a known working version. Preserve the current work first, then check exactly which changes the restore will remove.
Stop asking for unrelated fixes while you investigate. Find the last version where you actually tried the affected task successfully. A description such as “client can submit a response and read it after refreshing” is more useful than “latest backup.”
Check what the restore includes
Ask your tool to show the changes since that version. You may be able to undo the broken change while keeping useful work that came later. If you're using Git, a commit records a version of the project's tracked files. Git's guide to undoing changes explains recovery options and warns that some operations can discard work.
Before confirming a restore, have the tool explain what it will preserve and what it will replace. If there is no saved history, ask it to inspect available backups and change records. Recovery isn't guaranteed.
Code history and user data need separate attention. Restoring an earlier code version doesn't automatically restore deleted database records. If the change also altered the database, check its backups and compatibility with the older code before using it.
Try the restored version in a preview, repeat the failing task, and check the result. If the public app is affected, it may also need a deployment rollback or a new deployment.
In the Builders Handbook
Test it, fix it, and keep going explains checkpoints and data recovery. Get a live URL covers checking the deployed version.