Docs

How to make marketing video and images with vosso: recording, the studio, the vos CLI, the API, and the loop that lets a coding agent work on the same video you do.

Agents: every page serves its markdown at /docs/{page}.md, indexed at /docs/llms.txt.

Guides

What vosso is and how to record, edit, export and share with it.

What is vossoStartMarketing video and images from anything you bring, as an editable program.Make your first videoStartRecord your screen, let the studio plan the camera, and export a finished clip.Let an agent make itStartInstall the vos skills and ask your coding agent for a product video in one message.What the studio shows and whyEditOne editor for recordings and programs: the rows, panels and rail come from what the document contains.HTML layers: point at a component, sharp at any sizeEditA UI component authored as markup and CSS, composited over the footage and rasterized from source, so the thing the video is about is never the blurriest thing on screen.ExportShipFormats, quality presets and frame rates, and what stays free.Publish and shareShipVisibility, the watch page, remixing, and embedding a vos anywhere.Store listingsShipScreenshots, tiles and the marquee from one take, at the exact sizes the Chrome Web Store wants.Every releaseShipThe release loop: one editable take becomes the demo, the listing and the social cuts, and the next version re-renders it.

Agents

The contract that lets a coding agent make and iterate on videos with you.

The agent contractStartThree altitudes of agent access, and where the machine-readable contracts live.Install the skillsStartOne install line gives your agent the whole vos workflow.Push and pullThe loopHost agent work as a private vos, and sync human studio edits back down.Versions and conflictsThe loopThe version chain, the stale-base ritual, and why humans win by default.Folders and recipesStylePull a project folder before creating, so new work lands in the owner's style.CredentialsAccessContent keys, remix grants, claimable pushes and the browser sign-in.

CLI

The vos CLI: record a scripted flow into a take, edit JSON, render deterministically.

Install and log inStartOne package, one binary, and the browser sign-in that stores a key for you.The take directoryStartThe unit of work: recording, cursor track, the replay recipe and the editable doc.VerbsReferenceEvery vos command, from the one-shot create to the hosted push and pull.actions.jsonReferenceThe flow recipe: steps, selectors, how pacing becomes the zoom plan, and how an agent-browser walk becomes one.doc.jsonReferenceThe editable document: zoom, segments, speed, tilt, audio, overlays and frame.

API

The HTTP surface under vos.so/api: auth, programs, versions and the changelog.

Overview and authStartBase URL, the two credential shapes, and what a key can never do.The config formatContentWhat a VosConfigJson is, why a stored one must declare its version, and how to validate before you push.Voses and versionsContentCreate, read and iterate programs over HTTP, with lineage and typed changelogs.FontsCatalogsThe hosted webfont catalog: families, weights and file URLs, generated from the product module.Music and SFXCatalogsThe CC0 audio catalog: loudness-normalized tracks and built-in SFX with their hosted URLs.3D typefacesCatalogsThe hosted faces extruded 3D text renders from, and how to name them.BackdropsCatalogsThe hand-picked loops behind a take: the public set, its wire shape, and how a doc keys one.LimitsCatalogsThe free plan limits as a public endpoint: the recording cap every recorder states, and the quotas behind every refusal.