Navidrome Daily: Making Artwork Failures Explainable
A new artwork diagnostic command line group, paired with fixes for undecodable image formats and an overeager circuit breaker, closes out a week focused on making artwork resolution failures visible and fixable instead of silent.
Duration: PT2M23S
Episode overview
This episode is a short developer briefing from Navidrome Daily.
It explains recent repository work in plain language.
- Show: Navidrome Daily
- Published: 2026-08-15T10:00:49Z
- Audio duration: PT2M23S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 15th, and today's codebase activity centers on one theme: artwork has been a black box, and this week it stopped being one.
The headline is PR 5957, which adds a full "artwork" command group to the CLI — explain, refresh, reprocess, and status. Instead of someone querying the database directly to figure out why an album cover is wrong or missing, they can now run "artwork explain" and see the actual priority chain: what won, what lost,…
That work immediately surfaced a gap: PR 5959 found that CLI commands only see built-in agents, not plugins, because the plugin manager only loads when the full server starts. On a library using five agents, three of them plugins, the CLI's view was quietly incomplete. That's flagged as a known limitation, not yet…
The second theme is resolution correctness. PR 5952 fixes a real regression: the new artwork pipeline requires a successful image decode to record anything, so formats Go can't decode — JPEG XL, HEIC, AVIF on some builds — failed silently, retried for twelve hours, then served a placeholder permanently. The fix now…
Rounding it out, PR 5961 corrects the external circuit breaker, which was slamming shut on a single…
T…