spotifast
Spotify, native and fast. One lightweight Rust app for your whole library, local playback, and Spotify Connect on Linux, macOS, and Windows.
Runs with mockssource: GitHubhomepageRustMITcommit b5d579b857e6
Rust, MIT licensed. The project labels itself: audio, cross platform, desktop app, egui, gui, librespot, linux and macos.
spotifast runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Spotifast 0.8.0 builds from source on Ubuntu 24.04 (x86_64) without root, all 758 unit tests pass, and the app renders a demo screenshot showing the playlist view with queue panel visible.
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 92 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.
- Missing -dev packages (alsa, pulse, xkbcommon, wayland, libx11, libclang, etc.)5 minutes
- libclang not found at link time (libclang-18.so was a dead symlink without runtime library)2 minutes
- Disk full during test (35GB target/)2 minutes
- No Rust toolchain installed1 minute
- libGL and libgomp missing linker .so symlinks1 minute
- Install time
- 25 minutes
- Cold machine to finish
- 71 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- cargo test --all-targets --features demo passed: 758 unit tests ok, 9 integration/doc tests ok, 0 failed. Demo mode: ./target/debug/spotifast --demo --demo-page playlist:pl1 --demo-size 800x600 --demo-shot /tmp/demo_shot.png wrote a valid 207KB PNG (verified PNG header 89504e47). Binary reports 'spotifast 0.8.0' via --version.
- Model tokens used
- 587,745
- Exact commit tested
- b5d579b857e6
- 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 1903ms: test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s All tests pass and the app runs in demo mode. Here's the final assessment: **Install succeeded** - Rust toolchain installed, system library dependencies extracted from Ubuntu… **Launch succeeded** - The binary answers `--version` (`spotifast 0.8.0`), and demo mode produces a… **Full test suite**: 758 unit tests + 9 doc/integration tests, all pass (1 intentionally ignored). … tokens used 587,745 All tests pass and the app runs in demo mode. Here's the final assessment: **Install succeeded** - Rust toolchain installed, system library dependencies extracted from Ubuntu… **Launch succeeded** - The binary answers `--version` (`spotifast 0.8.0`), and demo mode produces a… **Full test suite**: 758 unit tests + 9 doc/integration tests, all pass (1 intentionally ignored). …
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 5 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 4 comparable projects Argusic has measured.
Of the 5 audio projects Argusic has installed and timed, spotifast was the 4th fastest to reach a running state, and 4 of 5 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.30 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.20 |
Topics (from GitHub)
audiocross-platformdesktop-appeguiguilibrespotlinuxmacosmprismusicmusic-playerrustspotifyspotify-clientspotify-connectwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/spotifast)Questions
- Does spotifast run?
- spotifast runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test spotifast?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b5d579b857e6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test spotifast?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does spotifast 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 spotifast need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing spotifast?
- 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 spotifast compare with the alternatives?
- Of the 5 audio projects Argusic has installed and timed, spotifast was the 4th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for spotifast?
- 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.