Version Control

Every change is committed to a private GitHub repository managed by Proyecta. Browse and switch between previous snapshots using the version dropdown in the builder toolbar.

Every change the AI makes to your app is committed to a private GitHub repository managed by Proyecta. Your code is always accessible and exportable from the builder.

Version History

Use the version dropdown in the builder toolbar to switch between snapshots. On mobile, access Version History via the More menu. While viewing a historical version, click Open history in the version banner to see the full version list. Each version shows:

• Its version number (e.g. “v12”)
• A label (e.g. ‘v1 (pre-cloud)’ for the initial frontend-only snapshot, or blank for iteration versions)
• The creation timestamp in your locale
• The first 7 characters of the git commit hash

Opening a previous version

Click any version card to open that snapshot in the preview. Historical versions open in read-only mode — you can inspect the code and preview, but you can’t edit from inside a historical view.

While you’re browsing a historical version, a banner below the toolbar shows “Viewing version N in read-only mode.” Click Return to latest in the banner to go back to the current working state and resume editing.

If you’ve never edited anything, the sheet shows “No snapshots yet — versions are created automatically after builder turns that commit changes.”

How do I actually revert?

One-click revert from the Version History sheet is on the roadmap. Today, you have two options:

1. Ask the AI — "Revert the last change", "Go back to how the homepage looked in version 6", "Undo everything from the last three commits". The AI reads the history and applies the reverse commit for you.
2. Use git in the Terminal — for precise control:

# View recent commits
git log --oneline -20

# Revert a specific commit (creates a new commit undoing it)
git revert <commit-hash>

# Or reset to a specific point (destructive)
git reset --hard <commit-hash>

GitHub

Your project code is stored in a private GitHub repository managed by Proyecta. You can access the code directly from the code editor inside the builder, or export it. If you have connected your own GitHub organization, the repository will be created there instead.

FAQ

What’s included in each version?

Code changes, configuration updates, and schema modifications — everything that lives in git. Assets stored outside the repo (like uploaded files and database records) are not versioned.

Can I create branches?

Yes. Use the Terminal to create and switch branches: git checkout -b feature/new-homepage. The AI will commit to whatever branch is currently checked out.

How do I collaborate with my team?

Multiple team members can access the same repository on GitHub. Use standard git workflows (branches, pull requests) for collaboration.

Coming soon

• One-click revert — a “Revert to this version” button in the Version History sheet that creates a new version matching an older snapshot
• Custom version tags — name individual versions so they’re easier to find later