Spotify's background coding agent merges 1,500+ migration PRs with 60–90% time savings
Spotify replaced hand-written AST and regex migration scripts in its Fleet Management system with a background coding agent, internally called Honk, that takes a natural-language prompt and opens PRs across thousands of repos. It has handled Java value types to records, breaking Scio upgrades, Backstage UI migrations and schema-aware config changes. Engineers and PMs can also trigger it from Slack or GitHub. Claude Code is its top-performing agent.
The numbers (as reported)
| Agent PRs merged to production | 1,500+ |
|---|---|
| Time saved on these migrations | 60–90% vs writing by hand |
| Users | Hundreds of developers |
| Pre-agent baseline | Maven updater script grew to 20,000+ lines |
Facts
- Company / subject
- Spotify
- Tools
- Claude Code, Claude Agent SDK, Internal CLI (Honk)
- Codebase
- brownfield
- Work type
- Migration
- Stack
- Java, Scio, Backstage, YAML/JSON
- Published
- 2025-11
- Last checked
- 2026-10-18
Caveats
Self-reported, and the time-saving method isn't detailed. Spotify flags slow and unpredictable agent runs, the need for new validation, safety guardrails and significant LLM cost. Later posts say prompts still evolve 'mostly by intuition'. A June 2026 Spotify post reports 76% more PRs to review, so review has become the bottleneck. Anthropic also publishes a co-marketing case study that claims 'up to 90%'.