Spotify
Claude Code and the Honk agent for code migrations and daily engineering
Spotify's engineers had AI write 73% of pull requests, with Claude Code agents running in the background
Problem
Spotify has about 2,900 engineers and a backend of more than 20 million lines of code. Large migrations and maintenance changes across thousands of repositories took months, and about ten were done each year.
Approach
Engineers ran Claude Code in terminal sessions, often with several background agents at once. Spotify also built Honk on the Claude Agent SDK to make migration and maintenance changes across repositories. A judge component checked the agent's output before a pull request was accepted.
Results
Takeaway
Adding a check on the agent's output raised the success rate of automated pull requests sharply. Spotify said it was still working to link pull requests and deployments to user value.
Categories
- Size
- Large enterprise
- Industry
- Media and entertainment
- Business function
- IT and R&D
- Innovation type
- Process innovation
- AI technology
- AI agentsGenerative AI
- Adoption
- Off-the-shelf tool or platform
- Evidence
- Vendor case study
Sources
Source summaries
Anthropic's Office Hours session with Spotify engineers covers how the company uses Claude Code and its Honk agent for daily work and large-scale code maintenance. It gives the share of AI-authored pull requests, the gain in pull request frequency and the success rate of Honk after a judge was added. The page carries no date; the Internet Archive first saved it on August 22, 2026.
Full details are in the original sources.