Cliparr
Create clips from media on your personal media server
Runssource: GitHubhomepageTypeScriptMITcommit 9cc203d86353
TypeScript, MIT licensed. The project labels itself: jellyfin, media server, plex, radarr, self hosted, sonarr and video editing.
Cliparr runs. An Argusic agent installed it in 6 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The project installs, builds, passes its workspace and browser tests, and its production server answered 200 on /api/health and / with a working SQLite database.
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 100 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.
- Node v18.19.1 is installed but the project requires Node >=24.16.01 minute
- npm install -g n failed with EACCES mkdir /usr/local/lib/node_modules/n1 minute
- pnpm not found on PATH1 minute
- No .env file present, so APP_KEY was unset1 minute
- No Playwright browser installed1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pnpm build exited 0; pnpm test and workspace tests passed (www 49, server 396, frontend 336, shared 23, plex 7, assets 6, 0 failures); curl localhost:7171/api/health returned 200 {"status":"ok","database":"ok"}; curl localhost:7171/ returned 200; pnpm test:browser passed 13 browser export checks; pnpm test:browser:loading exited 0 with 48 PASS lines
- Model tokens used
- 67,166
- Exact commit tested
- 9cc203d86353
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
67,166
I installed the repository, built it, ran its tests, and launched it. It works in this container. I…
**Environment fixes**
- Node v18.19.1 was installed, but the project requires Node 24.16 or newer. Global npm installs fa…
- There was no pnpm, no Playwright browser, and no `.env` file. I ran `playwright install chromium`…
**Observed results**
- `pnpm install` exited 0 and added 932 packages. `pnpm build` exited 0, including `apps/server/dis…
- `pnpm test` and the full workspace tests passed: www 49, server 396, frontend 336, shared 23, ple…
- Production server: `curl localhost:7171/api/health` returned 200 with `{"status":"ok","database":…
- `pnpm dev`: Vite answered 200 on `localhost:5173` and the API answered 200 on `localhost:3000/api…
- Real browser checks passed: `pnpm test:browser` passed all 13 export checks, including decoding e…
- No Plex, Jellyfin, or other third-party credentials were needed for anything verified. Provider c…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.
- Recovered from all 5 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.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 jellyfin projects Argusic has installed and timed, Cliparr was the 6th fastest to reach a running state, and 5 of 8 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6 minutes after the clone.
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
Topics (from GitHub)
jellyfinmedia-serverplexradarrself-hostedsonarrvideo-editing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cliparr)Questions
- Does Cliparr run?
- Yes. Cliparr runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test Cliparr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9cc203d86353. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Cliparr?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Cliparr take to install?
- 6 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 Cliparr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Cliparr?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Cliparr compare with the alternatives?
- Of the 8 jellyfin projects Argusic has installed and timed, Cliparr was the 6th fastest to reach a running state, and 5 of 8 reached one at all.
- Where is the evidence for Cliparr?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.