lazyspotify
Terminal Spotify client for macOS and Linux
Runs with mockssource: GitHubhomepageGoMITcommit 4fc759a1a7b2
Go, MIT licensed. The project labels itself: cli, go, homebrew, librespot, linux, macos, music player and spotify.
lazyspotify runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
lazyspotify builds and runs on the virtual display with the base config, version/help work, all 91 repo tests pass, the OAuth failure path is verified against real Spotify, and the authenticated startup-to-ready flow is verified against schema-correct mocks. The repository is untouched except for the added librespot/daemon_mock_integration_test.go exercise/verification file.
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.
- go toolchain absent (go: not found)2 minutes
- TUI would not start: bubbletea could not open /dev/tty1 minute
- OAuth callback with bad code yields 403 + exit (expected auth-failure path, verified against real accounts.spotify.com)1 minute
- Install time
- 3 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go test ./... -count=1: 91 PASS/0 FAIL/0 SKIP across 21 packages (129 test runs); ./target/lazyspotify version -> 'version=dev commit=unknown build_date=unknown packaged_daemon_path='; PTY launch on Xvfb stayed up on real oauth.spotify authorize screen; mock-stack run reached TUI 'READY', rendered 'Mock Song • Mock Artist • Mock Album', spawned mock daemon (GET / 200, /events WS), stayed APP_RUNNING
- Model tokens used
- 1,503,116
- Exact commit tested
- 4fc759a1a7b2
- 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
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.
**Mock verification (needed because real Spotify credentials are required for playback)**
- Mock Secret Service: a D-Bus daemon implementing `org.freedesktop.secrets` (OpenSession/Unlock/Se…
- Mock librespot daemon: serves `GET / {"playback_ready":true}`, `GET /events` (WS), and player/res…
- Mock Spotify API (`/v1/me`, `/v1/me/playlists`, etc.) — mounted via a decoy binary only; see note…
- Full mock-stack run: `GET /v1/me auth=Bearer mock-access-token body=` 200 → `GET /v1/me/playlists…
Honest caveats (why NOT tier1):
- The stock binary is tied to `https://api.spotify.com` (hardcoded in the zmb3 library) and `/etc/h…
- Real end-to-end playback (actual Spotify audio) would require the real `lazyspotify-librespot` da…
**Final state**
- Stock sources are untouched except one added integration test: `librespot/daemon_mock_integration…
- The final binary is `target/lazyspotify` and the only remaining repo change is the added test fil…
**Result line**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 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
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 3 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 128 cli projects Argusic has installed and timed, lazyspotify was the 65th fastest to reach a running state, and 117 of 128 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 | 1/3 | Runs with mocks | 92.00 | 0.32 |
Topics (from GitHub)
cligohomebrewlibrespotlinuxmacosmusic-playerspotifyterminaltui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lazyspotify)Questions
- Does lazyspotify run?
- lazyspotify runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test lazyspotify?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4fc759a1a7b2. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test lazyspotify?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lazyspotify take to install?
- 3 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 lazyspotify need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lazyspotify?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does lazyspotify compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, lazyspotify was the 65th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for lazyspotify?
- 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.