Skip to content
Superapp
Esc
↑↓navigate↵open⌘Jpreview
On this page

History and recovery

Restore a previous Superapp version instead of fixing a damaged state forward.

Superapp keeps a history of previous project versions. When a change breaks the app or takes it in the wrong direction, you can revert to a known-good version instead of adding increasingly complicated repair prompts.

Use a safe iteration loop

  1. Start from a version whose main flow works.
  2. Request one coherent change and wait for it to finish.
  3. Test the affected flow and nearby screens.
  4. Keep the result or return to the last good version before continuing.

When reverting is the safer choice

  • The same error remains after two focused repair attempts.
  • A narrow feature request unexpectedly changed several working areas.
  • Signing, entitlements, dependencies, or project structure changed without intent.
  • The current state is harder to explain than the original requested change.
  • You need a reliable build immediately for testing or release.

Revert in Superapp

1. Wait for the agent

Let the current change finish. Superapp disables restoration while the agent is still working so project state cannot change underneath it.

2. Open edit history

Open the project’s edit history and find the last version whose app behavior and build result you recognize as correct.

3. Choose Revert

Review the selected version’s message and time, then confirm. Superapp restores the project and automatically attempts a new build.

4. Verify the restored app

A successful revert message confirms restoration. If the files restore but the rebuild fails, treat the new build diagnostic separately before continuing.

Recover a Mac project

When working locally or with Claude Code, Codex, or Xcode, create small version-control commits at meaningful checkpoints. Review the diff before restoring anything, preserve uncommitted work that matters, and revert only the external changes responsible for the failure.

Continue from a clean base

After restoration, reproduce the original feature request as a smaller task. Name the working behavior that must remain unchanged and verify the next build before continuing.