# How do I fix a fault in my live app quickly, or go back to the last version?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Tell your AI the fault, or ask it to undo the change; say yes when asked to put the fixed or earlier version live.

## Deeper

Your app is live at https://&lt;name\>.pages.dev, where &lt;name\> is the name given to your site. GilbApp has no control that undoes code or goes back to an earlier version, and GilbPlatform has no command that switches a live site back to an earlier one. Both ways below end the same way: the version you want is published again under the same name, at the same address, and only with your yes.

Fix the fault. A fault, often called a bug, is anything in your app that does not do what it should. Tell it to your AI in plain words: what you did, what you expected, what happened instead, and the exact words of any message on the screen. Say that it is in the live app. Agent.Coder, the agent that writes your app's code, works on a fix, and its rules say to have each piece of work tested before it is handed back. An agent is your AI following one written procedure, its standing instructions, for one kind of work. Then your AI is told to ask if the new version should go live, and it may not put it live without your yes. The answer [How do I tell my AI about a fault so it can fix it?](http://support.gilb.com/help/how-do-i-tell-my-ai-about-a-fault-so-it-can-fix-it) shows what a good report says.

Go back to the last version. When a change broke something else, or was the wrong approach, you can ask your AI to undo it, in your own words, for example: The last update broke the booking page, undo it. Agent.Coder's way of undoing runs only when you ask for it. It adds a new version that reverses the change; nothing is deleted, and the tests run again. A fault in the new part itself is fixed in a new change instead. Agent.Coder does not build something new in its place until you have agreed the new direction. If the change you undid was already live, the earlier version must be published again at the same address, and Kai-Zen, the planning agent, never puts anything live without your go. The answer [Can I undo what I've built, or go back to an earlier version?](http://support.gilb.com/help/can-i-undo-what-ive-built-or-go-back-to-an-earlier-version) says more.

My live app broke after an update. Until the fixed or earlier version is live, people who open your app get the version that is live now. Use one of the two ways above. If Kai-Zen is running the change, then once the new version is live it asks you to check it live, fixes what you send back, puts it live again and asks again, until you approve. If you went straight to your AI, open the live address and [check it yourself](http://support.gilb.com/help/how-do-i-check-my-app-once-it-is-live).

Publishing again. Publishing a site you already hold again works and does not use a new one. If you can, publish updates from the same computer. If publishing again is refused, write to support@gilb.com with the address and what your AI showed you. The answer [How do I update my app after it is live?](http://support.gilb.com/help/how-do-i-update-my-app-after-it-is-live) shows the steps.

Your data. Going back in the code does not take back what was written to a vault, the place where a person or a group keeps their records. GilbApp has no button to bring a deleted record back. The answer [How do I see a record as it was before \(its history\)?](http://support.gilb.com/help/how-do-i-see-a-record-as-it-was-before-its-history) says more.

Published by mistake. Today you cannot take a site off the internet yourself: GilbApp and GilbPlatform have no way for you to do that. Your AI can publish a new version without the file or text that should not be there, at the same address. This page does not show that older versions or copies are gone, and anything that was public may already have been seen or copied. If something went live that should not have, write to support@gilb.com with the address; nothing here promises what support can do.

This answer is written for a computer screen.

Source: Standards read from GilbPlatform on 13 November 2026: Proc\_v\_Rollback \(only when the person asks; a change broke something unrelated or the approach was wrong; not for a bug in the increment; revert, nothing deleted; tests run again; agree the new direction first\), Agent.Coder \(AfterIncrement: have every increment tested before hand-back; AskGoLive; Contextual: rolling back\), Kai-Zen.GoLive, Kai-Zen.HumanCheck \(Ask, Fix\), Proc\_v\_i\_c\_PublishPagesDev \(step 10: publishing a held site again\), Standard Rule\_Code\_deployment \(RuleDeployPagesDev: takedown not live yet\). GilbPlatform 0fc5a548 \(https://id.gilb.com/version, read 13 November 2026\): src/routes/publish.ts:278, :413, :442 \(the only publish doors: ticket, precheck, admit; none goes back to an earlier version or takes a site down\). GilbApp 49b1ae53 \(https://gilb.com/app/version.json, read 13 November 2026\): no control in src that undoes code or restores a version. Live help pages, sentences shared: Can I undo what I've built, or go back to an earlier version?; How do I tell my AI about a fault so it can fix it?; Something that worked yesterday is broken today. What now?; How do I update my app after it is live?; How do I see a record as it was before \(its history\)?
