lux
👾 Fast and simple video download library and CLI tool written in Go
Runssource: GitHubGoMITcommit dd00f6d258d8
Go, MIT licensed. The project labels itself: bilibili, crawler, download, downloader, go, golang, iqiyi and qq.
lux runs. An Argusic agent installed it in 4.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Lux builds and runs: the binary outputs version info and help, extracts real YouTube video metadata, and 14 of 48 test packages pass (all failures are network-dependent extractor tests or DNS-timeout content-type lookups; no code defects remain).
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 90 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.
- Go not installed in container — downloaded go1.27.1 tarball manually3 minutes
- app/app.go:34: non-constant format string in call to color.Sprintf — vet/build failure1.5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- /tmp/lux --version printed version v0.0.0; /tmp/lux -i https://www.youtube.com/watch?v=dQw4w9WgXcQ successfully extracted YouTube streams (2160p/1440p/1080p etc.); go build exits 0; go vet exits 0; 14 test packages pass (douyu, hupu, huya, mgtv, netease, pornhub, rumble, twitter, vimeo, xvideos, yinyuetai, youku, parser, request).
- Model tokens used
- 165,331
- Exact commit tested
- dd00f6d258d8
- 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.
# download with: lux -f 271 ... The build works and YouTube extraction works too. Let me do one final comprehensive check: exec /bin/sh -lc 'export PATH="/tmp/go/bin:$HOME/go/bin:$PATH" && cd /work/repo && go build -o /tmp/lux … succeeded in 1392ms: BUILD OK lux: version v0.0.0, A fast and simple video downloader. VET OK Now I have a complete picture. Let me compile the final result. tokens used 165,331 Now I have a complete picture. Let me compile the final result.
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 4.5 minutes.
- Recovered from all 2 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 2 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.
- A quick evaluation: it was running 4.5 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.04 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.05 |
Topics (from GitHub)
bilibilicrawlerdownloaddownloadergogolangiqiyiqqscrapertumblrvideoyoukuyoutube
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lux)Questions
- Does lux run?
- Yes. lux runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test lux?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dd00f6d258d8. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test lux?
- 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 lux take to install?
- 4.5 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 lux need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lux?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for lux?
- 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.