OpenMotion: Recreate Videos With Your Own Agent, Keys, and Brand Kit
You've probably seen a video ad or social clip and thought, "I could adapt that for my product." Then you looked at the timeline, the keyframes, the transitions, and quietly closed the tab. OpenMotion is an attempt to make that adaptation process less painful—it's an open-source, full-stack video studio that lets you feed in a reference video and rebuild it with your own branding, using your own agent and your own API keys.
What It Does
OpenMotion bills itself as an open-source alternative to Claude Motion and CapCut. The core idea: you upload a reference video or paste a social video link, and an agent breaks down the reference—its shots, timing, and transitions—then rebuilds it with your brand kit and copy. It generates any missing assets along the way, and you edit the timing in a built-in Studio before rendering an MP4 from the same project.
The project is built around a concept called Motion.md, a Markdown format for describing shot order, timing, and transitions. It's meant to be shareable—you can hand someone a Motion.md file and they can see exactly how a brand film works, shot by shot. Under the hood, the README describes it as "code video with HTML," and it runs on Node.js 22.18 or later. It's licensed under Apache 2.0 and built by the OpenDesign team.
Why It's Cool
-
BYOA and BYOK are the whole point. OpenMotion is free and open source, and it doesn't lock you into a hosted service. You bring your own agent—Claude Code, Codex, and WorkBuddy are listed as supported—and your own API keys. That means you're not paying a markup on inference, and you're not handing your brand assets to a black box.
-
Motion.md is a smart abstraction. Most video tools store projects in proprietary binary formats. Describing a video as a Markdown document of shots and transitions is unusual, but it makes the structure inspectable, diffable, and shareable. If you've ever wanted to version-control a video project, this is a step in that direction.
-
The pipeline covers more than editing. The README lists image generation (GPT Image 2.6), shot generation (Seedance 2.5), music (Suno), and voiceover (Eleven v4). Rather than bolting these on as separate subscriptions, OpenMotion treats them as parts of one recreation workflow—generate what's missing, then assemble.
-
Edit and render from the same project. The Studio timeline and the MP4 render aren't separate exports from separate tools. You adjust timing visually, and the render comes from the same underlying project. That's a small detail, but it's the kind of thing that saves you from the classic "export, re-import, lose your edits" loop.
-
There's a real install path. The README points to a one-click install from the ChatGPT Marketplace, which lowers the barrier for people who don't want to clone a repo and wire up dependencies on day one.
How to Try It
The repository is at github.com/nexu-io/openmotion. Before you start, make sure you're on Node.js 22.18 or newer.
- Head to the repo and follow the Quick Start section in the README.
- If you want the fastest path, use the one-click install from the ChatGPT Marketplace mentioned in the README.
- Otherwise, clone the repository and install dependencies per the setup instructions.
- Connect your agent of choice—Claude Code, Codex, or WorkBuddy—and supply your own API keys for whichever models you plan to use.
- Upload a reference video or paste a social video link, then let the agent break it down and rebuild it with your brand kit.
- Open Studio to adjust timing, then render your MP4.
The README also links to the project's website, a Discord server, and a Feishu group if you run into trouble or want to see what others are building.
Final Thoughts
OpenMotion isn't trying to be a full replacement for a professional NLE—it's aimed at a specific job: taking a video that works and making it yours, quickly and with your own tooling. If you're a developer or small team who needs branded video content without a subscription stack, and you're already comfortable running agents locally with your own keys, this fits neatly into that workflow. The Motion.md format is the most interesting bet here; whether it catches on as a shared way to describe video structure is an open question, but it's a thoughtful one. Worth a look if the BYOA model appeals to you.
Follow @githubprojects for more developer tools and open source projects.