From install to your first AI-generated image in about 5 minutes. Or hand the whole thing to your AI assistant.
One command puts gflow on your PATH. Then install the browser engine it needs (~150 MB).
Install the CLI:
Install Chromium (one-time, required by the browser transport):
Verify the installation:
A one-time login opens a real Chrome window. Sign in with your Google account and keep going until the Flow editor loads — gflow closes the window for you and verifies the session automatically.
Use --browser chrome — the default auto picks the same real Chrome when it is installed, and only this strategy marks the profile as a real-Chrome profile.
On first run, the profile is created as default then auto-renamed to your email's local-part (e.g. your.name@gmail.com → your-name). Single-account users never have to think about profiles. To use a custom name, pass --profile myname.
The shortest happy path — one command, real output. Images are free; only Veo video costs credits.
Generate a text-to-image with the --tool creative-director flag, which expands your prompt with Google's 5-component formula before any credits are spent.
Files are saved to the output directory automatically — by default ./out/images/.
Route outputs to S3, MinIO, or GCS with external storage.
Turn that still into an 8-second Veo clip. This step costs 1 Veo credit.
Video outputs land in ./out/videos/.
If something goes wrong on this path, here are the most common errors and exactly how to fix them.
gflow auth login --browser chrome
gflow auth login --browser chrome
gflow auth login --browser chrome
gflow serve daemon or stray Chrome windows, then retry.
Everything above, an agent can do for you. Start the MCP server and point Claude, Cursor, or Copilot at it.
Just ask in plain language — the agent picks the model, aspect, and prompt tooling. See Agent-driven for the full setup.