Offline use

You don't need a Buildprint account to see your app as BubbleScript. Export your app from Bubble and open it with the CLI. Everything runs on your machine.

Note that features like issue checking, editing, and database access require a Buildprint account.

1. Export your app from Bubble

In the Bubble editor, go to Settings → General → Export application. Bubble downloads a .bubble file for the current branch.

Bubble removes private keys and other secure settings from exports, so the file has no API secrets.

2. Install the CLI

npm install -g buildprint

3. Open the export

buildprint open ./my-app.bubble

This creates a BubbleScript workspace at ./<appId>/export/. It contains the same files as a cloned branch: pages, reusable elements, workflows, backend workflows, data types, option sets, styles and settings. Use --dir <path> to choose where it goes.

4. Point your agent at it

Open the export folder in Claude Code, Codex, Cursor or any coding agent, and ask about your app:

• "Explain how the checkout flow works, from button click to database write."

• "Which pages show or change the Order data type?"

• "Find workflows that run without a privacy check."

• "Write documentation for every backend workflow."

You can also run checks without an account:

buildprint check    # validate the BubbleScript
buildprint audit    # scan the app for security and quality issues

What an export workspace can't do

An export workspace is a read-only snapshot. Editing is unsupported, and plugins are not supported (so this may mean some BubbleScript is expressed as raw JSON where it involves a plugin action/element).

To have an agent build and change your app, sign up for Buildprint, connect your app and clone a live branch:

buildprint link <token>
buildprint project clone <appId> --branch test