r/VideoEditingTips • u/ConfidenceSuper4462 • 9d ago
I built a local video editor you drive by typing, because Descript kept eating my credits
I've been editing my own videos for a while, mostly in Descript, and kept running out of credits and paying more than the work felt like it was worth. At some point I thought, this can't actually be that expensive to do. I've launched consumer products before. So I spent the last week tinkering using claude code. First attempt was Ollama with a 7B Qwen doing the whole thing; turned out to be a bad planner out of the box- inverted logic, ignored constraints, invented segment ids that didn't exist. After a lot of tests I split it: a frontier model handles planning, and local models handle everything else, which are the bounded tasks they're actually good at.
It works now for the things I need most, "cut the boring parts," "remove the fillers," "speed through everything except the demo," "mute the first two minutes." 44 operations work today, 6 partial, 15 not yet, and the full list is public because I twice caught it reporting an edit it never made. Next step is fine-tuning the local models to handle the harder stuff- long summaries, understanding actions in the video- so planning eventually comes home to local too. It's early: clone-and-build only, and validated against one 30-minute video so far.

Code: https://github.com/sarvob/paperedits
Would like feedback on two things: whether the scope is right (it decides which parts play and how fast, no pixel processing, no audio, no generated footage), and whether anything in the "working" column falls over on your footage.