VEED's OpenEdit lets AI coding agents edit video without a timeline

OpenEdit is an open-source video editing pipeline by VEED that turns AI coding agents into timeline-free video editors. Instead of dragging clips across a GUI, you can have Claude Code, Codex, or Gemini cut footage, generate subtitles, and build motion graphics directly from your prompt.

Everything is composed in standard HTML and CSS, which is then compiled into an MP4 locally by VEED's dedicated rendering engine without spinning up a headless browser.

What you can build

Captions are the most mature path in OpenEdit right now. Point your agent at a clip, and one to three minutes later you get a finished MP4 back with an interactive preview window. If the styling looks off, you simply tell your agent to nudge the text up or make the yellow darker. You can even hook in a Figma MCP server to pull styles straight from a brand kit.

Beyond basic captioning, it handles reframing, cutting, and layering motion graphics. You can hand it a slide deck or a web capture, and it will turn those assets into a polished motion video. Source footage is entirely optional: still images, slides, and pure CSS motion graphics are enough on their own.

An August 19 update also wired in VEED Fabric. That means your agent can now generate missing b-roll footage, still images, music, and multi-track audio through the VEED API on the fly rather than waiting for you to upload assets. Generating media costs API credits, and OpenEdit asks for permission before spending them.

VEED says its early internal benchmarks show the local engine running up to 2.2x faster than traditional agent video tools that rely on headless Chrome.

Requirements and licenses

The pipeline itself is open source under Apache-2.0 and available on GitHub. You install it with a single command: npx skills add veedstudio/open-edit, and it comes configured to load AGENTS.md across multiple models.

Licensing is split into two parts: the editing pipeline is fully open source, while the VEED Engine renderer binary is closed source under PolyForm Shield 1.0.0. The binary is free to use, and you can commercialize the videos you produce with it at no cost. If you object to closed binaries, the pipeline lets you swap back to rendering through Chrome.

Transcription runs through a free veed.io account. Only your audio track is uploaded for speech recognition, while your video footage stays local.

The current limitation is hardware. Right now, OpenEdit requires an Apple Silicon Mac running macOS 26 (Tahoe). It will not run on Intel Macs or older versions of macOS. VEED says Windows support is coming shortly, with Linux prioritized based on user demand.

Why it matters

If you produce high-volume social clips, podcast cuts, or developer demos, OpenEdit is definitely worth testing. Treating video composition like web development lets developers automate editing workflows, spin up parallel agents for batch production, and avoid recurring SaaS subscription fees for simple timeline tasks.

Ditching headless Chrome in favor of a specialized local HTML-to-video renderer was a very smart architectural move. Cutting and motion graphics are still noticeably rougher than its captioning tools, and the narrow macOS Tahoe requirement leaves a lot of creators out for now. But for developers already living inside terminal agents, this is a much cleaner way to ship video.