OpenVids

OpenVids is an open-source, agent-first AI video editor for macOS and Windows. Instead of assembling a film by dragging clips onto a timeline from the first frame, you describe the film you want and AI agents do the assembly work: they build the chapters, cut the timeline, add motion and sound, and review the render. The product is described on its own site as free and open source, and it is distributed as a downloadable desktop application with a build for Apple Silicon Macs and a build for Windows, alongside a public source repository on GitHub. Its stated premise is simple: you direct, and the agents edit. The problem OpenVids sets out to solve is stated directly on the site: "Every project starts with a story. Then the timeline grows faster than the story does." As the page puts it, you lose the thread somewhere around clip two hundred — the story that was clear at the start becomes buried under the growing volume of clips, cuts and edits required to finish it. The team behind OpenVids says they wanted the story to stay visible the whole way through, and that goal shapes the structure of the editor rather than being an afterthought. Instead of treating the timeline as the only source of truth, the product keeps the story itself visible as a first-class part of the project. The central capability is agent-driven editing by description. The site's own summary of the product is that you describe the film, and agents build the chapters, cut the timeline, add motion and sound, and review the render. This means the first pass at an edit is generated from a description of the film rather than from manual clip placement. The agents act on the project in more than one dimension: they organise content into chapters, perform the cuts that make up the timeline, generate motion elements, add sound, and then review the rendered output. The writing on the page frames this as "You direct. Agents edit." — direction is the human contribution, and the mechanical editing work is delegated. Chapters and story structure are kept explicit in the product. The landing experience itself is built as a chaptered film, listing segments such as Cold open, The problem, Meet OpenVids, Feature tour, In the field and Outro, each with its own timecode. The same idea appears in the navigation as a Story Graph area, which sits alongside Media and Edit rather than being hidden inside them. Because the story is represented as named chapters with timecodes, it stays legible even as the number of clips grows — which is precisely the thing the site says a conventional timeline makes difficult. Crucially, agent output is not a black box you are locked out of. OpenVids states that "every change lands on a timeline you can take over." So the agents' edits are recorded as real timeline changes that a human editor can subsequently pick up and modify directly. This is what separates an agent-first editor from a one-shot generative tool: the result of the agents' work is an editable project, and the site's feature tour describes showing the workspaces as one continuous workflow, implying that moving between agent-generated structure and hands-on editing is not a separate mode but part of the same flow. Motion and sound are handled as distinct concerns with their own place in the interface. The navigation lists Motion and Sound as separate areas, and the agent summary explicitly includes adding motion and sound to the timeline. The landing page illustrates this with media entries such as Title_Reveal.motion, a motion asset shown with its own duration, indicating that motion elements are tracked as items in the project just as footage is. Treating motion and sound as first-class, agent-addressable parts of the project is what allows a description of the film to result in something that is not merely cut but finished — with titles, movement and an audio layer rather than picture alone. Review and rendering close the loop. The site says the agents review the render, and Render is listed as its own area in the interface alongside Edit and Sound. The page also lists Licenses as a top-level area, and the demo project is annotated with a version marker (V1), a frame rate (24 FPS), a resolution (3840 × 2160) and the descriptors RESEARCH, OPEN MOVIES and CC BY. The landing page's imagery is drawn from open movies including Sintel, Big Buck Bunny and Tears of Steel from the Blender Foundation, shown under CC BY. Media management is visible too: a Media panel in the demo reports a count of 23 assets, with 1 missing. Overall, OpenVids works by inverting the usual relationship between description and timeline. Rather than beginning with an empty timeline and building a story clip by clip, you start with a description of the film; agents translate that description into chapters, cuts, motion and sound; the result is reviewed and rendered; and every one of those changes is written onto a timeline that remains yours to take over. The unique approach, as the site frames it, is being agent-first: agents are the primary operators of the edit, and the human's role is direction — deciding what the film is, with the option to step in and edit the timeline directly at any point. The stated benefit follows from that approach. If the story stays visible the whole way through, you are less likely to lose the thread as the project grows — the failure mode the site describes around clip two hundred. Because agent edits land on a takeable-over timeline, you get the speed of delegating assembly without giving up control of the final cut: you can direct, let the agents build and revise, and then take over the parts you care about. And because the product is free and open source, the editor itself, not just its output, is something users can download, inspect and build on. In practical terms, the workflow the site describes plays out as follows. You begin a project with a description of the film you want to make. Agents build the chapter structure — something like a cold open, the problem, an introduction, a feature tour, a field section and an outro — and cut the timeline accordingly. Motion elements such as a title reveal are added, and sound is layered in. The render is produced and reviewed, and the whole thing arrives on a timeline you can take over, with the project's media assets tracked in one place. From there you can keep directing further revisions, or edit the timeline directly. OpenVids is built for macOS and Windows. The site offers a direct download for macOS on Apple Silicon (the .dmg build labelled v0.5.4) and a Windows build (the x64 setup executable, also labelled v0.5.4), plus a link to view the source on GitHub. The product is described as free and open source, and no paid tier is described on the page — the emphasis is on the download and the repository rather than on plans or subscriptions. The interface organises the work into named areas including Agents, Media, Story Graph, Edit, Motion, Sound, Render and Licenses. You direct; the agents edit. That single line captures what OpenVids is: an agent-first, open-source video editor that turns a description of a film into chapters, cuts, motion, sound and a reviewed render — all landing on a timeline that stays under your control, so the story remains visible from the first clip to the last.