OpenMontage Video Studio

Starting from a video you already like

Instead of writing a prompt from nothing, you can hand the assistant a video you already like, a YouTube short, a Reel, a TikTok, or a file on your own computer, and ask for something similar on a different topic.

Here's a YouTube short I love. Make me something like this, but about
CRISPR for high school students.

The assistant reads the reference video's pacing, hook, and structure, then tells you what it will keep, what it will change, what it will cost, and gives you a sample before running the full production.

More prompts to try

Free real footage path

Create a 60-second Adam Curtis style archival collage about 1950s consumer
optimism. Prefer Archive.org and Wikimedia footage.

With one image provider configured, roughly 15 cents to 1.50 dollars

Create a 30-second Ghibli style animated video of a floating library in the
clouds at golden hour

Full setup with video generation, roughly 1 to 3 dollars

Create a cinematic 30-second trailer for a sci-fi concept: humanity receives
a warning from 1000 years in the future

How the system works, so you can steer it

The reason output quality is in your hands is that this is not one black box. Every video runs through the same stages a real production team would follow, in this order: research, script, scene plan, assets, edit, then final render. You can see each stage happen.

The important part for you is where it pauses. The system stops and asks for your approval on the creative stages, the idea, the script, and the scene plan, and then runs the technical stages, the asset generation, edit, and render, on its own. Those pause points are your steering wheel, and they come before anything expensive has been generated.

Under the hood it reads three kinds of plain files you can open and change yourself: the tool list of what it can do, the pipeline playbook that defines the stages and quality checks for each video type, and the skill files that hold the know how for using each tool well. Every choice it makes, which provider, which voice, which style, gets written to a decision log you can read after the fact.

Bottom line: you do not need to touch code to control the output. You control it by giving a sharp brief, approving or rewriting at the pause points, and setting a style once. The rest of this guide is how to do exactly that.

Getting the best output

1. Write the brief like a creative director, not a search query This is the single biggest lever. A one line brief gets you a one line result, which is to say generic. Name six things every time: the format and length, who it is for, the tone, the pacing, where the footage should come from, and the platform you are posting to. The more specific you are, the closer the first render lands to what you actually pictured.

Weak brief

`` Make a video about AI agents. ``

Strong brief

`` Make a 45 second explainer for founders on why AI agents fail in production. Confident, plain spoken tone. Fast cuts. Real stock footage, no cartoon look. Word by word captions, vertical for Reels. Match the pacing of this video: [link]. ``

1. Start from a reference whenever you can The reference workflow is the fastest route to a format that already works. Paste a short, Reel, or TikTok you like, or a file of your own, and ask for the same treatment on your topic. The agent studies the pacing, the hook, and the structure, then hands you two or three directions with cost estimates before it spends anything. The strongest move is to feed it your own best performing video, so the output inherits a format your audience has already told you it responds to.
2. Steer at the checkpoints. Do not rubber stamp the script It stops for your approval on the idea, the script, and the scene plan. This is where you rewrite a flat hook, tighten the pacing, or cut a weak line. Fixing the script here costs nothing, because no footage or voice has been generated yet. Fixing it after the render means paying to produce everything twice. Treat the script approval as the most valuable thirty seconds of the whole job.
3. Encode your taste in a style playbook This is what separates your videos from the wave of identical output that everyone cloning this repo is about to publish. A style playbook is a short file that locks your typography, your colors, your motion feel, and your audio profile, so every video comes out looking like yours instead of the default. It ships with a few ready made looks, such as Clean Professional, Flat Motion Graphics, and Minimalist Diagram, and you can write your own once and reuse it forever. Set this up a single time with your brand and the generic look problem goes away for good.
4. Spend where it moves the needle, nowhere else The free path is genuinely strong for documentary and explainer formats. If you add one paid thing, add a single image key, FLUX through fal.ai, for a clear jump in visual quality at close to no cost. Save premium video generation, Veo and Kling, for cinematic pieces and ads where real motion matters. The system scores every provider for each scene and logs why it chose one, so you can always see where your money went.
5. Iterate on the weak scene, not the whole video If one shot is off or the narration is flat, regenerate that one piece instead of re running the entire production. The run is saved and resumable, so you fix the ten seconds that are wrong and keep the ninety that already work. This is where the real time and cost savings live once you are producing regularly.
6. Preview before you commit the final render The system opens a live preview you can scrub in your browser before the final export runs. Catch pacing and caption timing there, where changes are free. You can also share that preview link so a partner or an editor like Renzo can review and leave notes before you spend anything on the final file.
7. Read the decision log when something looks off Every provider, style, voice, and music choice is written down with the reasoning behind it. When a video comes out wrong, the log tells you which provider or which style caused it, so your next run is a targeted fix rather than a guess. Over a few videos this is how you learn which settings consistently give you your look.

Provider cheat sheet

One key shortcut: a single fal.ai key gives you FLUX images plus Veo, Kling, and MiniMax video, so you can cover most premium generation with one signup instead of five.

Pick the right pipeline for the job

Forcing the wrong pipeline is the most common reason output disappoints. Match your goal to the right one, or just tell the agent your goal in plain words and let it recommend.

Name your target platform in the brief, YouTube, Shorts, Reels, TikTok, LinkedIn, or 21:9 cinematic, and it exports at the right size the first time instead of making you reformat afterward.

Honest limits

This is a developer tool, not a hosted app. You are running it on your own machine from a terminal. If you have never used one, expect a learning curve on day one.

The free path uses offline narration. It sounds fine but not as polished as premium voice providers. If voice quality matters most to you, budget for a narration key.

Quality still depends on your brief. A vague prompt produces a vague video. The more specific you are about tone, pacing, and what footage to use, the better the output matches what you actually wanted.

It is released under the AGPL 3.0 license. Free to use and modify, but if you distribute a modified version you are required to release your changes under the same license. Worth knowing if you plan to build a product on top of it.

Local LLM support is not available yet. You currently need a cloud based AI coding assistant to drive it. Support for fully local models is listed as planned but not shipped.

If something goes wrong

npm install fails on Windows with an argument type error. Run npx --yes npm install instead.

The assistant seems unsure how to use the project. Point it directly at AGENT_GUIDE.md in the project folder and ask it to read that file before continuing. This file is the instruction set the whole system is built around.

You added API keys but the assistant is still using the free path. Check that the keys are saved inside the .env file, not just set in your terminal session, and confirm there are no extra spaces around the equals sign.

A render looks like a slideshow of still images instead of real motion. The system has a built in check for exactly this and is meant to block it before you see the final file. If it still happens, ask the assistant to confirm which render engine was used and whether a video generation provider was actually available for that request.

The output looks generic or off brand. Set up a style playbook, or point the agent at one of the built in looks, before you generate. A good playbook is the difference between your look and the default look, and it is the fix for almost every complaint about output feeling flat.

What this changes

Making a video used to mean a script, a separate tool for voice, a separate tool for footage, and a separate tool for editing, with your own time spent gluing all of it together in between.

This collapses that into one conversation. You describe what you want once, and the same assistant you already use for other work does the research, the writing, the sourcing, and the final edit. The free path costs nothing and the paid path costs cents to a few dollars, not the price of hiring anyone.

The people who figure this out first are going to publish more, test more ideas, and spend far less time per video than the people still doing it the old way.