History & Backup
Two different things, and you only need the first one. History is your undo button and is always on. GitHub is an optional extra for developers.
Changed something you did not mean to — or the AI did? Click History at the top of your site, pick an earlier version, and restore it. Nothing to set up.
You do not need GitHub for this. Most people never connect it.
History — your undo button
Every time you or the AI changes your site, we save a checkpoint automatically. Open History to look through them, preview an older version, and restore it in one click. Restoring is itself reversible, so you can move back and forward until the site looks right.
- Always on. No setup, no account to connect.
- Saved with your site on Serenities AI's servers — not in GitHub.
- Keeps the last 100 changes, and everything from the past 30 days.
- You can undo one single change, or roll the whole site back to a moment in time.
History has no branches. It is a single straight line of checkpoints — the story of your site over time. If you want to try a bigger idea without touching your live pages, that is what GitHub branches are for.
GitHub — optional, for developers
Connecting GitHub mirrors your pages and components into a code repository you own. It is genuinely optional, and it is aimed at people comfortable with code. It gives you three things History does not:
- A copy outside Serenities AI, in an account you control.
- Branches — a separate version of the whole site to build something big without disturbing the live one.
- Code review and normal developer tooling.
Find it under Config → History & Backup. Once connected you can switch branches, create a branch, and save your current pages to the branch with Commit.
How they work together
They sit side by side and neither replaces the other. The rule is simple: History is the safety net, GitHub is a mirror.
| Situation | What happens |
|---|---|
| GitHub not connected | History works fully. You just have no branches and no copy outside Serenities AI. |
| GitHub connected | You get both. History behaves exactly the same as before. |
| GitHub disconnected, or its access expires | History is untouched. Your undo button never depended on GitHub. |
| You switch branch, pull, or merge | A checkpoint is saved first, so you can undo the whole thing from History. |
| You have edits you never committed | Switching stops and tells you which pages, instead of discarding them. |
Taking a page from another branch
There is no way to pull a single page across from another branch on its own — switching branches always brings the whole site with it. To copy one page over:
- Click Commit so your current work is saved to the branch you are on.
- Switch to the other branch and open the page you want.
- Copy what you need.
- Switch back and paste it in.
Every step is checkpointed, so if it goes wrong you can restore from History. If you would rather not do this by hand, ask the AI to rebuild that page for you on the branch you are already on — usually faster than moving code between branches.
Words you will see
| Word | What it means |
|---|---|
| Checkpoint / version | A saved snapshot of your whole site at one moment. Made for you automatically. |
| Restore | Put your site back to how it looked at a checkpoint. Reversible. |
| Commit | GitHub only. Save your current pages to the branch you are on. |
| Branch | GitHub only. A separate copy of the whole site you can change without affecting the other one. |
| Switch branch | Replace the pages you are editing with that branch's copy. |