Build an open-source DaVinci Resolve style video editor for Linux in C++

A Redditor had Claude write all the code of Kinoklip, a GPL C++ editor modeled on DaVinci Resolve with h264, h265 and AAC on Linux, and covered their own editing workflow in four days.

Done withClaudeinGitHub· Nov 8, 2026

What they did

u/SeniorMatthew, a C# game programmer, was fed up with DaVinci Resolve on Linux: a hard install, no h264, h265 or AAC in the free version, and poor speed on anything but NVIDIA. On a Claude Max plan they had Claude write Kinoklip, an open-source C++ video editor that copies Resolve's layout on purpose. Claude wrote every line of code; the poster only drew the icons. All seven of Resolve's pages were built, and every change has to pass a suite of more than 140 test programs before it lands. The project is GPL-3.0 and adds a single-file project mode, where dropped media is copied into the project file so it can be backed up or sent as one file.

How it went

After four days of work the poster says their own editing workflow is fully covered and the app runs at least ten times faster than Resolve on their ThinkPad with Iris Xe graphics. Only the edit page is confirmed complete. They had to find about 30 small problems in the edit tab by hand, and work paused while they waited for the weekly usage limit to reset.

Worth knowing

The post names the Claude Max plan and a high effort setting but not the harness. The speed claim is the poster's own and was not measured in the thread. Commenters asked whether it will be maintained and pointed out that Resolve's free version is strong on Windows and Mac; the poster agreed and said the project mainly helps Linux users.

Try it

With Claude· 6 parts to fill in

Build [app name], an open-source [language] replacement for [existing app] on [platform], matching its layout so its users feel at home. Do not copy the original's code, artwork or text. Start with the [most used screen, e.g. edit page] and make it fully work with [formats or codecs I need] before touching other screens. Keep a growing set of test programs and run all of them after every change; a change that breaks one is not done. Keep the code readable for human contributors. After each screen, stop and give me a list of what to test by hand.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related