ytermusic

An in terminal youtube music client with focus on privacy, simplicity and performance

Runssource: GitHubRustApache-2.0commit 0663348365eb

Rust, Apache-2.0 licensed. The project labels itself: music player, rust, terminal, tui, youtube and youtube player.

ytermusic runs. An Argusic agent installed it in 27 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

ytermusic builds with nightly rustc and the local pkg-config shims, its unit tests pass 2/3 against live music.youtube.com responses (the account-dependent library test needs a real Google account), and the TUI binary launches and renders on the virtual display with a headers.txt cookie configured.

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

At a glance

verdict
Runs
Argusic Score
71.7 / 100
cost of the verifying run
$0.85 (measured)
recorded runs
2
last tested
stars
698
forks
35
open issues
59
watchers
7
size
6 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 ytermusic, 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.

  • rustix 0.37.28 fails on current nightly (rustc_attrs-gated rustc_layout_scalar_valid_range_* no longer resolve; 'attributes starting with rustc are reserved')6 minutes
  • cargo build failed: pkg-config could not find alsa.pc (alsa dev headers not installed; system packages unavailable without root)5 minutes
  • cargo build failed: pkg-config could not find dbus-1.pc (libdbus-1-dev not installed)5 minutes
  • ytpapi2 unit tests read ../headers.txt (a real YouTube cookie); repository ships none, and the real account-dependent test advanced_like cannot pass without a genuine Google session5 minutes
Install time
27 minutes
Cold machine to finish
66 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
Cargo release build: 'Finished release profile in 26m17s' with exit 0; cargo test --release --workspace --exclude ytpapi2: all suites '0 passed; 0 failed' (9 result lines); ytpapi2 --lib: '2 passed; 1 failed' (advanced_test and home_test ok, advanced_like assertion failed); binary --help exit 0; --files and --fix-db exit 0 with headers provided; TUI ran 12-25s on DISPLAY=:99 pty rendering 'Choose a playlist'/'Local musics (0/0 0%)' and Error screen
Model tokens used
4,155,333
Exact commit tested
0663348365eb
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 2, run , the attempt that decided the verdict above. 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.

try:
    os.remove('/tmp/print_final.py'); print('removed')
except FileNotFoundError:
    pass
PY
ls /tmp/print_final.py 2>&1 | head -1; git -C /work/repo status --porcelain | wc -l" in /work/repo
 succeeded in 0ms:
removed
ls: cannot access '/tmp/print_final.py': No such file or directory
0
tokens used
4,155,333

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 27 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 Apache-2.0, 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.

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/3Runs100.000.85
Argusic Runner1/3Did not run43.331.34

Topics (from GitHub)

music-playerrustterminaltuiyoutubeyoutube-player

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/ytermusic.svg)](https://argusic.com/subject/ytermusic)

Questions

Does ytermusic run?
Yes. ytermusic runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test ytermusic?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0663348365eb. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ytermusic?
The run that produced this verdict cost $0.85: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ytermusic take to install?
27 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 ytermusic need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ytermusic?
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 ytermusic?
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