Koito
Koito is a modern, themeable scrobbler that you can use with any program that scrobbles to a custom ListenBrainz URL
Runssource: GitHubhomepageGoMITcommit a079fa693569
Go, MIT licensed. The project labels itself: docker, listenbrainz, music, navidrome, scrobble, scrobbler, self hosted and subsonic.
Koito runs. An Argusic agent installed it in 57 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Go backend API server builds and runs: all 26 tests pass, the binary starts with SQLite, creates a default user, listens on a configured port, returns HTTP 200 on the /health endpoint, and shuts down cleanly.
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.
- libvips-dev and CGo dependencies (glib, pcre2, etc.) not pre-installed28 minutes
- bimg/vips.h naming conflict with system <vips/vips.h>15 minutes
- Linker resolution of transitive shared libs (HDF5, Imath, libsz, etc.)10 minutes
- Go 1.25 not pre-installed2 minutes
- Install time
- 57 minutes
- Cold machine to finish
- 56 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go test -count=1 ./... (26 passed, 0 failed, 0 skipped); curl -s -o /dev/null -w %{http_code} localhost:9998/apis/web/v1/health returned 200; ./koito launched, initialized SQLite DB, created default user, and responded to requests
- Model tokens used
- 418,492
- Exact commit tested
- a079fa693569
- 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.
{"level":"info","time":1789773094174,"message":"FetchMissingAlbumImages: No albums with missing ima…
{"level":"info","time":1789773094175,"message":"BackfillTrackDurationsFromMusicBrainz: No tracks ne…
{"level":"info","request_id":"ISYPIHpq","type":"access","time":1789773096753,"time":1789773096753,"…
Health endpoint HTTP status: 200
{"level":"info","time":1789773096755,"message":"Engine: Received server shutdown notice"}
{"level":"info","time":1789773096755,"message":"Engine: Waiting for all processes to finish"}
{"level":"info","time":1789773096755,"message":"Engine: Shutdown successful"}
Server stopped
All systems verified. Let me provide the final report:
tokens used
418,492
All systems verified. Let me provide the final report: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.
- Recovered from all 4 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 did not, or is not known
- Took 57 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.
Of the 9 docker projects Argusic has installed and timed, Koito was the 9th fastest to reach a running state, and 8 of 9 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.
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)
dockerlistenbrainzmusicnavidromescrobblescrobblerself-hostedsubsonic
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/koito)Questions
- Does Koito run?
- Yes. Koito runs. Argusic installed and launched it on a clean machine in 57 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test Koito?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a079fa693569. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Koito?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Koito take to install?
- 57 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 Koito need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Koito?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Koito compare with the alternatives?
- Of the 9 docker projects Argusic has installed and timed, Koito was the 9th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for Koito?
- 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.