gflow-cli 0.21.0

Unofficial CLI for Google Flow — drive Veo image-to-video generations from the terminal.

gflow-cli

Unofficial Python CLI for Google Flow. Drive Veo (image-to-video, text-to-video) and Imagen (text-to-image) from your terminal: scripted, batched, pipeline-ready.

⚠️ Unofficial, reverse-engineered, not affiliated with Google. Endpoints can change without notice. Read the full DISCLAIMER.

🌐 Headed browser today. gflow drives Flow through a persistent Playwright Chromium profile, because Google's auth and reCAPTCHA gates require it. The Architecture section shows where you can help.

Why gflow-cli?

You pay for Google AI Ultra or Pro, you have Veo credits, and you run real batch work. gflow-cli gives you:

• Batch generation. Loop prompts straight from the shell: for p in $(cat prompts.txt); do gflow image t2i "$p"; done. Image batching plus gflow video t2v / i2v / r2v all ship today.
• Consistent subjects. gflow character create mints a Flow Character (face and body reference) so the same person appears from one generation to the next.
• Pipelines. Wire Veo into your content automation, AI-video stack, or batch experiments.
• Terminal-native. After one gflow auth login, you stay in the shell. No clicking through dialogs.

Same Veo and Imagen models, same quality, same Ultra/Pro billing, now programmatic.

60-second quick start

# 1 · Install (uv recommended; also: pip install gflow-cli)
uv tool install gflow-cli
uv tool run --from gflow-cli playwright install chromium     # one-time, ~150 MB

# 2 · Authenticate (one-time, opens a real Chrome window)
gflow auth login --browser chrome

# 3 · Generate
gflow image t2i "a hot air balloon over Tokyo at sunrise"
# or:
gflow video t2v "Slow cinematic push-in on a sunlit forest clearing" --aspect 16:9
# or mint a reusable Character (face + body reference):
gflow character create --project <id> --name "Aria" --face-prompt "..." --body-prompt "..."

Outputs land under $GFLOW_CLI_OUTPUT_DIR, or you can route them to S3, MinIO, or Google Cloud Storage with GFLOW_CLI_STORAGE_URI. The first call takes 30 to 90 seconds while Chromium warms up; later calls reuse the warm session.

Why --browser chrome? Google rejects Playwright's bundled Chromium. The CLI fails fast with a friendly error (AuthBrowserRejectedError, exit code 14) if you pick anything else.

For the full 10-minute walkthrough with troubleshooting and multi-account setup, see USER_GUIDE: Journey 1.

Examples

One command in, real Flow output back. Left: gflow image t2i generating a photorealistic scene in your library. Right: a frame-to-frame transform.

Demo

A single gflow image t2i "..." --aspect 9:16 --model nano2 call against a logged-in Pro/Ultra profile. The terminal streams the run's structlog JSON, then lists the written PNG. Chromium drives the Flow editor silently in the background.

Reproduce the recording with scripts/record_demo.ps1 (Windows, OBS, ffmpeg, gifski). More formats, including the side-by-side split-screen: docs/DEMOS.md.

Documentation

docs/INDEX.md is the master routing layer. Quick links:

Topic	Read
🎯 Getting started	User Guide · Usage · Configuration
Storage & catalog	External Storage · Data Layer
🎭 Characters	Characters, reusable subjects (gflow character)
🔐 Auth & sessions	Authentication · Known issues
🏗️ Internals	Architecture · Security · Debugging
📦 Releases	Changelog · Roadmap · Release protocol · Project status
🤝 Contributing	Contributing · Development · GitHub workflow

For AI agents & LLMs

gflow-cli ships three agent entry points. Pick the one your tool reads first.

File	Audience	Tools
AGENTS.md	Universal coding-agent spec	Cursor · Codex · Aider · Gemini CLI · Jules · Devin · Windsurf · Zed · Warp · opencode · Copilot
CLAUDE.md	Claude Code's auto-loaded memory	Claude Code
llms.txt	LLM-readable summary (llmstxt.org format)	Paste into ChatGPT, Claude, or Gemini to onboard the model
skills/gflow-cli/SKILL.md	Claude Code Skill	Symlink into ~/.claude/skills/

Onboard any agent in one line. Paste this into your agent of choice:

"Read AGENTS.md and docs/INDEX.md, then help me with my Flow batch."

Architecture & current limitations

gflow CLI  →  Provider (interchangeable)  →  Flow (ui_automation) / Mock (tests) / [planned: Official Veo]
                                              ↓
                                      Playwright Chromium (headed login, headless after)
                                              ↓
                              aisandbox-pa.googleapis.com  (Google's private Flow API)

Current transport: ui_automation drives Flow through a persistent Playwright Chromium profile. It is production-stable and verified end-to-end every release (see the per-release LIVE_VERIFICATION_* evidence files).

What's blocked: a pure HTTP transport for video generation. The video upload endpoint returns HTTP 401 under non-Chrome browsers plus a reCAPTCHA mint we cannot reproduce headlessly. Three earlier HTTP strategies (evaluate_fetch, bearer, sapisidhash) live under src/gflow_cli/api/transports/experimental/ for research, off the production path.

How you can help: if you have driven aisandbox-pa.googleapis.com from outside a real Chrome session, or you understand Google's anti-bot stack here, please open an issue. A working REST transport would unlock serverless deployments, true horizontal concurrency, and roughly 10x the project's reach. Details: docs/ARCHITECTURE.md § Headed-browser dependency.

Project status

Alpha. Image (t2i, i2i, upload) and video (t2v, i2v, r2v) run end-to-end on ui_automation, with a 5-model Veo picker plus --duration and --count. Recent additions: gflow character for reusable subjects, gflow scene for credit-free server-side stitching, and gflow video chain for linked clips. Video batch is still queued for Phase B, so use a shell for-loop until then (USAGE).

Full milestone history lives in CHANGELOG.md. Where the project is heading: ROADMAP.md.

License & legal

MIT License © 2026 Flavio Oliva (ffroliva). The MIT license covers gflow-cli's code only. It grants no rights to Flow, Veo model output, or any Google service. Google's own terms (Labs Additional Terms, Ultra/Pro subscription terms) govern your generations. See the DISCLAIMER.

Acknowledgements

• edge-tts, design inspiration for community SDKs over private cloud APIs.
• googleapis/python-genai, the official Veo SDK that a future provider release may alias.
• Keysight, Google Labs – Flow AI with Veo3: A Network Traffic Analysis, an independent capture that helped validate the route patterns.

---

Stats

If gflow-cli saves you time, please ⭐ the repo. It is the cheapest way to support the project.