File system

When you run buildprint project get <appname>, Buildprint creates a local folder structure for one Bubble app and one Bubble branch. The goal is to give you normal files and folders to work with instead of one massive app export.

What you will see

<app-root>/ — the app root. It holds shared state for that Bubble app.
<app-root>/<branch>/ — the branch workspace. This is the folder you actually work in.
<app-root>/.buildprint/ — internal Buildprint state shared by the app root. Leave this alone.
pages/, styles/, data_types/, option_sets/, api/, and related folders — the editable app surface.

Inside the branch folder, Buildprint breaks the app into smaller files. That makes diffs easier to read, merge conflicts easier to resolve, and agent edits much more targeted.

What to edit

Edit files inside the current branch directory, such as page files, element files, styles, API definitions, and other Bubble entities.
Use normal git tools like git status and git diff to review what changed.
Use buildprint tree <target> when you need a quick outline of a page, reusable, or element subtree before you edit.

What not to edit

.buildprint/ — internal Buildprint state. It is not part of your editable app surface.
.git/ and git internals — treat the workspace like a normal git repo, but do not hand-edit git metadata.
Anything outside the current branch folder unless you intentionally want to work on a different branch workspace.

What this layout does

Keep changes local and reviewable.
Makes merges work with ordinary git tools.
Give agents files they can search and edit without needing to reason about the whole app at once.

If you are looking for branch management and where commands should run, continue to Workspaces.

Was this helpful?