A precise, simple timeline.
Scrub to a frame, select clips or mark a region, then describe the change. Review and refine it. Undo, redo and saved editing history keep your work recoverable.
OPENEDIT 1.4 · AI-NATIVE VIDEO EDITING
Select the moment. Describe the edit. Your agent makes the creative decisions; OpenEdit handles the timeline, preview and export.
Local editing · Windows & Linux x64 · Six composable MCP tools
THREE JOBS. ONE FOCUSED WORKSPACE.
Preview, timeline, AI instructions, media and export. The essentials are close at hand.
Scrub to a frame, select clips or mark a region, then describe the change. Review and refine it. Undo, redo and saved editing history keep your work recoverable.
Retrieve timestamped frames, contact sheets and selected transcript ranges. Cached analysis and on-demand tool help reduce repeated inspection and unnecessary context.
Preview work starts around the playhead and reuses unchanged ranges. OpenEdit handles cuts, transitions, overlays, keyframed graphics and synchronized audio, then verifies the export.
More room for animation. Graphics supports 500 visual layers and 4,096 total nodes, including keyframes. Completed graphics are reused across matching previews and exports.
START WITH THE CURRENT EDITOR
The latest source is OpenEdit 1.4.0. Download and extract the source ZIP, open a terminal in its OpenEdit-main folder, then run your platform’s installer.
For packaged downloads, choose 1.4.0 or newer when available. Earlier 1.3 releases use the previous editor and setup. Current release ZIPs contain the same installers; Git is not required for either extracted ZIP.
Ubuntu 24.04 recommended
bash ./install.sh
~/OpenEdit/OpenEdit.sh
Debian/Ubuntu setup requests administrator access for Python venv and browser/media libraries. Other distributions need equivalent prerequisites.
Windows 10 / 11 · PowerShell
powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1
& "$env:USERPROFILE\OpenEdit\OpenEdit.cmd"
Setup can install Python through winget. Native Windows media tools are provisioned; WSL and a manual MLT build are unnecessary.
Required: Python 3.11.8+ (3.12 recommended) and Internet access for initial setup. The installer provisions pinned Node 24, FFmpeg/MLT, the graphics worker and Chromium, then tests an actual editing/export workflow.
Projects live separately under ~/OpenEditProjects. Back up the entire project, including .open_edit. macOS and ARM need source setup with their own native runtimes.
YOUR AGENT. YOUR DIRECTION.
The installer creates connection files for its starter project. Merge the OpenEdit entry into your agent host’s existing settings, then reload its MCP servers.
| Your host | Generated file | Entry to merge |
|---|---|---|
| OpenCode | opencode.json | mcp.openedit |
| Codex CLI | codex.toml | [mcp_servers.openedit] |
| Cursor / Claude Desktop / standard MCP host | mcp.json | mcpServers.openedit |
Find these files in ~/OpenEdit on Linux or %USERPROFILE%\OpenEdit on Windows. Generated commands use absolute paths and connect to one project. Existing agent settings are preserved.
“Use OpenEdit to inspect my selected moment. Make it more energetic, add an animated title, and show me a preview.”
Confirm six tools appear: query_project, edit_project, run_script, trigger_render, get_render_job and cancel_render_job. Your agent gets editing context and parameter help through these tools.
External agents use their own authentication; OpenEdit needs no provider key for MCP. Built-in chat is optional. To connect another project, generate a new configuration using the installation’s CLI.
REAL EDITS. RECORDED CHECKS.
The trailer was authored through real MCP tools, reviewed on the live graphics canvas and exported through OpenEdit’s UI at 1080p/60 fps. Its editable ZIP reopened with graphics, separate music/effects tracks and history intact.
The recorded regression run passed 1,797 tests; browser workflows ran separately. Native Windows/Linux package checks exercise imports, transitions, animation, synchronized audio, full decoding, UI export/download and reopening.