ai-video-editor
Open-source, local-first video editor where creators and AI agents edit the same real timeline.
Could not verifysource: GitHubhomepageJavaScriptMITcommit 68980d142cce
JavaScript, MIT licensed. The project labels itself: agent skills, ai music, ai video editor, ai voiceover, automatic captions, browser ai, joyvasa and liveportrait.
Argusic could not get ai-video-editor running. An Argusic agent installed it in 19 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install, TypeScript typecheck, and Vite build all pass; the dev server starts and serves the application at localhost:5173; the headless timeline CLI command engine parses commands and returns structured JSON errors.
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 80 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.
- ESLint 10.7.0 crashes on Node 18: TypeError: util.styleText is not a function3 minutes
- Install time
- 19 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- Model tokens used
- 69,093
- Exact commit tested
- 68980d142cce
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
VERSION_ID="24.04" exec /bin/sh -lc 'cd /work/repo && echo "=== Install succeeded ===" && npm ls --depth=0 2>/dev/null | ta… succeeded in 420ms: ├── [email protected] ├── [email protected] ├── [email protected] └── [email protected] Everything is working. Let me compute the elapsed time and produce the final JSON 2026-09-05T21:05:09.094688Z ERROR codex_core::session: failed to record rollout items: thread 01a07… tokens used 69,093
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
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 19 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
Of the 9 agent-skills projects Argusic has installed and timed, ai-video-editor was the 7th fastest to reach a running state, and 8 of 9 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.04 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.01 | |
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.04 |
Topics (from GitHub)
agent-skillsai-musicai-video-editorai-voiceoverautomatic-captionsbrowser-aijoyvasaliveportraitmodelscopeonnxpwareacttalking-avatartext-to-speechvideo-editorvideo-processingvideo-restorationwebassemblywebcodecswebgpu
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ai-video-editor)Questions
- Does ai-video-editor run?
- Argusic could not verify that ai-video-editor runs. Argusic installed and launched it on a clean machine in 19 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test ai-video-editor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 68980d142cce. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ai-video-editor?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ai-video-editor take to install?
- 19 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 ai-video-editor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ai-video-editor?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ai-video-editor compare with the alternatives?
- Of the 9 agent-skills projects Argusic has installed and timed, ai-video-editor was the 7th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for ai-video-editor?
- 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.