digarr
Self-hosted music discovery for your library. Find artists and albums, review recommendations, and send them to Lidarr, slskd, or playlists. Bring your own AI provider or local model. Works without Lidarr.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit b65a8f5dca34
TypeScript, MIT licensed. The project labels itself: ai, albums, docker, lastfm, lidarr, listenbrainz, music discovery and musicbrainz.
digarr runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
digarr 1.18.0 is installed with Bun 1.4.4, dependencies are resolved, TypeScript type-checking passes, lint passes with no errors, the Vite frontend and Bun backend both build, embedded PGlite migrations apply on startup, the server boots and responds to HTTP requests, and 3550 of 3567 tests pass (15 PostgreSQL-specific failures are expected without Docker/postgresql).
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.
- Bun not installed — Node 18.19.1 was the only runtime2 minutes
- Node 18.19.1 lacks node:util.styleText — vitest 5/Vite 8 rolldown crashes with SyntaxError1 minute
- 15 test failures in 5 files: session-queries (5), oidc-link-postgres (4), oidc-token-retirement (1), sync-flow (4), reconciler-cache (1) — all ECONNREFUSED 127.0.0.1:5432
- Install time
- 7 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cd /work/repo && PORT=3000 PATH=/tmp/bun-install/bun-linux-x64:$PATH bun run dev: server printed 'Digarr running on http://localhost:3000' and 'Database migrations applied'; curl -s http://localhost:3000/api/v1/health returned 403 with {'error':'Setup not complete','redirect':'/setup'}
- Model tokens used
- 262,947
- Exact commit tested
- b65a8f5dca34
- 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.
**Dependencies installed (Bun 1.4.4) — clean.** TypeScript strict type-check passes. Lint passes (1… **340 of 355 test files pass (3550 of 3567 tests).** The 15 failures in 5 files are all PostgreSQL-… **The app launches and responds.** Server starts on port 3000, migrations apply automatically again… 2026-10-25T01:42:48.114414Z ERROR codex_core::session: failed to record rollout items: thread 01a17… 2026-10-25T01:42:48.114496Z ERROR codex_core::session: failed to record rollout items: thread 01a17… 2026-10-25T01:42:48.114513Z ERROR codex_core::session: failed to record rollout items: thread 01a17… tokens used 262,947 Here's the full diagnostic report. **Dependencies installed (Bun 1.4.4) — clean.** TypeScript strict type-check passes. Lint passes (1… **340 of 355 test files pass (3550 of 3567 tests).** The 15 failures in 5 files are all PostgreSQL-… **The app launches and responds.** Server starts on port 3000, migrations apply automatically again…
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
- 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.
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.
- Took 7 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 237 ai projects Argusic has installed and timed, digarr was the 145th fastest to reach a running state, and 168 of 237 reached one at all.
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.03 |
Topics (from GitHub)
aialbumsdockerlastfmlidarrlistenbrainzmusic-discoverymusicbrainzrecommendationsself-hosted
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/digarr)Questions
- Does digarr run?
- digarr runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test digarr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b65a8f5dca34. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test digarr?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does digarr take to install?
- 7 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 digarr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing digarr?
- 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.
- How does digarr compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, digarr was the 145th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for digarr?
- 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.