CLI

Introduction

Introduction

Buildprint CLI gives you a local, code-first workspace for a Bubble app branch. Instead of editing your app directly in Bubble, you pull a branch into files, make changes locally, validate them, and send the result back.

It is designed for both humans and coding agents. Humans get a reviewable local workflow. Agents get a filesystem they can read, search, edit, diff, and merge.

Typical flow

  1. Link the CLI with buildprint link <token>.

  2. See the apps your token can access with buildprint project list.

  3. Create a branch workspace with buildprint project get <appname>.

  4. Edit files inside that workspace.

  5. Run buildprint check before you apply changes.

  6. Use buildprint sync when you need the latest Bubble changes in your workspace.

  7. Use buildprint apply to send your committed local changes back to Bubble.

Core commands

  • buildprint link <token> — connect the CLI to Buildprint.

  • buildprint project list — list projects available to your token.

  • buildprint project info <appname> — inspect one project before you clone it.

  • buildprint project get <appname> [--branch <name>] — create a local workspace for one Bubble branch.

  • buildprint sync — fetch the latest Bubble snapshot for the current branch and merge it into your workspace.

  • buildprint check — validate the workspace before you apply.

  • buildprint apply — send committed local changes back to Bubble.

  • buildprint tree <target> — inspect a page, reusable, or element subtree from the command line.

  • Read File system to understand what the CLI creates on disk and what you should edit.

  • Read Workspaces to understand app roots, branch folders, and where commands should run.

  • Read Managing changes and syncing for the day-to-day workflow.

Was this helpful?