Chat and editor

Review history and undo a build

Inspect the latest completed build round, undo it when needed, and verify the app before continuing.

On this page

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 Preview. Confirm that the unwanted result came from the latest round and note anything in it that you would need to rebuild.

Undo this round is on the latest round, and undoes only that round. On an older round, Roll back to this round's version makes a new version that matches that round, and keeps the database files as they are. A round that only changed the database has nothing to undo, because database changes stay as they are. Ask Ahamo if you need them changed back.

Undo the round

  1. In the completed round, choose Undo this round.
  2. Review the confirmation, which says in plain words what it does.
  3. Confirm the action.
  4. Wait for the result, then return to Preview.

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 ask Ahamo 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, see Plan first or build at once and troubleshoot an app build.

On this page