Forty Cents of Agent Research, One Hallucinated Email, and the Script That Caught It
NeonBench is in public beta, and the people most likely to care are the schools and studios that still teach glass bending. There is no directory of them, and finding them is tedious web research, which is exactly what a cheap agent is for, and exactly where a cheap agent will make things up. So I spent forty cents on ten agent jobs, got back a spreadsheet of trade schools, and built a deterministic verifier that refused to trust any of them. It caught a hallucinated email address. The whole thing is the subject of this post.
The agent is the same Hermes/DeepSeek setup I use for code jobs on the homelab GPU box (.62): an open-source agent framework in a container, a DeepSeek V4 Flash model through OpenRouter, briefs written as Markdown files, one job per brief, run in parallel. For research jobs it gets the web, file and terminal toolsets and a plain output directory instead of a git worktree. A pleasant surprise: the framework’s web search works with no API key at all (it falls back to a free search backend), so the research side cost nothing beyond model tokens.
The punchline, spoiled up front: the model followed every rule except the one that mattered, a dumb script was the only thing that noticed, and the forty cents bought a lesson about rules versus controls that I’d happily have paid more for.
One Song Wouldn't Play. 231 Files Were Broken. Lidarr's Ogg Tag Writer Was the Culprit.
On September 11, 2026, one song would not play. The client just retried it, in a loop, forever. Not a silence, not an error dialog — a little spinner that never resolved. I’d seen that behavior before, and I’d always blamed the server. This time the server was fine, and the truth was stranger: Lidarr had been quietly corrupting my Ogg Vorbis files for months, nightly, one byte at a time.
The setup is a normal homelab. Music lives on the NAS (.12, ZFS) and is served by Navidrome on .21, which streams the raw file — transcoding is off — to a desktop client called Supersonic. Lidarr 3.1.0.4875, also on .21, manages the library. Somewhere along the way I’d set “Write Metadata to Audio Files” to Sync (writeaudiotags = Sync, scrubaudiotags = True), which means every nightly Refresh Artist rewrites tags and embeds cover art directly into the files themselves.
That setting is the whole story. It turned a metadata tool into a corruption machine.
Porting Pithos to macOS: Four Merged PRs, One Rewritten Design, and a Red CI Nobody Had Fixed
I like Pandora. I use a Mac. And the best Pandora client on Linux, the GTK 3, Python Pithos, has never supported macOS. Last release was 1.6.2 back in March 2024. The maintainer, TingPing (Patrick), is a one-person operation, and the project had no merges at all for over two years. My goal, set in mid-September: get Pithos running on my Mac, then send whatever it took upstream as pull requests he could actually review.
Two days later the project had its first merges since 2024, and they were mine. That sounds like a victory lap. This post is the more honest version: four merged PRs, one of them redesigned on request, a CI that had been red for months before anyone fixed it, and the single biggest discovery of the whole trip, that a one-maintainer project rewards you in proportion to how much upstream time you decide not to spend.