vossodocs
Open studio
  • Overview
  • With your agent
  • What is vosso
  • Make your first video
  • Keyboard shortcuts

Studio

    • Install the recorder
    • Record a tab
    • Record a window or the screen
    • Webcam and microphone
    • Tab and system audio
    • Take a screenshot
    • Record without the extension
    • Bring a video file
    • Record with the CLI
    • Record a desktop app
    • Zooms
    • Adjust a zoom
    • Add and delete zooms
    • Camera styles
    • Follow the cursor
    • Tilt
    • Cursor and clicks
    • Trim and split
    • Speed
    • Freeze
    • Range chips
    • Add footage and transitions
    • Text
    • Media
    • Reuse a file
    • HTML layers
    • Live layers
    • Soundtrack
    • Voice and levels
    • Backdrop
    • Card and frame
    • Webcam
    • History
    • Save and autosave
    • Projects and recipes
    • Files
    • Export a video
    • The program itself
    • Publish
    • The watch page
    • Embed a vos
    • Remix and duplicate
    • Every release

Agents and code

    • The agent contract
    • Install the skills
    • What your agent does on your machine
    • Bring a Remotion or HyperFrames video
    • Push and pull
    • Versions and conflicts
    • Folders and recipes
    • Credentials
  • Start

    • Install and log in
    • The take directory

    Reference

    • Verbs
    • actions.json
    • doc.json
    • HTML layers
  • Programs

    • Overview and auth
    • Config format
    • Voses and versions

    Catalogs

    • Fonts
    • Music and SFX
    • 3D typefaces
    • Backdrops
    • Limits
Back to vos.so

CLI › Start

The take directory

The unit of work: recording, cursor track, the replay recipe and the editable doc.

previous← Install and log innextVerbs →

A take is the unit of work: one directory holding the footage, the script that produced it, and the editable document that turns footage into a video. Everything the CLI does reads or writes this directory.

Text
take/
  recording.webm   encoded footage (constant-frame-rate WebM)
                   or recording.mp4, when a pull brought it home as mp4
  frames/          raw screencast JPEGs, kept for re-encode (deletable; ~1GB at 2K)
  cursor.json      synthesized cursor track: exact coords, element rects
  meta.json        recording metadata (producer: "cli")
  actions.json     the script that produced it, the replay recipe
  doc.json         the editable document, THE product artifact
  vos.json         hosted tracking (vos id, base version, origin and account), written by push and pull

A take of a desktop app (vos record --app) holds recording.mp4, cursor.json, meta.json and doc.json, and no frames/. The cursor track is the real pointer's path over the window, and meta.json says producer: "desktop". A performed take has no actions.json, because nothing scripted it. A scripted one (--actions) keeps its actions.json and its steps in meta.json, like a page take.

Why this shape matters

doc.json is the product. Zoom and pan are spans, trims are segments, pacing is speed spans, all plain JSON. Editing the document and re-rendering never re-runs the browser; fixing a zoom is editing a number. The renders are deterministic: same take plus same doc equals same pixels. Never re-record to fix pacing or framing.

The cursor track is synthesized, not observed. Because the CLI issues every input itself, cursor.json carries exact coordinates, exact timing and fresh element rects, plus typing pings during type steps (when and where typing happens, never the text). That precision is what powers element-aware auto zoom, typing zooms and click effects downstream.

actions.json makes the take reproducible. The same script against the same page produces the same take, which is why iterating on the document beats re-recording: the flow is already captured.

vos.json is the thread to the cloud. Push writes it, pull repoints it; it records which hosted vos this directory belongs to, which version you last built on, and which account it belongs to, so a verb on the directory uses that account's stored credential before the one in use.

Related

  • actions.json for writing the flow.
  • doc.json for the full document reference.
  • Push and pull for the hosted loop vos.json tracks.