Flova CLI Guide for AI Agents

Flova CLI lets you use Flova from external agents such as Codex and Claude Code. You can copy the setup prompt into the agent you are using, and it will install and load Flova CLI and the Flova Skill, connect to your Flova account, then help you create projects, drive generation, read project state, and export the final video in natural language.

This is not the same as using Flova as a single image or video generation API. Flova CLI connects to the full Flova project system: project requirements, chat history, storyboard, media, documents, and timeline all stay inside the same project. The external agent talks with you, calls the CLI, and reports progress; Flova keeps advancing the video creation work inside the project.

When to use it

Use Flova CLI when you already work in Codex, Claude Code, or another agent environment and want that agent to participate in video creation. For example:

• Work in Codex on scripts, references, or product notes while asking Flova to create the video project.
• Ask Claude Code to call Flova and generate the storyboard, media, and final edit from your natural-language request.
• Let an external agent read the real Flova project state instead of describing progress from memory.
• For long generation or export tasks, let the agent keep watching the task status and report back with the project link and final result when it finishes.

How setup works

Open the Flova CLI page in Flova, then hand Flova to the agent you are using:

Copy the setup prompt

Send the text below to the AI agent you are using. It installs and loads Flova CLI and the Skill, guides you through sign-in, then continues creating with the Flova Skill.

Example:

Please help me install Flova CLI: https://cli.flova.ai/flovaCLI-setup.md

Describe the video

Describe the video as you would in a normal AI conversation. Include the video goal, length, aspect ratio, style, key content, and final delivery expectation. If you want to choose the right Flova Skill first, ask the agent to recommend options before creating the project.

Example:

Use Flova to make a 30-second, 16:9 warm fantasy narrative short:On a blackout night, a small robot living on a city rooftop discovers a glowing seed and overcomes obstacles to deliver it to a lost little girl downstairs.The pacing should be clear: use the first 5 seconds to set up the blackout and introduce the robot, the middle to show it delivering the seed, and the ending to show the city lighting up again.Before production starts, recommend 2-3 suitable Flova Skills, explain why each one fits, and wait for me to choose before creating the project.

Choose and keep reviewing

As the project progresses, review the work, give feedback, and tell the agent what has already been approved and what should change next.

Example:

The storyboard is approved overall, but the third shot is too dark. Only adjust the third shot, do not change the confirmed character design, and continue production after the adjustment is done.

The agent follows the setup prompt to install Flova CLI and read the Flova Skill, which explains how to create projects, upload materials, send creative instructions, wait for generation results, read project state, and export videos.

In most cases, the agent connects to your Flova account through browser sign-in. It opens an authorization page; after you sign in to Flova and approve the request, the local CLI can continue with your account permissions.

If the agent cannot open a browser, or if you want to authorize an external agent directly, you can generate an Agent API Key from the Flova page or account settings and provide it through a secure channel. An API Key grants access to your Flova account, so treat it like a password. You can revoke it whenever you no longer need it.

What the agent can do

After setup, an external agent can use Flova CLI to:

• Create a new project or continue an existing one.
• Upload images, videos, audio, or documents as project materials.
• Send natural-language creative instructions to Flova so it can advance the storyboard, media generation, audio, timeline, and export preparation.
• Read the project's storyboard, media, documents, chat history, and export status.
• Keep checking task status during generation or export, and recover local observation if it was interrupted.
• Start export when the video is ready, then report back with the project link, final video, and current status.

Relationship with the Flova web app

Projects created or advanced through the CLI are still regular Flova projects. You can return to the Flova web app at any time to review the storyboard, Media Space, Docs panel, and Timeline, or continue editing directly in the web app.

The same is true in the other direction: an external agent can continue working on an existing web project. It reads the current project state, then continues based on the real storyboard, media, documents, and export readiness.

Usage tips

• Tell the agent the video goal, length, aspect ratio, style, key points, existing materials, and final delivery expectation.
• Avoid only saying "continue generating." It is better to state the current stage and next step, such as refining the storyboard, generating keyframes first, or exporting after the timeline is ready.
• Ask the agent to read project state before reporting progress, so it does not guess from earlier conversation.
• Share API Keys only with agents you trust. Do not put them in code, logs, or shared documents.
• For long generation or export tasks, do not treat a local CLI interruption as project failure. The Flova backend task may still be running, and the agent can recover progress through the CLI.