Code, Terminal & Saving
Alongside the agents and the preview, every project has a code editor, a terminal, and a simple save flow.
Code editor
Section titled “Code editor”Switch the toolbar’s Preview / Code toggle to Code to browse and edit the project’s files. Edits you make here and edits the agents make are the same kind of change: they show up in the preview right away and are kept until you save or clear them.
Terminal
Section titled “Terminal”The bottom panel has:
- Terminal tabs — bash shells in the project’s sandbox. Open more with New terminal to run commands while an agent works.
- Server — the dev server’s log.
- Console — the preview’s browser console.
On the browser runtime, install packages with npm install. On the server runtime, use bun add.
Saving changes
Section titled “Saving changes”Changes from the agents and the editor collect as unsaved changes, counted in the toolbar (for example, 12 changes):
- Save keeps them as a new version. Saving is what makes changes part of the project: it’s what other members see, what Share builds from, and what you publish.
- Clear discards every unsaved change and returns the files to the last saved version.
If another member saved changes to the same files in the meantime, Frontend shows the conflicts before saving so you can choose what to keep.
Download the code
Section titled “Download the code”Download a zip of the project from Settings → Advanced → Export Project. To keep the code in your own repository, connect GitHub.