yt-short-clipper

Windows desktop app that turns long-form YouTube videos into 9:16 short-form clips, AI highlight detection, face-tracking portrait reframe, and word-by-word captions.

Runs with mockssource: GitHubTypeScriptMITcommit f6d6d98f3bce

TypeScript, MIT licensed. The project labels itself: ai video, content creation, ffmpeg, instagram reels, llm, mediapipe, python and react.

yt-short-clipper runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

YT Short Clipper v2 frontend builds with npm, Rust backend compiles, Python sidecar binary responds to ping commands, and the Tauri desktop app launches on the Xvfb virtual display and stays running.

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 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.36 (measured)
recorded runs
2
last tested
stars
1,106
forks
312
open issues
2
watchers
19
size
4 MB
created
last push

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.

Time lost to each failure while testing yt-short-clipper, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Rust toolchain not installed12 minutes
  • System dev libraries (glib-2.0, webkit2gtk-4.1, gtk-3, soup-3.0, javascriptcoregtk, etc.) missing; no root access to apt install10 minutes
  • Rust compilation failed: resource path binaries/ytclip-sidecar-x86_64-unknown-linux-gnu missing5 minutes
  • @tailwindcss/oxide native binding missing for Linux x641 minute
  • pip install blocked by externally-managed-environment (PEP 668)1 minute
  • Rust linker failed: missing -ldbus-1, -lgobject-2.0, -lwebkit2gtk-4.1, etc.1 minute
Install time
25 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
9 hit, 9 fixed with no human help
How the result was proved
timeout 5 src-tauri/target/release/yt-short-clipper-v2 on DISPLAY=:99 ran 5 seconds then exited 124 (still running when killed); echo '{"command":"ping"}' | src-tauri/binaries/ytclip-sidecar-x86_64-unknown-linux-gnu returned {"ok":true,"result":{"pong":true}}; npm run build produced dist/index.html + assets; all 15 Python core modules import without error
Model tokens used
172,506
Exact commit tested
f6d6d98f3bce
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 succeeded in 0ms:
Started: Sun Oct 11 06:41:40 UTC 2026
Now: Sun Oct 11 07:06:57 UTC 2026
The elapsed time is approximately 25 minutes. Here is the structured result.
<pre><code>ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes":…
2026-10-11T07:07:09.555803Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
2026-10-11T07:07:09.556027Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
2026-10-11T07:07:09.556062Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
tokens used
172,506
The elapsed time is approximately 25 minutes. Here is the structured result.
<pre><code>ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes":…

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 9 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 25 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.

Of the 6 ai-video projects Argusic has installed and timed, yt-short-clipper was the 6th fastest to reach a running state, and 4 of 6 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.36
Argusic Runner1/3Did not run20.000.25

Topics (from GitHub)

ai-videocontent-creationffmpeginstagram-reelsllmmediapipepythonreactrustshort-form-videotauritauri-apptiktoktypescriptvideo-editingyoutube-shortsyt-dlp

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/yt-short-clipper.svg)](https://argusic.com/subject/yt-short-clipper)

Questions

Does yt-short-clipper run?
yt-short-clipper runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 9 errors on the way, and recorded the session.
How did Argusic test yt-short-clipper?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f6d6d98f3bce. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test yt-short-clipper?
The run that produced this verdict cost $0.36: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does yt-short-clipper take to install?
25 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 yt-short-clipper need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing yt-short-clipper?
9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does yt-short-clipper compare with the alternatives?
Of the 6 ai-video projects Argusic has installed and timed, yt-short-clipper was the 6th fastest to reach a running state, and 4 of 6 reached one at all.
Where is the evidence for yt-short-clipper?
All 2 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.

Discussion