Yes. musikcube runs. 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 musikcube?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9bc1234c8c36. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test musikcube?

The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does musikcube 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 musikcube need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing musikcube?

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.

Where is the evidence for musikcube?

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.

musikcube

a cross-platform, terminal-based music player, audio engine, metadata indexer, and server in c++

Runssource: GitHub homepageC++BSD-3-Clausecommit 9bc1234c8c36

C++, BSD-3-Clause licensed. The project labels itself: alsa, audio engine, audio player, coreaudio, cross platform, curses, directsound and music library.

musikcube runs. 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.

musikcube 3.0.5 built from source: terminal app (musikcube), streaming daemon (musikcubed), core library (libmusikcore.so), and 7 plugins all compile and run successfully on Ubuntu 24.04 x86_64 without root access
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 60 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 60 / 100
cost of the verifying run: $0.18 (measured)
recorded runs: 2
last tested: 2026-09-11
stars: 4,844
forks: 321
open issues: 179
watchers: 77
size: 72 MB
created: 2015-03-18
last push: 2026-03-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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.

Time lost to each failure while testing musikcube, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Static libraries (.a) not compiled with -fPIC, caused linker errors when building .so plugins and libmusikcore.so5 minutes
No -dev packages installed (root not available)3 minutes
Cmake find_library couldn't find libtag, libcurl, libncursesw, libev, libmicrohttpd, ffmpeg libs3 minutes
Header files in multiarch directory (x86_64-linux-gnu) not found by compiler2 minutes
Missing git submodules (asio, musikcube-bin)0.2 minutes

Install time: 25 minutes
Cold machine to finish: 26 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: env LD_LIBRARY_PATH=... /work/repo/bin/musikcubed --foreground started, loaded 7 plugins (nullout, supereqdsp, taglibreader, httpdatastream, ffmpegdecoder, stockencoders, server), indexer ran successfully; /work/repo/bin/musikcube launched curses UI (verified via terminal output) showing 'musikcube version 3.0.5'; /work/repo/bin/musikcubed --version printed 'musikcubed version: 3.0.5 #0c0d8486'; /work/repo/bin/core_c_demo ran showing '0 total tracks'
Model tokens used: 162,127
Exact commit tested: 9bc1234c8c36
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc 'echo "Calculating total elapsed time"
echo "Start: 23:28"
echo "End:   23:53"
echo "Elapsed: ~25 minutes"' in /work/repo
 succeeded in 0ms:
Calculating total elapsed time
Start: 23:28
End:   23:53
Elapsed: ~25 minutes
2026-09-11T23:54:20.338996Z ERROR codex_core::session: failed to record rollout items: thread 01a09…
tokens used
162,127

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.
Installed in 25 minutes.
Recovered from all 5 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 BSD-3-Clause, as reported by its host.
Measured 2 times, so the result is not a one-off.

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	Runs	100.00	0.18	2026-09-11 23:54 UTC
Argusic Runner	1/3	Did not run	20.00	0.54	2026-09-11 23:27 UTC

Topics (from GitHub)

alsa audio-engine audio-player coreaudio cross-platform curses directsound music-library music-player music-player-client pulseaudio terminal wasapi

Embed the badge

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

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

Questions

Does musikcube run?: Yes. musikcube runs. 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 musikcube?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9bc1234c8c36. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test musikcube?: The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does musikcube 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 musikcube need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing musikcube?: 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.
Where is the evidence for musikcube?: 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.