A tool that writes real playlists from my library, built in a dayA tool that writes real playlists from my library, built in a day

August 6, 2026 · Fifty-eight commits, nearly all from sessions nobody was sitting in front of. One project went from knowing nothing about my library to writing real playlists.Fifty-eight changes, almost all made without anyone watching. One project went from knowing nothing about my music to building real playlists.
last updated

Playlist Maker, start to finish

At ten past eight this project knew nothing about my music library. The probing was the expensive part and earned every minute: the interface it had to drive is old, quirky, and documented mostly by folklore.

The worst discovery was in the writer. The rest of the day went into the machinery that makes it safe to leave alone: a library-reset guard, a partial-read guard, and a rule that it may only ever touch a playlist whose identifier it recorded when it created one. Never by name: a name is a display choice a human can change at any moment, and a tool that decides what it may delete by reading a name will eventually delete something it did not create.

The quality pass at the end found the prompt and the validator asking for different things, which is the kind of disagreement that produces confident nonsense rather than an error.

Eight tickets: the runbook, the token commands, the read client, a scheduled refresh, the local media cache, self-hosted images, the page, and the pipeline that runs all of it in order. There is still no photo in it, because there is no token yet.

Two facts shape everything downstream. The image links the API returns are signed and expire within hours, so a page built from them is broken by morning. Hence copying every image onto this site's own storage. And the access token dies after sixty days and cannot be renewed once it has, so the refresh runs daily inside a ten-day window: ten chances rather than one.

The cache is one rule wearing three faces: only a complete walk may conclude a deletion. A run that stopped early has not seen the older end of the list, so it may add but never retire.

A job that restarts the server it runs inside

Every job prompt ends with “if you changed the backend, restart it”, and the queue worker runs inside that backend, so a job doing exactly as instructed kills the process supervising it. Two separate things were broken and fixing either alone was not enough: the session had to survive the restart, and its output had to survive the reader dying with it.

Elsewhere, an hour went on deleting things that were no longer true: a dozen commits that changed no behaviour and corrected what this repo says about itself. And two of the three ways out of the Email Organizer's seven-day credential clock were tested and closed.

A playlist tool, start to finish

At ten past eight this project knew nothing about my music. By the end of the day it was building real playlists. Most of the time went into poking at the music app to find out how it actually behaves, which was worth every minute.

The rest went into making it safe to leave alone. The important rule: it only ever touches playlists it made itself, and it knows which by a hidden identifier rather than by name, because names can be changed, and that is how a tool ends up deleting something it should not.

Eight tasks built the whole gallery: fetching, storing, publishing and the page itself. There is still not a single photo in it, because the account is not connected yet.

Two facts shaped all of it. The picture links expire within hours, so every image is copied onto this site instead. And the access pass expires after two months and cannot be recovered afterwards, so it renews itself early with ten days of spare chances.

A job that restarts the thing it runs inside

Every job is told to restart the server if it changed it, and the jobs run inside that server, so doing as instructed kills them. Two separate things had to be fixed: the job had to survive, and so did its output.