blitflow

Author and run BlitFlow AI workflows from the terminal — generate game assets, images, and other media by running single nodes or whole workflows against BlitFlow Studio.

Install

npm install -g blitflow
# or run it without installing:
bunx blitflow --help
npx blitflow --help

Requires Node.js 20 or newer. The package is a single self-contained bundle — no runtime dependencies.

First use

# 1. Sign in (OAuth device flow — approve a code in your browser)
blitflow login

# 2. Explore the node palette
blitflow nodes sprite

# 3. Run a single node
blitflow node rd-fast -i prompt="a brass key"

# 4. Run a published workflow, or a local YAML definition
blitflow run acme/[email protected] -i prompt="isometric stone tower"
blitflow run flow.yaml -i photo=@https://example.com/tower.jpg

Progress streams to stderr; results go to stdout (pipeable, --json for machine-readable output).

Commands

| Command | What it does | | -------------------------- | ------------------------------------------- | | blitflow login | Sign in via the browser (OAuth device flow) | | blitflow logout | Remove the saved token | | blitflow whoami | Show the signed-in user | | blitflow nodes [query] | List or search the node palette | | blitflow node <id> | Run a single node (no workflow) | | blitflow run <file\|ref> | Run a YAML workflow file or a published ref | | blitflow runs [id] | List past runs, or inspect one run's steps | | blitflow usage | Run/cost/error metrics for a time range |

Run blitflow --help for all options.

CI / headless use

Set BLITFLOW_TOKEN to a personal access token (created in the Studio under Settings → API tokens) instead of logging in. BLITFLOW_URL overrides the API base URL (default: https://studio.blitflow.com).

Text feedback

Create a minimized JSON report with a stable submissionKey UUID, source (cli), category (bug or feedback) and comment (1–8,000 characters). Optional reproduction, expected and actual fields each allow 2,000 characters.

blitflow feedback --file report.json --org acme --dry-run --json
blitflow feedback --file report.json --org acme --json
cat report.json | blitflow feedback --file - --org acme --json

Dry-run prints a sanitized preview without signing in or submitting. Review it before submitting. File/stdin input is limited to 64 KiB and avoids putting the report text in shell history. Reuse the same submission key when retrying; the server returns the original { id, createdAt } receipt without changing its body. All member roles may submit. Admission allows ten new reports per rolling minute per principal, across organizations. Reports become eligible for daily deletion after ninety days. There is no report-read API or public feed.

Never reveal sensitive data in feedback. Anonymize the report before submitting: replace names, emails, organization/customer identifiers and private paths with neutral placeholders. Remove API keys, tokens, passwords, cookies, authorization headers, environment variables, private prompts/assets and customer data. Include only the minimum reproduction steps and sanitized error details. Do not attach transcripts, files, screenshots or raw logs automatically. If a report cannot be made safe, omit the sensitive detail and describe the failure generally.

Known-pattern redaction helps minimize reports; it cannot recognize every private fact.