museeks
🎵 A simple, clean and cross-platform music player
Could not verifysource: GitHubhomepageTypeScriptMITcommit 7163f6019a31
TypeScript, MIT licensed. The project labels itself: cross platform, electron, museeks, music, music player and react.
Argusic could not get museeks running. An Argusic agent installed it in 54 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The frontend installs, builds, and all 9 unit tests pass. The Rust/Tauri backend could not compile due to cumulative disk space exhaustion (7.8GB) from extracting system library .deb packages, the Rust toolchain, and 638 compiled crate dependencies. The E2E browser tests (7 tests across 3 files) fail because they require the Tauri desktop application to be running.
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 50 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.
- System libraries for Tauri/webkit2gtk not installed (no root access)15 minutes
- Rust backend (cargo build) ran out of disk space (7.8GB total) after compiling 638 crate dependencies10 minutes
- Vite+ vp CLI not available and npm-installed version had native binding issues8 minutes
- Node.js 18.x installed, project requires >=225 minutes
- E2E browser tests failed: Playwright chromium not installed3 minutes
- pnpm-workspace.yaml had strictPeerDependencies:true causing install failure after vp migrate2 minutes
- Install time
- 54 minutes
- Cold machine to finish
- 55 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- vp test --project unit exited 0, 3 test files (9 tests) passed; vp build succeeded (1293 modules, dist/index.html generated); cargo build failed with disk full after 638 deps
- Model tokens used
- 427,235
- Exact commit tested
- 7163f6019a31
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec /bin/sh -lc 'export PATH="/home/runner/.cargo/bin:$PATH" cargo --version 2>&1 rustc --version 2>&1' in /work/repo succeeded in 0ms: cargo 1.99.0 (5f94df478 2026-08-27) rustc 1.99.0 (b940084d7 2026-09-28) Now I have all the data to compile the final assessment. The development started at ~14:44 UTC and … 2026-10-04T15:38:42.640880Z ERROR codex_core::session: failed to record rollout items: thread 01a10… tokens used 427,235 Now I have all the data to compile the final assessment. The development started at ~14:44 UTC and …
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 7 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
- An agent with no time limit did not get it running.
- Took 54 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
Of the 7 cross-platform projects Argusic has installed and timed, museeks was the 7th fastest to reach a running state, and 4 of 7 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 | Did not run | 50.00 | 0.34 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.22 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/museeks)Questions
- Does museeks run?
- Argusic could not verify that museeks runs. Argusic installed and launched it on a clean machine in 54 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test museeks?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7163f6019a31. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test museeks?
- The run that produced this verdict cost $0.34: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does museeks take to install?
- 54 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 museeks need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing museeks?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does museeks compare with the alternatives?
- Of the 7 cross-platform projects Argusic has installed and timed, museeks was the 7th fastest to reach a running state, and 4 of 7 reached one at all.
- Where is the evidence for museeks?
- 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.