One version of the reel, checked by the director

One version instead of a choice#

AI montage now delivers one version of the reel. The director used to build an alternative with a different script as well, but it came out weaker than the main one — that time now goes into a self-check. There is nothing to pick: when the montage is ready, the project opens on the Editor section with the finished reel. The Pick a version sheet and the button with the number of versions in the project header no longer appear after a montage.

A rebuild with new settings and a retry work the same way. The montage price hasn't changed — 24 tokens.

The director checks the finished reel itself#

Once the reel is built, the director reviews it the way a viewer will: in playback order, with what is on screen and what can be heard. It straightens out the logic and order of the clips and removes cut-off thoughts, and if the plan changed, the reel is built again. On the run card this is the Polishing the cut stage; in the Chat journal — Director’s reasoning on the finished cut.

A faster montage#

Slicer watches the frames while it transcribes the speech, and prepares the editor preview while the director is thinking about the edit. The finished reel arrives noticeably sooner.

Earlier versions stay in the history#

Every rebuild, retry, style change and export still adds a new version, and the earlier ones stay in Media → History: you can bring back any of the last 10 with Make current or by asking the director in the Chat — “bring back the previous version”.

API and MCP#

• AI montage delivers one version: versionChoice is null after a montage, and the project.version_ready event doesn't arrive.
• POST /v1/projects/{id}/versions/{versionId}/choose and the MCP choose_version tool now also make current any version from the history that has a file (hasFile) — for example, the reel from before a rebuild.

The self-check of the finished reel · The finished reel · Video versions in the API