Review history and undo a build

Each completed build round remains in Chat with its summary and actions. Use Undo this round on the latest committed round when its changes should be removed together.

The editor also has Show history, which opens an app audit timeline. That view records meaningful app events; it is not where you undo code. Choose Show chat to return to completed rounds.

Inspect the round

Use the prompt marks beside Chat to inspect earlier prompts, or scroll to the latest completed round. Read its summary, then reproduce the problem in Build. Confirm that the unwanted result came from the latest round and note anything in it that you would need to rebuild.

The undo action is disabled when a round has no committed change. It is also unavailable after the latest round has already been undone. Do not use an older round's control to choose a historical target; the current action rolls back one step from the app's present state.

Undo the round

In the completed round, choose Undo this round.
Review the confirmation: all files from that build return to the previous commit.
Confirm the action.
Wait for the rollback result, then return to Build.

Undo removes the round as a unit. It cannot keep one file or visual change from that round while discarding another.

Verify restoration

Repeat the journey that failed and check the surrounding screen. If shared layout changed, check another screen and viewport too. The restored preview should match the behavior from before the undone round.

Then switch to Plan before rebuilding the failed idea:

The earlier booking form is working again. Plan a confirmation improvement only. Keep the service selection, form fields, and current styling unchanged. Explain how I can test the new confirmation before building.

Undo affects generated source, not separately stored records or a version already published to visitors. Check Runtime for data effects and the live address for production behavior.

Next: Choose Plan or Build mode and troubleshoot an app build.