All Collections

Exploring an app

Once you are inside a branch workspace, five commands cover everything you need to understand an app without opening Bubble: summary, tree, context, schema, and docs.

Top-level surfaces: summary

buildprint summary

Lists pages, mobile views, reusable elements, global elements, data types, option sets, styles, and API connector calls. Each entry shows the display name, the Bubble id, and the file path you can open.

Use buildprint summary --json for a machine-readable form when scripting.

Element and workflow trees: tree

buildprint tree <target>

Target is a page, reusable, mobile view, or element. You can pass the folder key, the friendly name, or the Bubble id.

Useful flags:

  • --include <list> — comma-separated set of extras. Choices: text, types, ids, paths, layout, design, properties, workflows, actions. Default is types,ids. actions implies workflows.

  • --cursor <n> — pagination offset. Tree output is paginated 250 lines at a time; the footer tells you the next cursor.

Relationships for one node: context

buildprint context <node-id-or-name-or-file-path>

For a single node, prints:

  • Subject — what you asked about.

  • Contained By and Contains — hierarchy.

  • Triggered By and Triggers — workflow wiring.

  • References and Referenced By — reads and writes elsewhere in the app.

  • Instantiates Reusable and Instantiated By — reusable wiring.

For elements the output also includes a ## Tree section with up to five ancestors and five levels of descendants.

If a name or id is ambiguous, the command exits with a list of candidates so you can retry with a fully-qualified path.

Bubble schema lookups: schema

buildprint schema [query...] [--category <name>] [--action-type <type>] [--element-type <type>] [--limit <n>]

Searches Buildprint's copy of Bubble's static schema — every operator, action, element type, workflow type, surface, and so on. Use it when you are unsure what shape a node expects.

Examples:

buildprint schema "append text"
buildprint schema --category actions
buildprint schema --action-type CreateThing

At least one of a query, --category, or a context filter must be provided.

Documentation lookups: docs

  • buildprint docs buildprint <query> — search the Buildprint help center from inside the CLI. Use --limit to tune the result count (default 5, max 50).

  • buildprint docs bubble — fetch Bubble's own llms.txt payload for quick access to Bubble manual entries.

Tips

  • Start new tasks with summary to get a map of the app before drilling in.

  • tree --include properties,workflows is the fastest way to understand what a page actually does.

  • context is much cheaper than tree when you only care about one node's neighbours.

Was this helpful?