Tracking: OpenCut rewrite

What's coming:

• Editor API: a clean, stable API anyone can build on top of
• Plugin system: third-party plugins
• Desktop, mobile, and browser: OpenCut runs anywhere
• MCP server: for AI agents
• Headless mode: automation, batch rendering, CI pipelines
• Scripting tab: write and run scripts directly inside the editor

One thing needs to change for all of the above to work: separating the engine from the UI:

flowchart TD
    Web --> Core
    Desktop --> Core
    Android --> Core
    iOS --> Core
    Core["Rust core (engine)"]

Everything else uses the same engine:

flowchart TD
    MCP --> Core
    Headless --> Core
    Scripting --> Core
    Core["Rust core (engine)"]

In addition to the new architecture:

• The renderer will be more stable (and faster)
• Auto captions are getting some fixes
• You'll finally be able to group elements
• Transitions and filters are coming
• We're expanding the effects library significantly
• Keyboard-first mode (opt-in)
• The UI is getting a new look (!!)

---

Sneak peeks and early builds of the desktop/mobile app go to the Discord first.

---

FAQ:

Is OpenCut staying open source?

Yes. The source code for all platforms and the core engine will live inside this repo.

Why are you adding plugins? Will that not make it bloated?

The opposite. Plugins let us keep the editor light by default. You should be able to decide what's in your editor. Not us.

Will plugins also work in the mobile app?

Yes, plugins will work on all platforms including mobile.

What does the transition look like?

When the rewrite launches, it'll replace opencut.app. The old editor moves to old.opencut.app and you'll be able to carry your projects over there and continue editing in the old version.

Will I lose my projects?

No. I've been there. Never again.

Can I contribute?

We're still writing the architecture docs. Once those are out, you'll be able to contribute with a clear direction.

Is there a timeline on when it's coming out?

There isn't, but you will be able to watch us build it in the open.

---

Progress

• Document the architecture
• Engine Core (data model, state, rendering, etc)
• Editor API design
• Plugin API design
• Plugin host (sandboxing, lifecycle, event routing, etc)
• Project storage
• Web UI
• Built-in plugins
• Headless mode
• MCP server
• Scripting
• Desktop UI (GPUI)
• Android
• iOS
• Public beta

The issue names the planned Rust core, web, desktop, mobile, MCP, headless, and scripting components but provides no files, tests, or entry points. Start with the promised architecture documentation; the issue becomes actionable when it identifies component boundaries and a specific implementation task with a clear completion check.