spotify-player
A Spotify player in the terminal with full feature parity
Runssource: GitHubRustMITcommit dac1fa7aa2c1
Rust, MIT licensed. The project labels itself: cli, music, music player, player, rust, spotify, spotify api and spotify tui.
spotify-player runs. An Argusic agent installed it in 15 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
spotify_player 0.25.1 builds and passes all 45 tests, clippy (all features + no-features), and cargo fmt; the binary starts on Xvfd and produces the expected OAuth authentication URL on first launch. All requested features (streaming, rodio-backend, media-control, image, notify, fzf, daemon) compile and run without 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 83.3 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.
- pkg-config could not find alsa/dbus-1 (no -dev headers, no root)4 minutes
- rustc/cargo not installed1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test --no-default-features --features rodio-backend,media-control,image,notify,fzf,daemon: 45 passed, 0 failed; cargo clippy -- -D warnings: passed; cargo fmt --all -- --check: passed; spotify_player --version returned 'spotify_player 0.25.1'; spotify_player features confirmed all requested features enabled; spotify_player launched and displayed OAuth authentication prompt confirming startup
- Model tokens used
- 86,437
- Exact commit tested
- dac1fa7aa2c1
- 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 1, 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.
**Build and verification results**: - `cargo build --no-default-features --features rodio-backend,media-control,image,notify,fzf,daemon… - `cargo test` (same features) → **45 passed, 0 failed** - `cargo clippy -- -D warnings` → **no warnings**, includes both feature-gated and no-feature paths - `cargo fmt --all -- --check` → **passed** - `spotify_player --version` → `spotify_player 0.25.1` - `spotify_player features` → confirms streaming, rodio-backend, media-control, image, notify, fzf,… - `spotify_player generate bash` → generates shell completions - `spotify_player` (launched, via Xvfb) → starts and initiates the OAuth authentication flow (expec… **Errors encountered** 1. **`rustup` and `cargo` not installed** → installed with standard rustup.sh, `<5 min` 2. **`pkg-config` cannot find `alsa` and `dbus-1`** (`libasound2-dev`/`libdbus-1-dev` not installed…
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 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 did not, or is not known
- Took 15 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
Of the 25 cli projects Argusic has installed and timed, spotify-player was the 22nd fastest to reach a running state, and 23 of 25 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.
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 | 66.67 | 0.03 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.06 |
Topics (from GitHub)
climusicmusic-playerplayerrustspotifyspotify-apispotify-tuiterminalterminal-basedtuivim
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/spotify-player)Questions
- Does spotify-player run?
- Yes. spotify-player runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test spotify-player?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dac1fa7aa2c1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test spotify-player?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does spotify-player take to install?
- 15 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 spotify-player need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing spotify-player?
- 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.
- How does spotify-player compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, spotify-player was the 22nd fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for spotify-player?
- 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.