fframes studio
Windows preview

YOUR CODE. YOUR AGENT. YOUR STUDIO.

A video studio.
Built around
your code.

Describe an animated video to your AI coding assistant. Studio builds a preview you can watch. Select a scene, ask for a change, then export the finished video.

Get Studio Explore the studio

Requires your own AI assistant, such as Claude Code or Codex.

ONE WAY TO WORK / THE AGENT LOOP

A small change.
A complete loop.

For example: ask for a short title video, then select its title and say “Change the title to ‘Make your move.’” You can also select a scene or time range when individual objects cannot be selected.

Follow “Hello.” from a selected title to an updated preview. Scroll slowly, pause, or go back.

01 / SELECT

Start with what
you can see.

Click a selectable object in the preview. Studio pauses at that frame and carries the selection into your next agent task.

Object selection depends on the project’s preview worker. A selection gives context; it does not change the source.

02 / AGENT EDIT

Say what
should change.

“Change the title to ‘Make your move.’” Your agent edits the Rust project in a draft working copy.

The last working preview stays visible while the next revision takes shape.

03 / BUILD & CHECK

Put the draft
through its paces.

Studio builds the candidate, then validates it with frame inspection and audio checks. The report includes diagnostics and coverage gaps.

A failed or cancelled build keeps the previous preview. Checks report what they covered.

04 / UPDATED PREVIEW

Meet the
next revision.

A validated edit applies automatically by default. With manual review, it waits for you to choose Apply.

The accepted revision becomes the updated preview. Your video remains an ordinary Rust project.

Look inside the workflow
ANATOMY OF AN EDITILLUSTRATION · NOT A LIVE APP
An edit, separated into its working parts A selected title in the preview supplies context to an agent draft. The draft is built and inspected before a successful edit updates the preview. Pink marks selection, blue marks the draft, and green marks successful checks. This is an illustration, not a recording of the application. cargo build ✓ compiled inspect ✓ checked 03 / CHECKS Build → validate src/lib.rs · working copy <text id={title_key}> − "Hello." + "Make your move." </text> 02 / DRAFT Agent edits Rust LAUNCH FILM / INTRO Hello. Make your move. 01 / PREVIEW Select the title YOUR REQUEST Change the title to “Make your move.” title_key candidate accepted SOURCE → CANDIDATE → ACCEPTED REVISION
A selected title in the preview supplies context to an agent draft. The draft is built and inspected before a successful edit updates the preview. Pink marks selection, blue marks the draft, and green marks successful checks. This is an illustration, not a recording of the application. 03 / CHECKS Build → validate cargo build inspect ✓ compiled ✓ checked src/lib.rs · working copy 02 / DRAFT <text id={title_key}> − "Hello." + "Make your move." LAUNCH FILM / INTRO 01 / PREVIEW Hello. Make your move. REQUEST Change the title to “Make your move.” title_key candidate accepted
One selected title, an agent’s draft, and the checks between them. Simplified workflow; example artwork and code.

Connect the coding agent you use.

THE REST OF YOUR WORKSPACE

Your files. Your timeline.
A complete video workflow.

01 / YOUR PROJECT

Open files.
Keep control.

Your video is a Rust project: source, media and a timing document. Open it in your editor, keep it in Git, and bring the tools you already use.

Studio adds a workspace around those files. The project remains yours.

YOUR FILES, CONNECTEDSCROLL TO FOLLOW · ILLUSTRATION
YOUR FILES, CONNECTED Rust source, media and timing remain ordinary project files that your editor and Git use directly. Studio adds a workspace around them, builds the project and prepares a video preview. STUDIO WORKSPACE MY-VIDEO/ src/lib.rs RUST media/ MEDIA timeline.json TIMING YOUR EDITOR GIT cargo build STUDIO PREVIEW Hello. 01 Your video is a Rust project of ordinary files 02 Open them in your editor; keep them in Git 03 Studio adds a workspace around them 04 It builds the project from those files 05 Studio prepares a video preview
Rust source, media and timing remain ordinary project files that your editor and Git use directly. Studio adds a workspace around them, builds the project and prepares a video preview. STUDIO WORKSPACE MY-VIDEO/ src/lib.rs RUST media/ MEDIA timeline.json TIMING EDITOR GIT cargo build STUDIO PREVIEW Hello. 01 Your video is a Rust project of ordinary files 02 Open them in your editor; keep them in Git 03 Studio adds a workspace around them 04 It builds the project from those files 05 Studio prepares a video preview
A project structure, not a hidden document format. The preview requires a compatible project and a successful build.
02 / THE TIMELINE

Change the rhythm.
Keep the source.

Split a scene, move the outro, or trim a clip’s edge. Timing edits write timeline.json and update the preview without rebuilding Rust.

Timing edits support undo and redo. Finish or cancel an agent task before changing the timeline.

CHANGE THE CUT, KEEP THE CODESCROLL TO FOLLOW · ILLUSTRATION
CHANGE THE CUT, KEEP THE CODE A scene is split, the outro moves to the beginning and a clip edge is trimmed. Each timing change is written to timeline.json; Rust source stays unchanged. TIMELINE A / INTRO B / MAIN B₁ B₂ C / OUTRO timeline.json REV 1 REV 2 REV 3 REV 4 SPLIT · MOVE · TRIM Rust source → unchanged NO REBUILD 01 Split the main scene 02 Move the outro to the start 03 Trim the intro’s edge 04 timeline.json changes; Rust does not
A scene is split, the outro moves to the beginning and a clip edge is trimmed. Each timing change is written to timeline.json; Rust source stays unchanged. TIMELINE A / INTRO B / MAIN B₁ B₂ C / OUTRO timeline.json REV 1 REV 2 REV 3 REV 4 SPLIT · MOVE · TRIM Rust source → unchanged NO REBUILD 01 Split the main scene 02 Move the outro to the start 03 Trim the intro’s edge 04 timeline.json changes; Rust does not
Illustrative split → reorder → trim. Timing-only edits do not rebuild Rust. Timing changes are unavailable while an agent task is running.
03 / THE BUILD ENVIRONMENT

An example in.
A preview out.

Install the managed SDK from Setup, then open an example. Studio builds the project and prepares its worker, first frame and audio.

The current preview stays available while the next revision is prepared.

FROM SETUP TO A WORKING PREVIEWSCROLL TO FOLLOW · ILLUSTRATION
FROM SETUP TO A WORKING PREVIEW Studio installs a managed SDK. A compatible example project builds with it and prepares a preview worker, frame and audio before replacing the preview, which stays available meanwhile. MANAGED SDK Rust fframes SDK INSTALLED EXAMPLE </> cargo build WORKER FIRST FRAME AUDIO PREVIEW CURRENT 01 Install the managed SDK from Setup 02 Open a compatible example 03 Studio builds it with the SDK 04 and prepares its worker, first frame and audio 05 The new preview replaces the current one
Studio installs a managed SDK. A compatible example project builds with it and prepares a preview worker, frame and audio before replacing the preview, which stays available meanwhile. MANAGED SDK Rust fframes SDK INSTALLED EXAMPLE </> cargo build WORKER FIRST FRAME AUDIO PREVIEW CURRENT 01 Install the managed SDK from Setup 02 Open a compatible example 03 Studio builds it with the SDK 04 and prepares its worker, first frame and audio 05 The new preview replaces the current one
A preparation sequence, not elapsed build time. Failed or cancelled builds keep the previous preview.
04 / THE FINISHED FILE

Make the video.
Take it with you.

Choose an export format supported by your project’s worker, set the size and frame rate, and render a video file. Follow progress or cancel the export.

From editable source to a file you can share. Export capabilities depend on the project.

TURN THE PROJECT INTO A VIDEOSCROLL TO FOLLOW · ILLUSTRATION
TURN THE PROJECT INTO A VIDEO The project's preview worker exposes its supported export formats. Studio renders the chosen output with progress and cancellation, then saves the video file. PREVIEW WORKER supported formats EXPORT FORMAT from worker ▾ SIZE 1920×1080 FRAME RATE 30 fps RENDER CANCEL 001 045 090 VIDEO RENDERING FRAME 001 / 090 FRAME 045 / 090 FRAME 090 / 090 SAVED 01 The worker reports what it can export 02 Choose format, size and frame rate 03 Render: follow progress, or cancel 04 The video file is saved
The project's preview worker exposes its supported export formats. Studio renders the chosen output with progress and cancellation, then saves the video file. PREVIEW WORKER supported formats EXPORT FORMAT from worker ▾ SIZE 1920×1080 FRAME RATE 30 fps RENDER CANCEL 001 045 090 VIDEO RENDERING FRAME 001 / 090 FRAME 045 / 090 FRAME 090 / 090 SAVED 01 The worker reports what it can export 02 Choose format, size and frame rate 03 Render: follow progress, or cancel 04 The video file is saved
Illustrative frames and render progress. Available formats, size and frame rate come from the project’s worker.

START WITH AN EXAMPLE.

Make your
first move.

01   Install Studio02   Open an example03   Make it yours

YOUR NEXT FRAME STARTS HERE Download for Windows

Windows x64 · .exe installer

Release notes & other downloads ↗
INSTALL WITH POWERSHELL

One command. Your own Studio.

Per user, no administrator rights.

PS> irm https://github.com/khanhthanhdev/fframes-desktop/releases/latest/download/install.ps1 | iex

From a checkout

Then install the SDK on the Setup screen.

$ cargo run --locked --manifest-path desktop/Cargo.toml -p fframes-studio

Status  Windows is the tested platform and the preview is unsigned. Linux runs the tests in CI. macOS is not fully tested yet.