cliamp
cliamp - Terminal music player inspired by winamp
Runssource: GitHubhomepageGoMITcommit d40cb792b606
Go, MIT licensed. The project labels itself: cliamp, icecast, icecast player, jellyfin client, m3u, music, music player and navidrome.
cliamp runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
cliamp builds from source, all 52 Go test packages pass with gofmt and go vet clean, and the binary responds to --help and runs its daemon to audio initialization despite no ALSA hardware in this container.
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
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.
- CGO link failed: missing -dev packages for ALSA, FLAC, Ogg, Vorbis, mpg1238 minutes
- Linker could not find -lasound/-lFLAC/-lmpg123/-logg/-lvorbis/-lvorbisenc after first attempt4 minutes
- Go binary not found in PATH (no goenv/mise/asdf)3 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- make check exited 0, 52 packages ok; /tmp/cliamp --help printed full usage; timeout 5 /tmp/cliamp --daemon ran to audio-device probe then logged expected 'no audio card' error
- Model tokens used
- 64,223
- Exact commit tested
- d40cb792b606
- 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
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 2, 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.
- **Run:** `cliamp --daemon` starts but exits with expected "no audio card" since this container ha… - **Help:** `cliamp --help` prints full usage with all commands and global options tokens used 64,223 All tests pass and the binary builds. Let me provide the final result. **Summary of what was done:** - **Go install:** Downloaded `go1.26.8.linux-amd64.tar.gz` and extracted to `/home/runner/go1.26.8` - **C library -dev packages:** Downloaded `.deb` packages for `libasound2-dev`, `libflac-dev`, `lib… - **Build:** `go build ./...` and `make build` both succeed — binary compiled to `/tmp/cliamp` - **Tests:** `make check` (gofmt + go vet + go test) passes for all 52 packages, including daemon, … - **Run:** `cliamp --daemon` starts but exits with expected "no audio card" since this container ha… - **Help:** `cliamp --help` prints full usage with all commands and global options
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 15 minutes.
- Recovered from all 3 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 MIT, 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
Topics (from GitHub)
cliampicecasticecast-playerjellyfin-clientm3umusicmusic-playernavidromenavidrome-clientplex-clientplugin-systempodcastradiosoundcloudspotifystreamwinampyoutubeyt-dlp
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cliamp)Questions
- Does cliamp run?
- Yes. cliamp runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test cliamp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d40cb792b606. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test cliamp?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cliamp take to install?
- 15 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 cliamp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cliamp?
- 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.
- Where is the evidence for cliamp?
- 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.