Cards come off the camera once. From then on the footage lives in Osmo Cloud, an AI editor can cut it from a brief, and human editors pull any cut into DaVinci Resolve, change it, and push it back. Every version is kept. Color only downloads the seconds the final cut uses.
osmo-dit copies and verifies every card, and makes small editing proxies that keep the camera's name and timecode.Think of it as Google Docs version history for a timeline, with one rule: nothing is ever overwritten.
Every push is a new numbered version (v1, v2, v3...). It's never changed or deleted. Any version can be pulled again.
A line of work. main is the cut. agent is what the AI made. Make your own for a cutdown, like nik/30s.
The latest version on a branch. "Pull main" means "pull the head of main".
"I'm cutting main right now." Others can still push, but their version is saved beside yours instead of replacing it. Lasts 12 hours, or until you release it.
His v8 becomes the head of main.
Her v9 is saved, but main stays on Nik's v8. Resolve tells her: "main moved on while you worked (now v8, by Nik). Your version is saved beside it."
and sees exactly what Nik changed ("head trimmed 12 frames at 0:42, 1 clip moved"). Then she either makes hers the head, or pulls v8 and carries her idea over. Nobody's work disappears.
| part | what it is | why |
|---|---|---|
| OTIO | The timeline in an open format: which clips, which source timecode, where. | The AI reads it, diffs are made from it, color conform comes from it. It works in Resolve and Premiere. |
| .drt | Resolve's own timeline file, attached automatically on every push from Resolve. | Keeps what OTIO can't: effects, color, titles, speed ramps, the mix. Pull opens it when it's there. |
| files | Never inside a version. Clips point at the original file names plus timecode. | Each person's machine links to its own copy: editing proxies for editors, camera originals for color. |
/agents: write a brief, pick a playbook, watch the AI cut live. When it's done you get an email with a watch link: play it on your phone, tap a line to jump there, pin notes to a moment, send them for the next version.
Send them a cut's watch link (Copy a link to share, on the cut's page). They watch that one cut on any phone, no account, nothing else in the project, and leave notes pinned to a moment. You get one email per burst of notes, and one click turns them into the next version. Links last 30 days; you can turn them off any time.
/editors once to set up. Then in Resolve: Workspace > Scripts > Edit > Osmo > Pull, Push, Changes. The Osmo Edit menu bar app tells them when someone pushes and downloads cuts ahead of time.
/versions: open the locked version and get its conform list. Pull it with the camera originals.
/versions shows every branch, who has what checked out, and what changed between any two versions.
| thing | where |
|---|---|
| footage, proxies, previews, .drt files | Osmo Cloud (cloud.osmo.inc, stored on Wasabi), in each project's folder. Osmo files sit in its _osmo subfolder. |
| projects, transcripts, versions, branches | Selects (transcripts.osmo.inc), on Cloudflare |
| the AI editor | The Mac mini in the server room. It runs Claude with the editing tools, renders previews, and uploads them. |
| your local copies | ~/Movies/Osmo Cache/<project>/media. Safe to delete; pull downloads them again. |
At most $10 per AI edit, $40 a day, and 2 tries per job. Spend shows on /agents.
Every 5 minutes it checks the mini, transcription, stuck or failing jobs, failing edits and spend. It emails once when something breaks, again every 6 hours, and once when it's fixed. The same problems show at the top of /agents.
The mini turns itself back on, logs in, and restarts the AI editor on its own.
Monday 9am: the week in one email. Cuts made and what they cost, versions pushed and by whom, picture locks, footage indexed, anything that failed.
Every change runs about 200 automatic checks, including a full pull and push inside real Resolve, before it goes live.