CLI Reference

Complete reference for all blueprint commands, flags, and environment variables.

Global Flags

These flags are available on every command.

Flag	Short	Description
--registry	-r	Path to local registry. Defaults to `$BLUEPRINT_REGISTRY` or `~/.blueprint/registry`.
--dir	-d	Project directory. Defaults to the current working directory.

`blueprint install <ref>`

Install a package from the registry into your project. The <ref> must be a fully-qualified package reference in the form @namespace/type/name@version.

Flags

Flag	Short	Default	Description
--force	-f	false	Bypass the security block for blocked packages. Use with caution — this is the only flag that overrides a hard security stop.
--yes	-y	false	Auto-approve the pre-install confirmation prompt. Safe for CI and non-interactive scripts. Does not bypass the security block — a blocked package still requires `--force`.
--dry-run		false	Show the files that would be written without writing anything.
--continue		false	Resume a partial bundle install from the last recorded failure in the install journal. Skips packages that already succeeded.
--clean		false	Remove orphaned files left by a failed bundle install, then start the install fresh from the beginning.
--platform		""	Override platform auto-detection. Accepts a comma-separated list of platform IDs: `claude-code`, `opencode`, `gemini-cli`, `antigravity`. Also reads `BLUEPRINT_PLATFORMS` env var when the flag is not set.

Examples

$blueprint install @blueprint/packages/sdlc@1.0.0

$blueprint install --yes @blueprint/packages/sdlc@1.0.0

$blueprint install --force @blueprint/packages/sdlc@1.0.0

$blueprint install --dry-run @blueprint/knowledge/go-best-practices@1.0.0

$blueprint install --continue @blueprint/packages/sdlc@1.0.0

$blueprint install --platform claude-code,gemini-cli @xadk/ai-native/skill@1.0.0

`blueprint update [ref]`

Update installed packages to their latest versions. Without a ref, all packages in the lockfile are updated. With a ref, only the matching package is updated.

Flags

Flag	Short	Default	Description
--yes	-y	false	Skip the confirmation prompt. Safe for CI.
--dry-run		false	Show what would be updated without applying any changes or modifying the lockfile.

Examples

$blueprint update

$blueprint update @blueprint/knowledge/go-best-practices

$blueprint update --dry-run

$blueprint update --yes

`blueprint list`

List all packages currently recorded in the project lockfile (.blueprint/lock.yaml). Outputs a table of ref, type, and install destination.

No command-specific flags. The global --dir flag controls which project directory is read.

Example

$blueprint list

`blueprint inspect <ref>`

Fetch and display a package manifest from the registry without installing anything. Shows the package type, description, included sub-packages, template variables, security status, file count, and a link to the registry browser.

No command-specific flags. The global --registry flag controls which registry is queried.

Example

$blueprint inspect @blueprint/packages/sdlc@1.0.0

`blueprint version`

Print the installed Blueprint CLI version string and exit.

$blueprint version

Environment Variables

These environment variables are read by the CLI and can be used to configure behaviour without passing flags on every invocation.

Variable	Affects	Description
BLUEPRINT_REGISTRY	all commands	Path to the local registry directory. Equivalent to passing `--registry`. The flag takes precedence when both are set. Default: `~/.blueprint/registry`.
BLUEPRINT_PLATFORMS	`install`	Comma-separated list of AI platform IDs to target when installing `ai-native` packages. Equivalent to `--platform`. The flag takes precedence when both are set. Valid values: `claude-code`, `opencode`, `gemini-cli`, `antigravity`.

Next steps

Browse packages →Getting Started →