Who it is forA video maker who got a first cut from an agent and wants precise manual control over layout, text and timing.
The problemAsking an agent for every small change is slow, and the agent's first draft often needs fixes in exact positions and timing.
The outcomeA revised film with your manual edits saved to the film's files, with named versions you can return to.
What you need first
- Node 22.2 or later and ffmpeg on macOS, Windows or Linux, or the OpenFilm desktop app for macOS or Windows, which includes ffmpeg and the headless browser
- A coding agent such as Codex or Claude Code, or any coding agent
- Git, for Studio's saved versions
- About 100 MB of disk space for the headless Chromium download on the first run
- Your own API keys in Studio's Settings → Providers, only if you want generated voice, music, images or video
Steps
- Open the film with
openfilm open <folder>. (inferred, check the README) - Select a page element in Studio and move, scale or rotate it, or change its text, color or style.
- Trim, cut or restyle clips on the timeline, and adjust their volume and speed.
- Save a named version from Studio so you can go back to it.
- Render the result with
openfilm render.
Prompt for your agent
In the openfilm/openfilm repo, run `openfilm open <folder>` to show an existing film in Studio. Make the edits listed in <edit list> by hand in Studio, then save a named version. Expect the film's files to reflect your edits, so the agent can keep them. Verify by reopening the film and confirming the changes are still present.
Caveat. The README says Studio works best on a Chromium-based browser such as Chrome or Edge, so the preview you see there is the one that gets exported.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page