Git Version Control
Every project gets its own private git repository, hosted by Frontend. Your project’s sandbox is a clone of it, so you and your agents can use git exactly as you would on your own machine: commit, push, pull and work on feature branches.
Use git in the sandbox
Section titled “Use git in the sandbox”Open a Terminal tab in the project and run git as usual:
git statusgit checkout -b feature/pricing-pagegit add -A && git commit -m "Add the pricing page"git push -u origin feature/pricing-pagegit pullAgents can run the same commands, so you can ask Claude Code, Codex, OpenCode or Pi to commit their work, start a branch for a feature, or pull what a teammate pushed.
Save changes
Section titled “Save changes”You don’t have to use the terminal. Changes from agents and the editor collect as unsaved changes, counted in the toolbar:
- Save commits them with a message written for you, brings in anything teammates pushed to the same branch, and pushes to the project’s repository.
- Clear discards every unsaved change and returns the files to the last commit.
Save always works on the branch the sandbox is on. If a teammate changed the same files, Frontend shows the conflicts before saving so you can choose what to keep. See Saving changes.
Feature branches
Section titled “Feature branches”Create a branch in the terminal with git checkout -b, and Save pushes your work to it. The sandbox stays on that branch: the next time you open the project, it picks up where you left off. Merge the branch back into main with git merge when the feature is ready.
Browse and restore commits
Section titled “Browse and restore commits”Open Git in the project’s sidebar to see the commits on the current branch, newest first, with each one’s message, author and time.
Click Restore on any commit to bring the files back to how they were. The restore is added as a new commit, so the commits after it stay in the history and you can go back to them. To put the restored version live, deploy again.
Clone the repository
Section titled “Clone the repository”To work on the project outside Frontend, open Settings → Git. It shows the repository’s clone URL, a username and an access token, and the full git clone command. The token belongs to your team: every member can clone and push this project and the team’s other projects.
Commits you push to the repository from elsewhere reach the sandbox the next time it saves or starts.
Sync with GitHub
Section titled “Sync with GitHub”Connect GitHub to keep a copy of the project in a repository you own. After every push, Frontend pushes every branch to the GitHub repository, so your feature branches show up there too and you can open pull requests from them.
Syncing goes one way, from Frontend to GitHub. When you start it, the GitHub repository’s branches and history are replaced with the project’s. Commits made directly on GitHub aren’t brought back into the project.