Complete Overhaul of OpenCut: Transitioning to AI Integration and Plugin Architecture

The open-source video editor “OpenCut” has officially announced a full-scale rebuild project from scratch. According to information released on GitHub Trending, the new version will be based on the current Classic edition and will include features such as a structured Editor API, a plugin-first architecture, cross-platform compatibility with a Rust core, support for AI agent-driven MCP servers, headless mode for automation and batch rendering, and an in-editor scripting tab. Although the development team is gearing up, they are not yet accepting external contributions, which will commence once the architecture design is finalized.

OpenCut is a free and open-source video editor that runs on web, desktop, and mobile platforms. The current stable version is available at opencut.app, while the new rewritten version is under development at new.opencut.app. The existing codebase has been archived in the opencut-app/opencut-classic repository, and the Classic version will remain in use for the time being. The rewritten version will feature a Rust-based core and a design philosophy aimed at decoupling the front-end from the back-end.

Background and Overview of the Rebuild

The primary goal of OpenCut’s rebuild is to overcome the limitations of its existing codebase. While the current Classic version offers a certain set of features, it struggles to accommodate modern requirements such as plugin extensions, automation, and integration with AI agents. The development team has decided to rewrite the project from scratch to ensure a scalable architecture for future expansions.

A key highlight of the rewritten version is the revamped Editor API. By exposing the editor’s internal functionalities through APIs, third parties will be able to add new features with ease. This API is designed with a plugin-first philosophy, encouraging not only official plugin support but also diverse community-driven extensions. Unlike conventional video editors, where plugins are often an afterthought, OpenCut integrates the plugin framework into its core architecture from the outset.

The use of a Rust core plays a significant role in realizing this plugin mechanism. Written in Rust, the engine promises high speed and memory safety, enabling consistent functionality across multiple platforms. While the user interface for web, desktop, and mobile platforms will be tailored to their respective characteristics, the core logic will be shared across a single codebase. This approach is expected to enhance both maintainability and development speed.

Plugin-First Architecture and Rust Core

One of the most noteworthy technical decisions in OpenCut’s rebuild is treating plugins as first-class entities. Many open-source video editors have relied on directly merging new features into the main codebase. In contrast, OpenCut aims to establish an expandable ecosystem by releasing its plugin API, allowing enhancements without contaminating the core.

The choice of Rust as the core language is driven by its ability to balance performance with cross-platform compatibility. Video editing is resource-intensive, demanding near-native execution speeds for both CPU and GPU resources. Rust offers zero-cost abstractions and memory safety, while its compatibility with WebAssembly makes it easy to compile for browser-based applications. This ensures high performance even for the web version.

The development process employs the proto toolchain. Executing proto use at the root of the repository automatically installs the toolset declared in the .prototools file. The web front-end can be launched on localhost:5173 using moon run web:dev, and the API server on localhost:8787 via moon run api:dev. The desktop app can be started following the instructions in the application directory’s README. The Moon monorepo tool oversees build and execution management.

AI Agent Integration and Automation

The OpenCut rebuild plan includes several intriguing elements for integration with AI agents. The introduction of an MCP server (Model Context Protocol server) is on the roadmap, enabling AI agents to control the editor’s functions externally. MCP, proposed by Anthropic, defines a standard interface for communication between AI agents and tools. By adopting MCP, OpenCut paves the way for AI agents to directly execute video editing tasks.

A headless mode is also under development, allowing command-line execution without a GUI. This feature is geared toward batch rendering and integration into CI/CD pipelines. For instance, it would be particularly effective in use cases like server-side automated generation of template videos.

In addition, an in-editor scripting tab will be introduced, enabling users to write and execute scripts in languages like JavaScript or Python directly within the editor. This functionality significantly expands the possibilities for nonlinear editing workflows.

Development Status and Relationship with the

Classic Version

The current version of OpenCut (Classic) remains accessible at opencut.app, while the rewritten version is hosted at new.opencut.app. Although the development team is not yet accepting external contributions, discussions on their Discord server and questions on GitHub Issues are welcome. Contributions are expected to be accepted once the architecture design is finalized.

OpenCut is supported by sponsors, including fal.ai, a platform that provides generative image, video, and audio models. This partnership is expected to foster synergy with creative tools like OpenCut. The project is licensed under the MIT license, which offers permissive terms for commercial use and redistribution.

The repository for the development version is publicly available on GitHub, allowing anyone to view the source code and track progress. However, as the project is still in its early stages, the completeness and stability of its features cannot be guaranteed. The team plans to gradually transition from the Classic version to the new version while leveraging existing assets.

Editorial Opinion

In the short term, the full-scale rebuild of OpenCut has the potential to introduce new competition in the open-source video editor market. Features such as MCP server compatibility and headless mode are likely to attract attention from developer communities focused on AI agents and automation pipelines. Since the Classic version remains available, the immediate impact on users will be limited, but it may take several months to years for the rewritten version to reach maturity.

From a long-term perspective, the plugin-first architecture could promote the formation of an ecosystem, broadening options for video editing environments that don’t rely on commercial software. The cross-platform compatibility enabled by the Rust core could lower the barriers between web-based and native applications, laying the groundwork for professional workflows that can operate entirely within a browser. However, the success of the project hinges on the effective design of the plugin API; a poorly designed API risks stifling ecosystem growth.

As the editorial team sees it, the key to OpenCut’s success will be the speed of development and the timing of involving the community in the project. These factors will ultimately determine the project’s long-term viability.

References

• “OpenCut-app /

  OpenCut", by **OpenCut-app** — GitHub Trending, 2026-07-14 (ARR)

• Source URL: https://github.com/OpenCut-app/OpenCut