Version History
Every successful build is saved, and any of them can be brought back.
fluos saves a version each time a build validates successfully. Nothing is overwritten, so an experiment that goes wrong is never expensive.
Open Version history in the sidebar while a project is open.
What you see
Versions are listed newest first on a timeline. Each entry shows:
- Version number and a Current badge on the one that is live
- The prompt that produced it, so you can recognize it without playing it
- When it was saved
- Duration, FPS, and resolution
That metadata line is genuinely useful: it is the fastest way to spot the build where the duration or aspect ratio drifted away from what you asked for.
Restoring
Press Restore version. That version becomes the live one for the project, and you land back in the chat.
Two things worth knowing:
- Restoring does not delete anything. The version you were on stays in the list, so you can bounce between two directions freely.
- Your conversation stays intact. Restore changes the composition, not the chat. Follow-up messages after a restore build on the restored version.
Use it as a safety net, not a last resort
Before asking for a big stylistic change, note which version you are on. If the rewrite goes sideways, restoring takes one click — much cheaper than trying to describe your way back.
Versions are per project
History is scoped to the project, not to a single chat. If a project has several chats exploring different directions, their builds all appear on the same timeline.
When history is empty
A project with no successful builds has no versions. Failed builds are not saved — only validated output makes the list.