Branches, versions and locked pages
Three safety nets let you change an app without fear: branches for trying something big, versions for undoing, and locked pages for things the AI must never touch.
Branches#
A branch is a copy of the app's files with its own live preview. Use one for a redesign, a new pricing page or any change you are not sure about. The live app and every other branch are untouched until you decide.
Create#
From the builder, create a branch and give it a name such as
redesignorspring-menu. This copies the files only; nothing starts running yet.Activate#
Open the branch to start its own preview. The preview has its own address, separate from the app's real one. Reopening a branch later wakes it again.
Edit#
Chat-edit the branch exactly as you would the app. Changes save to the branch only, and the branch preview updates in real time.
Decide#
Compare the branch preview with the live app. Keep working, discard the branch, or re-apply the changes you liked to the main app by chat.
| Per branch | Shared with the app | |
|---|---|---|
| Files and pages | Own copy | |
| Preview address | Own address | |
| Database and sign-in | Shared with the live app |
A branch cannot make database changes that diverge from the live app. For design, copy and most feature work you will not notice. Merging a branch back automatically is on the roadmap; until then, describe the winning change on the main app.
An idle branch's preview scales down after a while to save resources and wakes when you open it. Idle branches cost nothing.
Versions and rollback#
Before every AI edit the app's working files are snapshotted. The dashboard lists these versions with the time and the request that produced them.
- A change that breaks the build is never deployed. The last working version keeps serving, the broken files are reverted, and the chat tells you what failed.
- Roll back on demand. Pick any version and restore it. Your data is not affected, only the app's files.
- Up to eight recent versions are kept per app.
Locked pages#
Lock a page or file and the AI will not modify it, however you phrase a request. Use it for a legal page a lawyer approved, a landing page that converts, or anything hand-tuned.
- In the builder, open the lock control next to the attachment button.
- Tick the pages to protect. Page-like files are listed first; Show all files reveals the rest.
- Locks save as you tick. The badge on the button shows how many files are protected.
When a request touches a locked page, the planner routes around it (it will put the change elsewhere, or tell you it cannot), and a hard guard restores the locked file after the edit even if the model tried. Locks apply to every editing path: the chat, modify requests, and the API.
Using it from an assistant#
Branches are available as tools in the MCP integration: list_branches, create_branch, activate_branch, delete_branch. Versions and locked files are available over the API.