REEL 01THE TAKE

A deploy flow,
shot in one take.

23 seconds, unedited, delivered exactly as the agent handed it over. It drove a real browser through a real deploy — the file lands, the project gets a name, the build goes out — and a measured camera shot it from the plan it had already written.

demos/deploy.mp4 — 23 s, 1920×1080, unedited
No cuts, no second attempt. The raw capture behind this file is still on disk, which is why a change of mind here costs a re-render and not another deploy.
BEAT SHEETWHAT THE CAMERA DECIDED

Seven beats, one move.

Only one beat gets a zoom. That restraint is the editorial: a camera that punches in on everything says nothing about what matters. Pick a beat to jump there.

  1. Wide — establish

    The app arrives whole, at full frame. Nothing moves until the viewer has it.

  2. The drop — held at full frame

    index.html is dragged onto the target and the page lights up with drop to deploy. This is the thesis of the demo, so the camera refuses to punch in — cropping here would trade the whole gesture for a detail.

  3. New Project

    The panel opens with the uploaded file listed. The camera stays wide while the cursor travels.

  4. Punch in — the name field

    The only zoom in the take, and it departs on the keypress rather than before it. Framed so the name field and the Deploy button share one held frame — the two things the beat is about, and nothing else.

  5. Upload, held

    Uploading 1 of 1, and Deploy takes its spinner. The frame does not move while the work happens.

  6. Release — the deployment panel

    The camera pulls back out to logs, summary and domains. The release runs about 1.8× slower than the punch-in went in; a fast one reads like a flinch.

  7. It lands

    Congratulations, and the dashboard fills in. The take holds on the result instead of cutting on it.

PRODUCTIONHOW IT WAS SHOT

Nobody operated a recorder.

The agent explored the app first, wrote the beats above as a plan, then drove the browser against that plan. Because it wrote the plan, it knows every click, coordinate and timestamp — so the zoom follows ground truth instead of guessing at intent from cursor motion the way a screen recorder has to.

Everything cinematic here — the punch-in, the hold, the release, the cursor — lives in a readable composition.json beside the kept capture. The mp4 is a render of that file. See what a take is on disk.

  • Duration23 s
  • Resolution1920 × 1080
  • Zooms1 of 7 beats
  • Punch-in≈ 730 ms
  • Release≈ 1.8× slower
  • Edit passesnone

ROLL CAMERA

Your app deserves
one of these.

How it works Get started Star on GitHub