All Collections

Installation and authentication

Once installed, buildprint CLI includes everything you need. The only step you need to do yourself is link the CLI to your Buildprint account so it can read and write the apps your token can access.

Buildprint CLI is not currently publicly available. It runs inside Buildprint.ai sandboxes and is used by the Buildprint agent to understand and edit your Bubble app. We may release it publicly in the future.

Run this once per sandbox:

buildprint link <token>

Generate the token from Buildprint under Integrations → CLI.

Linking verifies the token against the Buildprint API and prints the projects it can access.

Your CLI token is unique to you, and should not be shared with other users.

Where credentials are stored

The token is written to ~/.buildprint/auth.json. Treat it like an SSH key:

  • Do not check it into source control.

  • Do not copy it between machines without re-setting the permissions.

  • If you suspect it leaked, revoke it from the CLI integrations page and run buildprint link with a fresh token.

Two quick checks:

  • buildprint project list - will print the apps your token can access.

  • buildprint docs buildprint "getting started" - should return search results from Buildprint's help center.

If either returns an authentication error, re-run buildprint link <token> with a fresh token.

Was this helpful?