Intent → Final cut
Thinkinstories.Notintimelines.
Tell it freely. Every cut comes back for you to keep, change or drop.
Hold on the ridge before the water.
Closing card over the trail.
Ease to 0.6x across the glide.
Drop 1.2s of drift before the trail.
The story is already in the folder.
Edit your clips at the speed of light.
What you have
47 clips · 1h 12mFour days, four cameras, no order. Finding it costs a day.
What comes back
1 sequence · 00:47Shots in order, cut to the track. A sequence you can change, not a render.
Simplesurface.Seriousengine.
You say it in your own words. Recut interprets and answers in frames.
- It reads intent, not keywords
The model names what you meant; deterministic code finds where. “Punch in on the drop” becomes one exact operation.
- It watched the footage first
Shots, spoken words and the beat grid are found on import, so it edits from what is actually in the file.
- One change, one undo
You and the agent write through the same typed operations. Whatever you accept lands as a single step.
- Time that never drifts
Every edit is an exact rational, not a float second. Cut all day at 29.97 and the beat still holds.
In your words
“45-second trailer from this folder”
Plan: 4 sections, 12 shots, out at 0:45
“cut it to the music”
14 cuts placed on the beat grid, 128 BPM
“punch in on the drop”
Scale 1.00 → 1.18 at beat 32, 0:11.4
“caption what she actually says”
9 cards, verbatim from the transcript
“the middle drags”
Section 2 retimed, 0:31 → 0:18
Each one arrives as a proposal. Nothing lands until you say so.
Getearlyaccess.
Free to start. No credit card.