Checkpoints exist because AI sometimes takes a wrong turn. Every schema-changing move snapshots the project schema first. If the next move looks bad, you restore the previous checkpoint with one click.
When checkpoints are created
- Before Build from plan runs.
- Before any AI move that creates a table or alters a column.
- When you click Save checkpoint manually in Build mode.
- Before a checkpoint restore (so you can undo the undo).
How restore works
- In Build mode, open the checkpoint history.
- Click Restore on the checkpoint you want to roll back to.
- 6cript first creates a fresh checkpoint of the current state, then applies the snapshot.
What restore does
- Rewrites the project_schemas record to match the snapshot.
- Rewrites the project_blueprints record if the snapshot captured one.
- Rewrites the last action / last UI fields of project_states.
What restore does NOT change
- Existing data rows in your tables. Restoring schema does not delete rows already inserted.
- Saved scenes. They persist across restores.
- Tasks. The task list is independent of the schema.
- The preview token.
Best practices
- Save a manual checkpoint before any "let me try a wild idea" chat session.
- After a restore, scroll the activity timeline to confirm the schema is what you expected.
- Do not rely on checkpoints for data backup — use the JSON export instead.