How Builds Work
What happens when fluos builds your video, and what it checks before you see it.
A build is one run of the agent that creates or changes your video. Every video is made this way, and every follow-up that changes the video starts another build.
What happens after you hit send
- Getting ready. fluos prepares your project's workspace. On a cold project this is the Booting state in the preview.
- The agent works. It reads the relevant skills, pulls in any attachments or library assets, designs and animates the scenes, and generates narration, music, or sound effects if the video needs them.
- fluos checks its own work. The result is validated and its motion is measured to see whether things actually move. Problems are repaired automatically.
- The preview updates. The status chip flips to Live and you can play it.
A build is meaningfully slower than a chat reply because all of those steps are real. Long, narrated, multi-scene videos take the longest.
Before the build starts
A new video begins with a storyboard you approve. If something important is missing, such as the product, the duration, or the tone, fluos can pause with a short question card so you can answer with a tap instead of the agent guessing. See Storyboards.
While fluos builds, a live shot list (the To-dos panel) ticks off each beat as it finishes. When you are only chatting or asking questions, the panel stays out of the way.
Refreshing or leaving the page
Refreshing the chat does not stop a build in progress. fluos keeps the run alive, and only Stop cancels it. If a project has been idle, a follow-up picks up from your latest saved version instead of starting over.
What you can ask for
You do not call tools directly — you ask for an outcome and fluos picks the right approach. Knowing what exists helps you ask for the right thing.
| Capability | What to ask for | Limits per build |
|---|---|---|
| Narration, music, sound effects | "Add a calm voiceover", "put a subtle music bed under it" | — |
| Word-level captions | "Add captions synced to the voiceover" | — |
| Review your uploaded footage | "Which parts of this clip are usable?" | 10 reviews |
| Cut a segment from your footage | "Use the 0:12–0:18 part of that clip" | 8 cuts, 60s max each |
| Browse the workspace library | "Use our logo from the library" | — |
| Read a spreadsheet | "Chart the revenue column" | — |
| Web research | "Match the style of stripe.com" | — |
| Remove a background | "Cut the person out of this clip" | See Library |
| AI video clips (MAX, paid plans) | "Generate a b-roll shot of a city at dusk" | 2 clips, 5s max each |
| AI images (MAX, paid plans) | "Generate an abstract gradient background" | 6 images |
The per-build limits exist so one slow step cannot hold up the rest of the build. If you need more, split the work across follow-ups.
Quality checks
fluos checks the motion it creates rather than assuming it works. A scene that fades in and then freezes is detected, even if it looks animated on paper.
- Breaking errors — anything that would stop the video from playing — are repaired before the preview updates.
- Visual findings — a frozen scene, overlapping elements, low contrast — never hold your preview back. fluos gives them one repair pass, publishes the new version, and lists anything left in chat as a review note with a link to the moment in the video. Ask fluos to fix a flagged scene and it reworks just that part.
- Softer observations — pacing notes, judgment calls — show as a dismissible Motion quality notes banner and never block.
A validated build is never thrown away over an opinion.
Free plan builds
On the free plan your first video is free: 300 one-time welcome credits, enough for one full video. Questions and conversation do not use credits (up to 20 replies a day) — only messages that actually commission video work.
When you are out, you get a clear message and the option to upgrade. See Plans and Credits.
If a build takes too long
Builds have a time budget. If a video is too heavy to finish inside it, the run stops with an explanation and your previous version stays exactly as it was. The usual causes are long embedded video and very long durations — shorten the footage segment or reduce the scope and try again.