ISpotify

Local-first desktop music search, playlist, download, and playback app for Windows and Linux

Runs with mockssource: GitHubPythonMITcommit b694116fd638

Python, MIT licensed. The project labels itself: linux, music player, pyside6, python, windows and yt dlp.

ISpotify runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

All 59 tests pass, core libraries import cleanly, and the GUI application initializes and runs in offscreen mode with no crashes

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
1
last tested
stars
1,901
forks
1
open issues
3
watchers
0
size
1 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.

Install time
under a minute
Cold machine to finish
1 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pytest tests/ -v: 59 passed 0 failed; QT_QPA_PLATFORM=offscreen python main.py ran 8s with no crash; window creation + event processing exited cleanly
Model tokens used
30,375
Exact commit tested
b694116fd638
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.

Everything works. Let me compile the final result.
**Installation**: pip installed all dependencies cleanly (`PySide6`, `yt-dlp`, `requests`, `imageio…
**Tests**: All 59 tests pass (0.88s). Tests use mocks/temp files — no real YouTube or Discord crede…
**Launch**: The app starts and initializes the Qt window successfully with the `offscreen` platform…
**External tools**: `ffmpeg` and `node` are available at `/usr/bin/`. `deno` and `aria2c` are not i…
The version file (`core/version.py`) defines `APP_VERSION = "19.5.0"` (not `__version__`), which is…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 0…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 0.2, "errors": [], "test_d…
tokens used
30,375

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

  • Installed in 0.2 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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.

  • pear-desktop verified to run · TypeScript · 3 shared topics
  • openspot-music-app verified to run · TypeScript · 3 shared topics
  • spotifast tested, not verified · Rust · 3 shared topics
  • SoundCloud-Desktop tested, not verified · TypeScript · 3 shared topics
  • marktext verified to run · TypeScript · 2 shared topics
  • yazi verified to run · Rust · 2 shared topics

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.01

Topics (from GitHub)

linuxmusic-playerpyside6pythonwindowsyt-dlp

Embed the badge

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

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

Questions

Does ISpotify run?
ISpotify runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test ISpotify?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b694116fd638. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ISpotify?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ISpotify take to install?
0.2 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 ISpotify need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ISpotify?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for ISpotify?
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.

Discussion