OpenCut
The open-source CapCut alternative
Runssource: GitHubhomepageTypeScriptMITcommit 400f097becba
TypeScript, MIT licensed. The project labels itself: editor, oss and videoeditor.
OpenCut runs. An Argusic agent installed it in 22 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenCut desktop builds and runs with lavapipe software Vulkan, web app builds and dev server returns 200, API serves /health and /echo endpoints correctly.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 94.7 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- desktop binary panicked: NoSupportedDeviceFound (no Vulkan driver)2 minutes
- cargo link failed: missing -lxcb, -lxkbcommon, -lxkbcommon-x11 (no .so symlinks for the linker)1 minute
- web build failed: Node v18 lacks node:util.styleText export required by rolldown/vite 81 minute
- wrangler dev port 8787 Address already in use from previous run1 minute
- Install time
- 22 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl http://localhost:5173/ returned 200; curl http://localhost:8788/ returned {"status":"ok"}; desktop binary ran for 10s timeout with lavapipe Vulkan on Xvfb
- Model tokens used
- 193,262
- Exact commit tested
- 400f097becba
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used
193,262
Here's the final summary of everything I did, and the required JSON result line.
**What was tested:**
- **Desktop app** (`apps/desktop`): Rust (GPUI) — `cargo build` succeeds, binary runs on Xvfb + lav…
- **Web app** (`apps/web`): Vite + React + TanStack + Cloudflare — `bun install` succeeds, `vite bu…
- **API** (`apps/api`): Elysia on Cloudflare Workers — `wrangler dev` serves `/` (200, `{"status":"…
**Errors encountered & fixed:**
1. **Node 18 lacking `node:util.styleText`** — web build failed. Fixed by installing Node 22.14.0 f…
2. **Missing `.so` symlinks for xcb/xkbcommon** — desktop linker failed. Fixed by creating symlinks…
3. **No Vulkan GPU driver** — desktop panicked `NoSupportedDeviceFound`. Fixed by extracting `mesa-…
4. **Port 8787 already in use** — API dev failed. Fixed by using port 8788.Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 22 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/opencut)Questions
- Does OpenCut run?
- Yes. OpenCut runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test OpenCut?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 400f097becba. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test OpenCut?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenCut take to install?
- 22 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does OpenCut need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenCut?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for OpenCut?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.