FableCut
The open-source video editor AI agents can drive
Start new thread

FableCut - The open-source video editor AI agents can drive

byβ€’
FableCut is an open-source, Premiere-style video editor that runs in your browser β€” no install, no build step, zero dependencies. AI agents like Claude edit by patching a simple JSON timeline over MCP, and the UI live-reloads in ~150 ms. You stay the director.

Add a comment

Replies

Best
Maker
πŸ“Œ
Hey Product Hunt πŸ‘‹ I'm Ronak, and I built FableCut because AI agents can write code, but they couldn't edit video β€” every editor locks its timeline inside a binary project file. FableCut flips that: the entire timeline is one readable project.json. An agent (Claude Code, or anything that speaks MCP/REST) edits by patching that file, and the browser UI live-reloads in ~150 ms β€” so you watch your edit assemble itself, then grab the mouse and tweak anything by hand. Keyframes, transitions, text animations, chroma key, AI background removal, speed ramps, beat-synced cuts. It can even analyze a reference reel into a beat-by-beat blueprint and rebuild it with your footage. It's fully open source, runs on node server.js with zero npm dependencies, and hit the front page of Hacker News last week (98 points) β€” the feedback there already shaped this release, including community PRs merged this weekend. I'll be here all day β€” ask me anything, and tell me what would make you actually use this.

The 150ms live reload after edits actually feels right, not laggy or jumpy like other browser editors I have poked at. The JSON timeline being open and inspectable is a really nice touch.

Maker

Β thanks!!

readable JSON timeline instead of a binary blob is the right call, that alone makes it way more hackable than Premiere/Resolve project files. question: what happens if I'm manually tweaking the timeline in the browser at the same moment the agent patches the JSON file - is there any conflict resolution, or does last write win and I could lose an edit mid-session?

Maker

Β No conflicts at all , shows that the changes are overwritten(can be undone), and synced with the agent implementation as you go..

Β good to know it fails safe toward the undo-able side rather than silently dropping edits. that's the right default for something running live during an editing session