Self-hosted service
0xsline/OpenChatCut avatar
0xsline/OpenChatCut

OpenChatCut: An Agent-Native Video Editor That Keeps Projects Editable

Open-source, local-first conversational AI video editor with a professional multi-track timeline, Agent Skills, MCP integration, and Remotion rendering.

1,824 stars271 forksTypeScriptAGPL-3.0

At a glance

What is it?
OpenChatCut is an open-source, local-first video editor that lets AI agents like Codex and Claude Code edit real timelines. It targets creators who want AI assistance without losing manual control.
Who is it for?
Adopt OpenChatCut if you are a developer or creator who wants AI agents to edit video projects with full manual control, undo, and versioning, and if you accept the AGPL-3.0 license. Do not use it if you need a cloud-based, zero-setup tool or if you require proprietary licensing.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 5 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.

DEEP OPEN-SOURCE ANALYSIS

What Problem Does OpenChatCut Solve?

OpenChatCut targets a gap between traditional video editors and one-shot AI generators. Traditional editors give you precise track-level control but no natural language interface. One-shot generators produce a video quickly but the result is immutable; you cannot easily edit it afterward. OpenChatCut claims to combine both: you can describe a goal in natural language, and an agent reads the project, makes verifiable edits, and writes them to a real timeline. The README emphasizes that every edit lands on actual tracks, clips, transitions, captions, and effects, so you can continue editing manually, undo or redo changes, save versions, or hand the project to another agent. This is for creators and developers who want AI to participate in the editing workflow without giving up professional control. The project is explicitly an open-source ChatCut alternative, independent and not affiliated with the commercial product.

The Core Mechanism: Agents, MCP, and a Real Timeline

The architecture is built around a shared set of editing tools. The built-in agent and external MCP agents use the same tools, which means Codex or Claude Code can directly manipulate the timeline. The README describes the core editing loop: describe the goal, the agent reads the project, produces verifiable edits, writes to the timeline, then you preview, adjust, undo, and export. The key distinction is that the agent does not generate a final video; it edits a project file. This is possible because the project stores real tracks, clips, transitions, effects, and media. The README mentions Remotion rendering, which suggests the export pipeline uses a React-based video generation library, but the documentation does not detail how Remotion integrates with the timeline. The MCP integration is a central feature, allowing external agents to control the editor, which is a different approach from most video editors that only offer a GUI.

Getting Started: Commands and Configuration

The README provides a Quick Start section, but the cleaned version does not include the actual commands. Based on the repository being a TypeScript Electron desktop app, you would likely clone the repository and run npm install and npm start, but this is not confirmed from the material. The README does mention that API keys remain server-side, which implies you need to configure API keys for the built-in agent. The project is local-first, so projects and media stay on your machine by default. For using OpenChatCut with Codex or Claude Code, you need to set up the MCP integration, but the README does not give the exact configuration steps. The release tags (v0.2.11) suggest a pre-1.0 stage, so expect setup friction. You should check the official website or the full README for precise installation instructions.

Transcript-Driven Editing and Visual Geometry

A standout feature is transcript-driven editing. The README claims word-level transcription, text-based cuts, pause handling, speakers, and linked captions. This means you can edit by selecting text in the transcript, and the corresponding video clips are cut or adjusted. This is a powerful workflow for interviews, podcasts, or any content with dialogue. Another notable feature is visual geometry: in-browser person segmentation and face-safe zones. The README states that captions automatically avoid the speaker, reframing follows the subject, and overlay graphics land in empty space. This is a sophisticated feature that typically requires machine learning models running locally. The documentation does not specify the models or performance costs, but it is a clear differentiator from basic editors. However, these features are likely to be compute-intensive, and the README does not mention hardware requirements.

Production Exports and Project Portability

OpenChatCut supports production-ready exports including MP4, audio, captions, FCPXML, and complete project data. The FCPXML export is significant because it allows you to move a project to Final Cut Pro for further editing, which is a practical bridge for professional workflows. The project data export means you can save and reload entire projects, which is essential for versioning and collaboration. The README emphasizes that projects remain fully editable, which is a key advantage over one-shot generators. However, the export pipeline relies on Remotion, which may have limitations on codecs, resolutions, or complex effects. The README does not specify export presets or performance benchmarks. For users who need specific formats or high-resolution exports, you should verify that the export meets your requirements before committing.

Limitations and When It Is the Wrong Tool

OpenChatCut is not a simple consumer tool. It requires setup, configuration, and a willingness to work with agents and MCP. If you are a casual user who wants a quick video with no technical overhead, this is not for you. The project is under active development with frequent releases (v0.2.9, v0.2.10, v0.2.11 within a week), which means features may change and bugs may exist. The README does not mention any limitations, but the complexity of the features suggests a steep learning curve. The AGPL-3.0 license is a significant constraint: if you modify and distribute the software, you must share your source code. This may be unacceptable for commercial products. Also, the local-first approach means you need a capable machine to run the editor, especially for visual geometry and WebGL effects. There is no mention of cloud rendering or collaboration features, so remote teamwork is not supported out of the box.

Alternatives: ChatCut and Traditional Editors

The most direct alternative is the commercial ChatCut product, which OpenChatCut explicitly positions against. ChatCut is likely a one-shot AI video generator that produces an immutable result, while OpenChatCut offers an editable timeline. The README includes a comparison table, but the actual differences are clear: ChatCut may be cloud-based and closed-source, while OpenChatCut is local-first and AGPL. Another alternative is a traditional editor like Adobe Premiere or DaVinci Resolve, which offer precise control but no native AI agent integration. You could use those editors with external AI tools, but the integration would not be as deep. OpenChatCut's MCP integration is unique because it allows agents to directly manipulate the timeline, which is not possible in traditional editors. For developers, this is a key differentiator, but for non-technical users, a traditional editor might be more accessible.

Maintenance, Upgrade Cost, and License Implications

The project has a changelog and a contributing guide, indicating an active maintenance process. The release cadence is high, with three releases in a week, which means you need to keep up with updates to get bug fixes and new features. Upgrading may introduce breaking changes, especially at this early stage (v0.2.x). The README does not specify a migration path for projects across versions, so you should back up your project files before upgrading. The AGPL-3.0 license has strong copyleft implications. If you use OpenChatCut as a library or modify it for internal use, you do not need to share source code, but if you distribute a modified version, you must offer the source to users. This is different from permissive licenses like MIT. For commercial use, you should consult a legal expert, but the license is clear: it is not permissive. The project is sponsored via Ko-fi and Afdian, which suggests community-driven development, but there is no guarantee of long-term support. You should evaluate your tolerance for a pre-1.0 dependency.

Editorial conclusion

Adopt OpenChatCut if you are a developer or creator who wants AI agents to edit video projects with full manual control, undo, and versioning, and if you accept the AGPL-3.0 license. Do not use it if you need a cloud-based, zero-setup tool or if you require proprietary licensing. Before adopting, verify the MCP integration works with your preferred agent (Codex, Claude Code), test the Remotion export pipeline with your target resolution and codecs, and confirm the transcript-driven features handle your language and audio quality. The project is under active development (v0.2.11 as of August 2026), so check the changelog for recent fixes and breaking changes. OpenChatCut is a serious alternative to one-shot AI generators, but its complexity demands a technical user.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Community notes

Community notes