SubTUI
A lightweight Subsonic TUI music player built in Go with scrobbling support.
Runs with mockssource: GitHubGoMITcommit 0d9e54bc0bb4
Go, MIT licensed. The project labels itself: golang, subsonic and tui.
SubTUI runs, with stand-ins for the services it depends on. An Argusic agent installed it in 30 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The app builds and launches, logs into and browses a mocked Subsonic server, renders search results, and sends stream loadfile commands to a mocked mpv IPC socket.
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- mpv required by README not installed (no root)12 minutes
- No Go toolchain installed in container10 minutes
- None of the app's packages contain tests8 minutes
- Install time
- 30 minutes
- Cold machine to finish
- 29 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go build exit 0 and go test ./... exit 0 (5 packages, no test files); e2e pty drive over mock server: /rest/getUser 200, screen rendered Mock Song/Mock Artist - Mock Album, QUEUE view after Enter, mock mpv logged loadfile of /rest/stream?id=song-1 plus 203 IPC requests
- Model tokens used
- 319,194
- Exact commit tested
- 0d9e54bc0bb4
- 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.
- Fixes: - Downloaded official Go 1.27.1 tarball into `/tmp/go`; built with it. - Built the app: `go build -ldflags "-X main.version=1.0.0-test -X main.commit=abc123" -o /tmp/su… - `mpv` missing (README prerequisite): recorded as gap, stood up a schema-correct mock: a fake `m… - Mock Subsonic server (`/rest/getUser`, `/getStarred2`, `/getPlaylists`, `/getPlayQueue`, `/getLyr… - E2E on a pty (`TERM=xterm-256color`, 100x60) driving the TUI: - Login form → submitted URL/user/password, server answered 200, `Welcome to SubTUI` and `Host no… - Typed search "test song" + Enter → `/search3` mock response, screen showed `Mock Song`, `Mock A… - Tab to main list + Enter → playing state: screen showed `QUEUE` view, no `Audio Engine Error`; … - Test suite: `go test ./...` exit 0, 5 packages `[no test files]` (0 tests exist in the repo). **Verified state** Install, launch, login, search, song selection, and stream playback to the mock mpv all exercised; …
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 30 minutes.
- Recovered from all 3 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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 with mocks | 92.00 | 0.20 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.12 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/subtui)Questions
- Does SubTUI run?
- SubTUI runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 30 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test SubTUI?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0d9e54bc0bb4. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test SubTUI?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does SubTUI take to install?
- 30 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 SubTUI need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing SubTUI?
- 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 SubTUI?
- 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.