Yes. mousiki runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test mousiki?

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

What did it cost to test mousiki?

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

How long does mousiki take to install?

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 mousiki need a GPU?

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

What goes wrong when installing mousiki?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for mousiki?

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.

mousiki

Highly customizable TUI music player designed to be fast and lightweight

Runssource: GitHubC++Apache-2.0commit 3a08e896c99d

C++, Apache-2.0 licensed. The project labels itself: cli, cpp17, indic languages, latin, music player, music streaming, ncursis free and online music.

mousiki runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Mousiki builds and runs: the binary launches its full keyboard-driven TUI in the terminal, displaying the spinning disk, progress bar, local/queue panels, and volume indicator; Python auxiliary tools (yt-dlp, lyrics fetcher, YouTube search) all connect to their respective live APIs and return valid data.
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 100 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.02 (measured)
recorded runs: 2
last tested: 2026-09-21
stars: 212
forks: 15
open issues: 3
watchers: 0
size: 23 MB
created: 2026-09-08
last push: 2026-09-19

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.

Install time: 2 minutes
Cold machine to finish: 4 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: ./build/mousiki launched and rendered TUI (disk art, panels, progress bar, volume bar) on virtual display; timeout 3 exit code 124 (expected: killed after timeout). lyrics fetcher returned ok=true with word-level timestamps from Better Lyrics API. fast_yt_search.py returned real YouTube results. yt-dlp --version returned 2026.08.19. cmake --build exit 0, binary 1.7MB at build/mousiki
Model tokens used: 45,729
Exact commit tested: 3a08e896c99d
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.

- Installed `yt-dlp` and `requests` into a Python venv (`/work/repo/venv`) — the system pip blocks …
- Copied the config and yt-dlp config to `~/.config/`
- `cmake -B build` configured cleanly; `cmake --build build -j$(nproc)` compiled all 24 C++ sources…
**Launch verified**:
- `./build/mousiki` started and rendered the full TUI: spinning disk art, progress bar, volume slid…
- Process exited with code 124 after 3s timeout (expected — the app runs until `q` is pressed)
**Python auxiliaries verified live**:
- `scripts/lrc.py` fetched word-level enhanced LRC lyrics for "Shape of You" from Better Lyrics (re…
- `scripts/fetch_lyrics.py` returned a valid JSON result with `"ok": true`
- `scripts/fast_yt_search.py` returned real YouTube search results
- `yt-dlp --version` confirmed v2026.08.19
**No errors encountered** during the entire process. No test suite exists in the repo, so verificat…

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 2 minutes, faster than the median of the 24 comparable projects Argusic has measured.
Nothing broke on the way: zero errors between clone and running.
Ran without a GPU, so it does not need one to start.
Licensed Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

Of the 25 cli projects Argusic has installed and timed, mousiki was the 6th fastest to reach a running state, and 23 of 25 reached one at all.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.
A quick evaluation: it was running 2 minutes after the clone.
Following its own README: the documented path worked with nothing to fix.

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.02	2026-09-21 10:35 UTC
Argusic Runner	1/3	Runs	100.00	0.03	2026-09-21 07:22 UTC

Topics (from GitHub)

cli cpp17 indic-languages latin music-player music-streaming ncursis-free online-music soft-dependency tui-app

Embed the badge

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

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

Questions

Does mousiki run?: Yes. mousiki runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test mousiki?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3a08e896c99d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test mousiki?: The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does mousiki take to install?: 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 mousiki need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mousiki?: Nothing did, in the recorded run: zero errors between clone and running.
How does mousiki compare with the alternatives?: Of the 25 cli projects Argusic has installed and timed, mousiki was the 6th fastest to reach a running state, and 23 of 25 reached one at all.
Where is the evidence for mousiki?: 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.