Spotify · Agent system
Honk / Xirp
Honk is Spotify's background coding agent (high confidence); Xirp is the workspace/context/session layer around it (medium confidence). Honk runs on a Claude-Agent-SDK harness in Kubernetes, uses trusted CI tools, and combines formatting and linting with LLM-based diff evaluation.
1 Supports2 Supports3 Supports
- Approach type
- Agent system
- Work
- Coding, Migrations, Code review
- Human involvement
- Drafts reviewed
- Invocation
- Event driven, Interactive
- Interfaces
- Slack, Github, Cli
- Deployment stage
- Scaled
- Evidence strength
- Detailed primary
- Entry reviewed
How it works
The workflow the sources report for this implementation.
The harness combines build/test tools, formatting and linting, and LLM-based diff evaluation
Target thousands of repos, run builds/tests, open and merge PRs at fleet scale
The session/context surface around the agent rather than an autonomous worker itself
Where people stay involved
- Honk coding task → verified pull requestWork product review · Level 3
Level 3 for Honk coding task → verified pull request; human attention boundary: work-product-review.
- Observation date
- 2025
Implementation details
Honk runs in a constrained Kubernetes container (it does not inherit arbitrary engineer credentials); jobs execute inside Fleet Management / Fleetshift
Honk: Claude Agent SDK + Spotify's own harness + Kubernetes pods; Honk v2 adds shared sessions, projects, and Chirp orchestration
Claude via the Agent SDK (Claude-centric); the surrounding platform is multi-model
slack, github, cli
Limited, deliberate tool surface; trusted CI tools verify changes, while an internal CLI runs formatting and linting through MCP and evaluates diffs with an LLM judge
Backstage/catalog ownership and developer-standardization primitives built over years, exposed via MCP/CLI
Runs in a constrained container rather than inheriting engineer credentials
Fleet Management coordinates repo targeting, builds/tests, and PR workflow at scale; Xirp pairs sessions with Portal org context
Reported results and limitations
The catalog records what the sources report, with the scope and the denominator of every figure. A qualification below limits the figure it sits under.
Reported metrics
1,500+ merged pull requests generated by Honk
The source does not report the denominator of this figure.
- Reported by
- Spotify
- Scope
- Cumulative merged Honk-generated PRs reported in Part 1; no measurement cutoff in preserved text
- Method
- Company-reported merged pull request count
1,500+ merged AI-generated PRs (Honk)
The source does not report the denominator of this figure.
- Reported by
- Spotify
- Scope
- Cumulative merged Honk-generated PRs reported in Part 1; no measurement cutoff in preserved text
60-90% time savings on migrations vs manual
- Reported by
- Spotify
- Scope
- Selected code migrations using Honk compared with writing the changes manually
- Denominator
- Manual completion time for the same migration work
Around half of Spotify PRs automated by Fleet Management since mid-2024, including deterministic transformations
- Reported by
- Spotify
- Scope
- Fleet Management automated pull requests since mid-2024, including deterministic transforms
- Denominator
- All Spotify pull requests
- Observation date
- 2024
Lessons and interpretation
Combine deterministic build, formatting, and lint checks with LLM-based diff evaluation
Constrain the agent's environment and tools rather than handing it engineer credentials
Invest in org context (Backstage/catalog) before agentic dev accelerates
Autonomy without structure fragments into per-engineer configs; shared org context is the multiplier
Sources and research details
Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.
- Spotify's Journey with Our Background Coding Agent (Honk)https://engineering.atspotify.com/2025/11/spotifys-background-coding-agent-part-1
- Code with Claude: coding is no longer the constraint (Honk v2)https://engineering.atspotify.com/2026/6/code-with-claude-coding-is-no-longer-the-constraint
- Xirp - Powered by Spotify Portalhttps://xirp.spotify.com/
Research details for every claim on this page
- Summary
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Headline claim
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Reported by
- Spotify
- Scope
- Cumulative merged Honk-generated PRs reported in Part 1; no measurement cutoff in preserved text
- Denominator
- Not reported
- Method
- Company-reported merged pull request count
- Observation date
- Not reported
- SupportsSpotify's Journey with Our Background Coding Agent (Honk)Preserved content.md, lines 70
- Sandbox
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Harness
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Model
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Interfaces
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Tool access
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Knowledge
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Credentials
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Context management
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Supporting component
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Supporting component
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Supporting component
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsXirp - Powered by Spotify Portal
- Key observation
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Reported by
- Spotify
- Scope
- Cumulative merged Honk-generated PRs reported in Part 1; no measurement cutoff in preserved text
- Denominator
- Not reported
- Method
- Not reported
- Observation date
- Not reported
- SupportsSpotify's Journey with Our Background Coding Agent (Honk)Preserved content.md, lines 70
- Key observation
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Reported by
- Spotify
- Scope
- Selected code migrations using Honk compared with writing the changes manually
- Denominator
- Manual completion time for the same migration work
- Method
- Not reported
- Observation date
- Not reported
- SupportsSpotify's Journey with Our Background Coding Agent (Honk)Preserved content.md, lines 70–77
- Key observation
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Reported by
- Spotify
- Scope
- Fleet Management automated pull requests since mid-2024, including deterministic transforms
- Denominator
- All Spotify pull requests
- Method
- Not reported
- Observation date
- 2024
- SupportsSpotify's Journey with Our Background Coding Agent (Honk)Preserved content.md, lines 22–38
- Lesson
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Medium
- Confidence reason
- The catalog derives this observation from the linked sources.
- Lesson
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Medium
- Confidence reason
- The catalog derives this observation from the linked sources.
- Lesson
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Medium
- Confidence reason
- The catalog derives this observation from the linked sources.
- Lesson
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Medium
- Confidence reason
- The catalog derives this observation from the linked sources.
- SupportsXirp - Powered by Spotify Portal
- Operating model assessment
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- High
- Confidence reason
- The source documents automated verification followed by a pull-request workflow that retains human review.
- Observation date
- 2025