rmpc
A modern, configurable, terminal based MPD Client with album art support via various terminal image protocols
Runs with mockssource: GitHubhomepageRustBSD-3-Clausecommit f677f677101b
Rust, BSD-3-Clause licensed. The project labels itself: mpd, mpd client, mpdclient, music, music player, sixel, terminal and terminal graphics.
rmpc runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
rmpc 0.11.0 builds from source in both debug and release profiles, passes all 897 tests, and its CLI subcommands (status, outputs, version, help) return correct data against a mock MPD server
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
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
- 15 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test --release exited 0, 897 passed; ./target/release/rmpc status returned valid JSON status via mock MPD server on port 6600; ./target/release/rmpc outputs returned valid JSON outputs list; ./target/release/rmpc --version returned 'rmpc 0.11.0 git f677f67'; ./target/release/rmpcd --help displayed usage
- Model tokens used
- 59,847
- Exact commit tested
- f677f677101b
- 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.
test ui::widgets::progress_bar::tests::middle_is_correct ... ok test ui::widgets::progress_bar::tests::only_track_when_empty ... ok test ui::widgets::progress_bar::tests::upper_bound_is_correct ... ok test ui::widgets::tabs::tests::can_be_stylized ... ok test shared::keys::key_resolver::test::timeout_on_prefix_is_noop ... ok test result: ok. 897 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.59s Ran `cargo test --release` as well to confirm. All 897 tests pass in both debug and release modes. … All builds succeed, all 897 tests pass, both binaries (`rmpc` and `rmpcd`) produce valid `--help` a… tokens used 59,847 Ran `cargo test --release` as well to confirm. All 897 tests pass in both debug and release modes. … All builds succeed, all 897 tests pass, both binaries (`rmpc` and `rmpcd`) produce valid `--help` a…
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 15 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed BSD-3-Clause, 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.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
mpdmpd-clientmpdclientmusicmusic-playersixelterminalterminal-graphicstui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rmpc)Questions
- Does rmpc run?
- rmpc runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test rmpc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f677f677101b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test rmpc?
- 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 rmpc 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 rmpc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rmpc?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for rmpc?
- 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.