DemoBitesRecording in the cloud
Describe the demo you want and an agent films it. It opens your product in a real browser, moves a real cursor, clicks real buttons, and the take arrives in Bite Studio as an editable Bite rather than a video file.
How a run works
Nothing to install, and no terminal, so anyone on the team can use it. You give it one domain and one prompt. A planner walks the site, photographs a storyboard, and waits for you. Once you approve, it films, and the take lands in your review queue.
Plan
A real browser walks your site and photographs every step.
Approve
You edit the zooms and the narration, then say go.
Film
It records exactly what you approved, then emails you.
The storyboard
Before a single frame is filmed, a planner opens your site in a real browser and walks it live. It can type into search boxes and move between pages, and it photographs every step as it goes. The first frames appear in roughly 25 seconds and a full journey is usually planned in about a minute.
What you get back is an approval page: a real screenshot per step, a draggable and resizable zoom box on each one, and the narration script beside it. Comment on individual steps or on the whole thing. Approving films it verbatim; leaving feedback triggers one automatic rework and then films.
Then it films
Filming happens in a disposable sandbox driving a browser on a residential connection, which is why sites that block datacentre traffic still record. A per-take clock keeps the zooms and the cursor in sync even on pages that load slowly. When the run finishes the take lands in your review queue and you get an email with a link straight to it. Runs still in flight show live status there, and failures show the actual reason.
Recording behind a login
Most of a product only exists after someone signs in, so the cloud lane supports it through a live handoff: you sign in yourself, in a real browser window. Your password goes to the application you are signing in to and never to us. What we keep is the resulting browser session, encrypted, reusable across runs, and revocable by you at any time.
Signed-in recording in the cloud is part of the paid plans, from Grow up. Recording public pages is available on every plan, including Free. The skill lane needs none of this: it uses the session already open on your machine.
Limits
- The cloud lane films websites and web apps. For desktop applications, use the native recorder.
- One recording per run. There is no batch mode that generates a library while you are away.
- Bites work best between 30 and 45 seconds. 90 seconds is the hard ceiling, and the recorder will suggest splitting anything longer.
- Runs are counted against the Bites on your plan, not metered per minute or per token.
The other lane
If you live in a coding agent, the skill lane is usually the better fit: it films on your own machine, in a browser you are already signed in to, and your agent has read the code before it starts. None of the sign-in handoff above applies there.