Editing the code yourself
The Code tab: the file tree, what is editable, the save check, what happens when a change breaks the build, and downloading the whole project.
Last updated September 17, 2026
On this page
You never have to touch code, but you always can. The Code tab shows every file the builder wrote, and you can edit any of them in place.
The file tree
Pages live under src/pages/, shared building blocks under src/components/, helpers under src/lib/, and the routes that connect pages to addresses in src/App.jsx. Larger apps are organised into feature folders the way an engineer would.
Editing and saving
Pick it from the tree. Unsaved changes are marked.
A quick check runs first. If it spots something that would obviously break the app, it says so and offers Save anyway for when you are sure.
A saved change is compiled straight away and the preview refreshes.
When a change breaks the build
If the app will not build with your change, the editor tells you and gives you two choices: Keep my changes to carry on editing, or Discard my changes to put the file back the way it was. Your saved text is never lost either way.
Read-only files
A few files are managed by the platform and marked locked: the SDK your app uses to reach its database and accounts, and the session helpers. They are updated for you and any hand edit is overwritten on the next build. Everything else is yours.
Working with the builder on your own edits
The builder reads a file before it rewrites it, so your edits survive its later turns. If you want it to keep its hands off a file, say so.
Downloading the code
Under Settings › Copies and exports, Download the code gives you every file as a ready-to-run project. Your data and backend functions keep running on Praxivara, and the downloaded app keeps talking to them.